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.

docs/traceability.md

@@ -45,11 +45,13 @@ For any order, the customer can follow the full chain:
   mother, stamper, press run, box) gets an ID, and every ID knows its
   parents. A customer complaint about one record resolves to a specific
   stamper, press, shift, and compound lot.
-- **One ERP, one set of keys**: business documents (orders, work orders
-  and job cards, lots, deliveries, invoices) live in ERPNext, which the
-  whole plant runs; the traceability detail lives in the factory
-  application and carries the same ERPNext document names, so a trace and
-  an invoice point at the same order
+- **One system of record, one set of keys**: every record of the
+  business and of production (orders, gates, work orders and job cards,
+  batches, quality inspections, metal parts and their genealogy,
+  deliveries, invoices) lives in ERPNext, which the whole plant runs;
+  only machine data (per-cycle rows, per-record results, telemetry, audio
+  captures) lives outside it, carrying the same ERPNext document names,
+  so a trace and an invoice point at the same order
   ([digital factory](digital-factory.md#erpnext-the-plants-erp)).
 - **Environment attached**: the whole-factory HVAC monitoring (temperature,
   humidity, PM per zone) is logged on the same timeline, so any production