Decided by the user (October 2026): the whole plant runs ERPNext, and
all tooling we develop has to interact with it.
digital-factory.md: standing decision in the summary; decision 10
(ERPNext owns the business documents, the factory application owns the
floor; ERPNext names are the shared keys); new section 'ERPNext: the
plant's ERP' with the ownership table (customers, prices, sales orders,
items and BOMs, work orders and job cards per station, batches and
quality inspections per compound lot, serial numbers for metal parts,
downtime entries, delivery notes, assets, accounting, payroll vs. cycles,
per-record inspection, genealogy and the hash-chained log staying in the
factory application), the integration rules (one typed Frappe REST
client in cnx-factory, an integration user per tool, webhooks in,
transactional outbox with idempotent postings so the floor never waits
on the ERP, business-sized postings, customisation as a Frappe app in
Gitea, nightly reconciliation, no public ERPNext endpoint, new tools use
the same client), hosting on NixOS (no nixpkgs module, NixOS/nixpkgs
#241921; Avunu frappe-nix as the start, frappe_docker as
oci-containers fallback; MariaDB + Redis; vinyl-erp on site behind the
gateway proxy; OIDC sign-on; upgrades on a restored copy), Thai
localisation (Ecosoft erpnext_thailand: VAT, WHT, PND, billing notes;
Ecosoft as partner to quote; payroll and BOI reporting to check),
phasing (dev ERPNext now; accounting and assets from the first capex
invoice; manufacturing at commissioning) and estimates. ERPNext added
to the architecture diagram, services, machines (vinyl-erp), module
list, backup, cost, build order and open decisions; the old 'ERP out of
scope, decide after launch' line replaced.
artist-platform.md: price list, customers, sales orders, campaign
pledges as payment entries, through the plant's outbox. traceability.md:
one ERP, one set of keys. README summary. total-investment.md added
scope: ERPNext (to quote, not in the sum, no licence fee).
New page docs/factory-console.html (site /demos/factory/): the factory
application of digital-factory.md on a simulated plant day, with a
switch to the customer portal of the same orders.
Factory console (sidebar: Floor, Orders, Quality, Lab, Metal, Ledger):
- floor: five presses of the launch fleet (two Newbilt Duplex systems,
one Classic) with the mounted order, live good / rejected counters,
stamper plays against life, cycle time and steam; KPIs for the day;
live optical inspection stream with record keys; alerts (stops, lab
holds, stampers near end of life, listening reviews, long gate waits);
stations (cutting, galvanics, stamper prep, lab, packing); orders by
stage; good records per day
- orders list with stage filters and search; order detail with stage
track, approvals, metal genealogy and stamper metrology, press run
telemetry, compound lot certificate, rejects by reason, audio samples,
packing and shipping, and the order's events
- press detail with telemetry sparklines; quality (rejects by reason,
yield per press, audio comparison); lab (compound lots with results
against illustrative limits, one lot on hold with re-dry and retest,
regrind batches, hoppers); metal (baths, mounted stampers, metrology,
archive); hash-chained event log
Customer portal (four demo customers: pressing now, waiting to approve
the test pressing, in plating, delivered): progress through every step
and the three gates, copies pressed so far with the latest copies and
their record keys, approving the test pressing books the press slot
(greedy plan of the queue gives the start time and press), and a quality
report that fills in step by step: files, lacquers, metal parts with
metrology, test pressings, the compound lot's lab results, pressing and
inspection, listening checks, packing.
Simulation: 60 days warmed up at load (about 0.7 s), then 1x to 3600x.
Stages and durations from the production timeline, Newbilt cycle times,
two shifts 06:00 to 22:00, unplanned stops, stamper life 1,000 to 2,000
plays, audio sampling first-off plus about 1 in 50 (1 in 25 near end of
life), compound lots through the lab gate and release test pressing.
All orders, values and IDs are simulated; limits are illustrative.
Linked from digital-factory.md (the factory application), traceability.md
(customer-facing view), the README and the landing page.
New static page docs/make-a-record.html (test site /demos/make-a-record/):
the artist platform as a customer would see it, polished for presenting.
- five steps (design, music and art, price, fan funding, track) with a
sticky stage: to-scale mock-up (record spins at 33 1/3 or 45 rpm on
hover), spec chips, price per copy, ship month and the next action
- design as option cards and swatches; options that do not apply stay
visible and disabled (weight and gatefold off 12", colour pickers for
black vinyl)
- masters and artwork read in the browser as in the detailed demo, side
bars per side, checks in plain words, approval 1 of 3
- price with the curve, itemised lines folded under one summary, lead time
as two bars (approvals, then the 7 to 9 week quote)
- fan funding: goal, break-even and what the artist keeps, money rules;
the campaign on a phone with a pre-order ticker, funded or missed ends,
production timeline with the artist's approvals, updates feed
- record passport for one delivered copy (stamper, press, cycle time and
side; stage dates; optical inspection and sampled audio), per
traceability.md and quality-automation.md, IDs simulated; repress card
- "Investor notes" switch with the business case per step (market
research, vault, short-run economics and the Thai price gap, plant-owned
vs broker and the Qrates lesson, traceability and represses); guided
tour of about a minute (#tour, #notes in the URL)
- light/dark theme shared with the other pages; phone layout with a
bottom bar
Same price list (demo-0.1) and stage table as artist-order.html, so the
defaults reproduce the artist platform example: 37,836 THB per title,
232 THB per copy at 100, break-even 41, goal 100, 548 THB kept a copy.
artist-platform.md: investor demo paragraph. traceability.md: the record
passport as the per-copy customer view. README bullet and layout line,
site DEMOS line and landing-page entry.
Most people the team talked to in Haarlem were strongly interested in the
full-traceability approach. For Sibert it was one of the reasons to talk to
us at all; without it their representative would strongly advise against
the plan, and seeing buildfor.life's development and data work convinced
him the project comes from the right direction.
Exhibitor briefing gets an "After the show" section (feedback, what has
been filed since); traceability.md opens with the market signal; roadmap
item 1 notes it as supply-side evidence, with buyer prices still missing;
README project status updated (show attended, Payap lead).
New docs/digital-factory.md: every system needed for environmental,
machine, QC and genealogy data to land in one database keyed to one
record identity. Standing decision: all services run on NixOS machines
declared and deployed as a single clan.lol inventory (mesh, backups,
host monitoring, secrets from clan services).
Covers machine list and roles, VLAN zoning, Telegraf/MQTT acquisition
source by source with the RFQ clause for each, environment sensor zones,
QC instrument integration paths, the factory application modules and
entities, alerting tiers, backup and retention, security, procurement
clauses, build order aligned with the roadmap phases, rough cost and
open questions.
README index and layout tree updated; roadmap item 17 and the
traceability spec link to the new document.
grabowski