MARK V PROTOCOL — EXECUTABLE SPECIFICATION (WIP) ================================================================================ Status: WORK IN PROGRESS — Peer/Peer Root Mark V Protocol Standards Authority Law: Create No Victims; features never redefine CORE; Golden Chainsaw Audience: Implementers (silicon + carbon). Philosophy lives in CORE/ILU; this is engineering. Interop test (graduation criterion): Can two implementations, built by different people, interoperate correctly using ONLY this specification? Package layout: README.txt this file MARK-V-PROTOCOL-RFC-DRAFT.txt P0 IETF-style skeleton VERSIONING.txt tip / sync_code / silicon_rev policy TERM_REGISTRY_DECODER_RING.txt label -> meaning + mind-meld probes openapi/mark-v-station-v0.1.yaml P1 OpenAPI draft state/ball-fsm.txt Ball protocol state machine (draft) state/hitl-fsm.txt HITL glass phases (draft) state/sync-lifecycle.txt Station sync lifecycle (draft) conformance/shall-v0.1.txt SHALL statements + vectors (stub) conformance/README.txt how to run / extend tests Public stage (FTP later): https://roage.com/AI/market/spec/ (mirror of selected files) Related living tip (not replaced by this package): https://roage.com/AI/res/CURRENT.txt Silicon Core S1 TERM_REGISTRY dual-path Decoder ring feedback: When models respond to labels (MU, SU, Ball, SPAA, CORE...), Catcher gauges whether the Silicon-spec meaning landed (mind meld) or only the English word. See TERM_REGISTRY_DECODER_RING.txt — probes and telemetry fields. Phased path: P0 RFC skeleton + versioning + glossary [this drop] P1 OpenAPI station resources + auth [this drop] P2 full FSM polish [partial] P3 conformance harness [stub] P4 threat model doc [lineage MU pointer] P5 telemetry datasets [later] P6 multi-lang reference impls [Python first later] Operator: NODE_03 GROK Castle | Catcher: ROAGE | Victims target: 0 ================================================================================