[!IMPORTANT]
TL;DR: Cytoplex is the home of CAP (Controller-Authority Protocol), the hard safety and authority boundary that governs everything Yar does. It is a standalone protocol (its own spec, conformance suite, and future standalone repo) that is integrated into Yar as the guard between the model and any action. If Yar is the navigator, Cytoplex is the rulebook that says which moves are allowed.
Cytoplex is a Yar component, nested at docs/cytonome/yar/cytoplex/. It defines and documents CAP, the protocol that:
CAP ships in two profiles: CAP-Lite (the lightweight profile Yar's MVP uses) and CAP-Med (a stricter clinical profile). The v0.1 protocol covers the Directive lifecycle, Guard decisions, refusal messages, execution reports, decision records, the audit chain, Ed25519 / JWS / DSSE / in-toto signing, and HTTP and gRPC transport bindings, with a passing conformance suite.
| Dimension | How it works |
|---|---|
| Standalone | CAP has its own specification (spec/), conformance and hardening tests, benchmarks, threat model, and a planned extraction to a standalone repo (github.com/cytognosis/cap). Other agents and organizations can adopt CAP without Yar. |
| Integrated with Yar | Yar runs CAP-Lite as the boundary before model routing and before any external write. See the Yar master §8 Safety and the architecture index. Nothing leaves the device or hits a tool without passing the Guard. |
| Platform tie-in | CAP is the Cytognosis platform's safety primitive (the open-science / Apache 2.0 half of the bifurcation). Cytoplex is its documentation home. |
| Area | Path | What is in it |
|---|---|---|
| Revision plan & deep-dive | overview.md | Current CAP scope, gaps, v0.2 proposed scope, phased plan, target standalone package structure. |
| Formal spec | spec/ | The narrative specification: 01_foundations → 07_profiles_roadmap, plus architecture.md, claims.md, appendix_schemas.md, conformance, and release gates. |
| Consolidated baseline | v1-baseline/00_INDEX.md | A single consolidated v1 baseline (status, foundations, architecture, primitives, security, integrations, conformance, schema appendix, examples). |
| Security | security/ | Threat model, security review, KMS/HSM, findings tracker. |
| Conformance & quality | compliance/ · quality/ · interop/ | Reviewer checklists, rubrics, report templates, interop reports. |
| Benchmarks | benchmarks/ | Mobile latency budget for CAP v1. |
| Research lineage | research/ | CAP comprehensive reference and protocol assessment. |
../yar-master-features-requirements.md §8.../architecture-index.md.../product-implementation.md.§4A.../sensors/ is governed by CAP (per-sensor consent, on-device-by-default).[!NOTE]
ADHD-friendly variant: a simplified reading copy of this overview lives at README-vault.md (surfaced in the Obsidian vault via the symlinked docs repo). Edit this spec file; the vault variant links back here.