Deploy test site / deploy (push) Successful in 53s
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.
75 lines
3.8 KiB
Markdown
75 lines
3.8 KiB
Markdown
# Process Logging and Traceability
|
|
|
|
Every step of production is logged continuously, so that every record is
|
|
traceable end to end for the customer. This is a set requirement, and it is
|
|
the core specification for the factory software this repository will
|
|
eventually host.
|
|
|
|
It is also the part of the plan the industry responds to. At Making Vinyl
|
|
Europe 2026 most people the team talked to were strongly interested in it,
|
|
and Sibert's representative named it as a reason to work with a newcomer
|
|
he would otherwise have advised against building a plant; buildfor.life's
|
|
development and data work settled the question for him (see the
|
|
[exhibitor briefing](suppliers/making-vinyl-europe-2026-exhibitors.md#after-the-show)).
|
|
|
|
## What a customer can trace
|
|
|
|
For any order, the customer can follow the full chain:
|
|
|
|
1. **Audio intake**: file received, checksums, versions, who handled it,
|
|
approval trail
|
|
2. **Mastering**: session log, engineer, settings, customer approvals
|
|
3. **Cutting**: lacquer IDs, lathe parameters, stylus used, inspection
|
|
result
|
|
4. **Galvanics**: silvering and plating batch IDs, bath chemistry logs,
|
|
father/mother/stamper genealogy (which stamper came from which mother
|
|
from which father), or the external stamper supplier and batch if bridged
|
|
5. **Pressing**: press ID, operator, shift, mold and stamper IDs, cycle
|
|
parameters (temperatures, pressures, cycle times), PVC compound lot and
|
|
virgin/recycled mix, label lot
|
|
6. **Quality control**: test pressing approvals, inspection results, reject
|
|
counts and reasons (the automated instrument layers feeding this are
|
|
specified in [quality automation](quality-automation.md))
|
|
7. **Finishing and packaging**: trimming, sleeving, carton lot, packaging
|
|
partner batch
|
|
8. **Fulfillment**: warehouse location, shipment or dropshipping consignment,
|
|
carrier tracking per end customer
|
|
|
|
## Principles
|
|
|
|
- **Log at the source**: machine data comes from the machine (the presses
|
|
and the plating rectifiers expose PLC data; the AD12 supports remote
|
|
monitoring), not from manual transcription. Manual steps get simple
|
|
operator check-ins, not paperwork.
|
|
- **Batch and genealogy first**: every physical artifact (lacquer, father,
|
|
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.
|
|
- **Environment attached**: the whole-factory HVAC monitoring (temperature,
|
|
humidity, PM per zone) is logged on the same timeline, so any production
|
|
window can be correlated with plant conditions.
|
|
- **Immutable and retained**: logs are append-only and retained for the
|
|
life of the customer relationship; stamper genealogy is retained as long
|
|
as the archive holds the metal parts.
|
|
- **Customer-facing view**: traceability is a product feature, not an
|
|
internal file. Customers get a per-order view (portal or report) covering
|
|
the chain above, without exposing other customers' data. The investor
|
|
demo [make a record](make-a-record.html) shows the per-copy version a
|
|
fan reaches from the code printed on the sleeve, the **record passport**:
|
|
stamper, press, cycle time and side, with the stage dates and the
|
|
inspection result (IDs simulated).
|
|
|
|
## Open design work
|
|
|
|
- Data model for batch genealogy across all eight steps
|
|
- Which PLC/machine interfaces each vendor exposes (ask Newbilt, Pheenix
|
|
Alpha, and Digital Matrix during procurement, before purchase)
|
|
- Retention, backup, and PDPA handling for operator-linked records
|
|
- Whether test-pressing approval workflows live in the same system from day
|
|
one
|
|
|
|
This system should be specified alongside equipment procurement: machine
|
|
data access is a purchasing requirement, not an afterthought. The systems
|
|
that implement this specification (machines, networks, collectors,
|
|
database, application) are planned in [digital-factory.md](digital-factory.md).
|