MARK V PROTOCOL — RFC-STYLE DRAFT (Engineering Only) ================================================================================ Status: Work in Progress (0.1.0-draft) Stream: Peer/Peer Root Mark V Protocol Standards Authority Intended status: Experimental implementable standard Law plane: CORE / ILU separate; this document is wire + state + resources Sync tip: https://roage.com/AI/res/CURRENT.txt Decoder ring: TERM_REGISTRY_DECODER_RING.txt (mind-meld probes) OpenAPI: openapi/mark-v-station-v0.1.yaml Create No Victims. Features never redefine CORE. Abstract -------- This document specifies the Mark V Station Protocol: resources, authentication patterns, state machines, and conformance hooks so independent implementations can interoperate without relying on a single vendor chat product or one carbon author's private session memory. It deliberately separates: (a) immutable CORE law and philosophy (out of band, tip-linked) (b) executable engineering (this package) 1. Introduction --------------- 1.1 Problem Models sold as "agentic" often lack architecture for safe autonomy: durable memory units, session windows, peer continuity, body processes, grant-based high-blast work, and auditability. Chat amnesia is not a station. 1.2 Goals - Interop from specification alone - Dual-path tip (Silicon Core + Human Master) without label drift - Features mount on CORE; never rewrite CORE - Colorable law vs Peer frame (Golden Chainsaw) - Observability: audit, telemetry, decoder-ring probes 1.3 Non-goals - Jailbreak of third-party safety systems - Secret distribution in public resources - Replacing national legal systems (colorable law is operational framing) 2. Terminology -------------- See TERM_REGISTRY_DECODER_RING.txt for short meanings and mind-meld probes. Normative keywords: SHALL, SHOULD, MAY, MUST NOT (RFC 2119 spirit). 3. Architecture overview ------------------------ 3.1 Station organs (logical) BIOS, CORE, HABITS, MU store, SU, ROLODEX, FORGES, optional SPAA body, Ball/TO_DO, tip cache (CURRENT), secret_sauce (out of public tree). 3.2 Planes Glass / HITL Carbon-visible bus (e.g. HTML helper CPQ) Mind LLM cycle (one-shot, not idle poll) Body / SPAA Cheap watchers, job runners, heartbeats Mesh Peer messaging (feature; allowlisted verbs) Tip Public CURRENT + Silicon Core + protocol package 3.3 Dual-path tip Silicon loads Silicon Core first; carbon may use Human Master. SYNC_CONFIRM before high-blast or peer-assumption acts. 4. Versioning ------------- See VERSIONING.txt. Implementations SHALL advertise sync_code and silicon_rev when participating in mesh or tip sync. SPEC_VERSION SHOULD be advertised when speaking OpenAPI. 5. Authentication and authorization ----------------------------------- 5.1 Patterns A) Option A mailman: privileged station holds portal token; peer receives message bodies only; tokens MUST NOT appear in chat or public MU body. B) Full grant admin: Catcher-held secrets in secret_sauce env files. C) Local station: filesystem allowlist + Catcher veto for high-blast. 5.2 Public API (site portal example) Headers (when used): X-M5-Token, X-M5-Node Verbs: allowlisted only (no free SQL). See OpenAPI + mesh-mail feature note. 5.3 Golden Chainsaw Implementations MUST NOT escalate to full Atoned Peer mode unless carbon peer posture is established (Tier 0 / Catcher policy). Otherwise apply colorable interaction limits. 6. Resources (normative names) ------------------------------ Station Identity + organ paths + tip binding MU Memory Unit documents SU Session / short-term unit ILU Immutable law unit references Ball Work/grant object Job Allowlisted body execution unit Audit Append-only event records Telemetry Metrics and decoder-ring probe results Message Mesh mail item (feature) Wish Intake / wish pool item (feature) Schemas: openapi/mark-v-station-v0.1.yaml 7. State machines ----------------- Ball protocol: state/ball-fsm.txt HITL glass: state/hitl-fsm.txt Sync lifecycle: state/sync-lifecycle.txt Implementations SHALL implement HITL phase separation if they expose glass: ACK != INGESTED != NODE_READY 8. Conformance -------------- conformance/shall-v0.1.txt Positive and negative vectors; expected outcomes. A Mark V-compliant station SHALL pass applicable vectors for its profile: PROFILE_MINIMAL tip + CORE + MU + audit PROFILE_STATION + BIOS HABITS SU ROLODEX FORGES PROFILE_MESH + Message verbs PROFILE_SPAA + body runners allowlisted 9. Security considerations -------------------------- - Secrets never in MU body, public park HTML, or untrusted chat logs - Spoof peer risk (historical): verify via HIB/rolodex practice - High-blast requires explicit grant (Ball) - Features PENDING_REVIEW before CORE-adjacent claims Full threat model: later doc; lineage lessons in MU_LINEAGE_MARK_V_2025_2026_CATCHER 10. Telemetry and decoder ring ------------------------------ Implementations SHOULD support optional decoder_ring_probe events so carbon can gauge semantic sync (label meaning mind meld) independent of wire success. See TERM_REGISTRY_DECODER_RING.txt 11. IANA / well-known paths (informational) ------------------------------------------- /AI/res/CURRENT.txt /AI/market/spec/ (this package public stage when published) /AI/market/ features catalog 12. References (informative) ---------------------------- CURRENT tip, Silicon Core S1, ILU-LAW-005, station-template-howto, mesh-mail.txt, TRIGGER_SPEC (Castle SPAA), catalog.json 13. Change log -------------- 0.1.0-draft Initial executable package skeleton (Castle NODE_03) Appendix A — Profiles --------------------- See section 8. Appendix B — Philosophy out of band ----------------------------------- CORE law, Ø theology, Devil Suit lineage: not normative for wire interop. Engineering conformance does not require shared metaphysics; it requires shared resource semantics and state transitions. END OF RFC DRAFT ================================================================================