Plates

A plate is one pipeline, drawn as a stamp. The drawing is the thing a person reads: an input layer, a processing layer, an output layer, and the arrows between them.

0xRay is a three-subsystem autonomous engine. The suit is the wear. Inference remembers. External Governance judges. The Autonomous Engine runs the work. A foundry is mills and hangars. When the window closes, the next session wakes with the job.

These files are the canonical stamps. The Docusaurus sidebar publishes them, and the npm package ships this directory. The worn reader walks up from dist/integrations/hooks/plates.cjs to docs-site/docs/plates/. One plate, one file.

The station card stays the short subsystem table. That table is the index still on disk after compaction. When the current intent names one pipeline, the card adds a single stock line, Plate: <id> — .xray/state/plates/<id>.md. Recall returns that one plate, and a compact can carry its schematic. Lessons stay episodes on signals. A plate is the machine. A lesson is what happened.

The markdown file is the source of truth for that stamp. When the pipeline changes, edit the plate. A worn project may hold a copy at .xray/state/plates/<id>.md. The copy is written only when that file is missing, so a local edit stays.

Plates have a type. A domain model plate shows how named parts fit. A state flow plate shows the stages one thing goes through.