ERPNext is the only system of record; we build tools on it

User (October 2026): we only build tools and interfaces that interact
with ERPNext; invoices, stock and the rest are kept there, except
telemetry and other machine data.

digital-factory.md: standing decision, decisions 2, 3, 6, 7 and 10
rewritten (ERPNext holds every record of the business and of production,
including artist gates, metal-part genealogy as serial numbers with
parents, and quality inspections; the machine-data store keeps only
cycle and record rows, the hash chain and time series, keyed to ERPNext
names; ERPNext first, then custom fields or document types in cnx_erp,
then a tool, never a second business database). Systems table,
architecture labels, factory application section (modules as a table:
records in ERPNext, what we build, machine data outside; our only tables
are the machine-data ones), ownership table, integration rules 4 and 8,
phasing and estimates (cnx_erp app 2 to 3 person-months; total 3.5 to 6).
artist-platform.md: campaigns are an ERPNext document from launch, pledges
post as advance payment entries; traceability, README, facility security
(archive location on the serial number), production timeline (sets per
mother on the mother's serial number), crane-workshop spares store,
total-investment.

Factory console: KPI row no longer touches the postings card (user
screenshot); ERPNext page, order card, sidenote and ledger say every
record lives in ERPNext and only machine data stays outside; new
postings for artist gates, stamper metrology inspections, stamper set
serial numbers (grown, retired with play count). Checked headless:
Edge dark and light, 1440/1024/390, no overflow or page errors, rows
aligned, pw_fc, pw_wo, pw_feed and pw_erp pass.

README.md

@@ -149,9 +149,10 @@ The detail lives in dedicated documents:
   shipment, and the requirements this sets for the factory software
 - [Digital factory systems plan](docs/digital-factory.md): every system
   that has to exist for environment, machine, QC and genealogy data to land
-  in one database keyed to one record identity, with ERPNext as the
-  plant's ERP that every tool we build integrates with: the plant as one
-  more site in B4L's existing NixOS fleet (the cnx-network clan: mesh, DNS, fleet
+  in one place keyed to one record identity, with ERPNext as the plant's
+  only system of record (every tool we build reads and writes it; only
+  machine data stays outside): the plant as one more site in B4L's
+  existing NixOS fleet (the cnx-network clan: mesh, DNS, fleet
   monitoring, site gateway module, public proxy), what changes in that
   repo, VLAN zoning, Telegraf/MQTT acquisition source by source, QC
   instrument integration, the factory application, alerting, backup,