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