green rose systems

“growth, forever”
A Software Studio · Established 2026

traveler

A factory-execution system for building complex hardware.

01  ·  description

traveler is a prototype in TypeScript that models a manufacturing execution record system. The runtime reads a single fixed contract of sixteen registry YAML files. Each operation it runs, each event it emits, each record it holds is declared in that contract.

132 operations, 136 events, 43 records, 16 state machines, 33 authorization rules registered. 129 of 132 operations are built; three are unbuilt, each with a recorded reason in the code. The specifications were reverse-engineered from public sources (industry standards, published architectures, job postings, open-source projects, regulatory guidance) using a language model and Signal-Driven Development.

Three governing document sets are closed. A nine-document founding stack. A receiving-evidence boundary where 15 of 15 criteria pass. An access-and-visibility boundary where 18 of 18 criteria pass or pass-in-part.

TypeScript on Node. In-memory and node:sqlite storage drivers. 38 scenarios covering 779 steps. 432 tests across 58 files. Bench 29/29 on both drivers. Backend gate exit 0 with fifteen durability proofs. Whole-bench cross-driver check over 37 scenarios: pass.

What it is not: no live floor UI (47 wireframes exist under canvas/), no device integration (scanners, printers, and machine adapters are named in the vocabulary but have no driver code), no scheduling or MRP, no authentication, no ERP integration. Apache 2.0.

02  ·  repository

github.com/laffeyp/traveler

Contact

We’re open to a small number of new engagements. Write with a short note about the work and the timeline.

info@greenrosesystems.com