Security Architecture & Trust Boundaries
DOCCAD's security model is designed around a fundamental premise: the published documentation is a static build artifact with zero runtime server footprint. Attack vectors targeting live application servers, database injection, or serving-time LLM jailbreaking are eliminated by construction.
The Six Trust Zones
DOCCAD divides the documentation lifecycle into six distinct trust zones:
Boundary Crossing Invariants
- Z0 -> Z2 (Input to Context): User questions enter prompts purely as delimited string data (
<<<EVIDENCE-DATA). - Z2 -> Z3 (CI to Cloud): Only content explicitly classified as public may be transmitted to cloud providers.
- Z2 -> Z4 (Private Tasks): Tasks marked
privacy: privateare hard-pinned to local execution. Cloud fallback is prohibited. - Z3/Z4 -> Z1 (Model Output to Repo): Generated text must pass schema validation and is persisted only through PR branches requiring human review.