[BRAND +
IDENTITY]
The first door. Build the language before filing any work into it.
Open the first outward-facing channel. Establish the collective's vocabulary — dossier, signature, redaction, strike bar — before filing a single piece of actual work into it. Prove the system can hold content before it has to.
This transmission is therefore recursive. The case file you're reading is itself one of the artifacts it produced. The landing page, the identity spec, the corruption studies — all of them exist because of TX.001, and TX.001 only exists because they do.
Significant Machine pays the rent. The corporate work is clean, legible, approved. What it doesn't have room for is everything you're looking at right now — the corruption, the disturbance, the refusal to read as agency.
GCC needed its own surface — not a portfolio, not a studio site. A place where the briefs come from the collective, the guardrails are optional, and the work is built to disturb the feed instead of fit into it. TX.001 is that surface.
Every pattern established here becomes the template for TX.002, TX.003, and every node page filed downstream. That's why this file matters out of proportion to its output — it's the grammar, not the sentence.
DEPENDENCIES
- Identity System v1.0REF.002
- design-taste-frontend.mdSKILL
- emil-design-eng.mdSKILL
- JetBrains MonoTYPE
- Significant Machine workstreamFIREWALLED
UNSHIPPED / QUEUED
- Standalone SVG logo filesQUEUED
- Poster / print surfaceQUEUED
- GCC / SM firewall pageQUEUED
- Favicon / app icon systemQUEUED
- XXXXXXXXXXXXXXXXCLASSIFIED