Signal Intelligence reads the moat (the 14) · Control routes the next move · Production builds: System → Line → Asset → Station · Engine Objects trace the runtime · Contract bounds it · Map navigates it · Labels show it · Smoke Test proves the loop.
Build unit = 1 deliverable = 1 Asset + its Station graph. The moat is NOT the machine — the machine serves the signal layer. The Engine (GHL) is a black box to MCP/API, so Linear carries the visibility it can’t give.
The 4 planes Signal → Control → Production → Proof — the loop
① Signal IntelligenceSensor → Signal (the 14-moat) → Signal Set / Pulse → Gap → PainReads what changed. The moat — judgment, not tools.
② ControlAxis → Router → Rule → GateDecides the next move (System / variant / message / suppress / escalate / STOP).
③ ProductionSystem → Line → Asset → Station · traced to Engine ObjectsBuilds the output. (The diagram below.)
④ Proof / StateSmoke Test → State → Trace → Receipt → DashboardVerifies the loop. Done needs live/readback proof.
Production plane System → Line → Asset → Station · Engine Objects branch off · all converge at Smoke Test
container (System / Asset) Line (lane) Station (step) Engine Object (runtime) Smoke Test (gate) blocks → Smoke Test
Dashed orange = blocks → Smoke Test (real Linear relations, not text). Concrete nodes = the Revenue Root System instance (FW-13). The shape is identical for every System — that is Goal 2.
The 2 goals the yardstick every node is measured against
Goal 1 — dependency-visible + non-inventedArrive at any node and SEE its up/down dependencies — Contract, Line, Stations, Engine Objects. Never re-derive, never invent. The Engine Object layer carries the GHL dependencies MCP can’t read.
Goal 2 — reusable + trackableSame model every System (reusable) + filter state by label axis in 4 months instead of rereading (trackable). Proven + tracked nodes graduate to dynamic workflows.
The production layers what each node IS · its Linear primitive · its rule
Layer
Is
Linear primitive
Rule
System
A packaged offer / client mechanism
Linear Project (inside a Core)
Container only — Contract + Map + Milestones. NOT where work is produced.
Line
A production path / lane
Issue (under the System)
5.0 lean: SELL · CHECKOUT · OFFER OUTPUT · SMOKE TEST. Assets hang under it.
1 skill step = 1 Station. Never group. Output in the comment.
Engine Object
A runtime object in an Engine
Issue (exact name in title)
Only when shared / risky / breaks >1 System. The GHL-blindness substitute.
Smoke Test
The launch-readiness gate
Issue (Assets block it)
No Asset claims launch alone. Proof converges here.
🔒 Core·Diagaxis / Core·Client lock
OFFER OUTPUT = the Core·Diagaxis promise + handoff. The client-installed build = Lines + Stations in Core·Client. Never call a Line “Delivery Journey” — that’s the Client-Facing Journey (end-customer experience), not a Line.
The label-axis stack labels are filters, NOT object names
Runtime objects get Engine Object cards (exact name in title), not labels. Labels stay queryable axes. Filter e.g. platform:ghl + exist:needs-readback = every GHL object still to verify.
Family
Values
Axis
runtime:
workflow · tag · custom-field · custom-value · route · webhook · form · agent · prompt · stripe-product