Public architecture must not become operational authority
Architecture, evidence and simulations may be public while private execution, memory and credentials remain unreachable from the public platform.
securityarchitectureboundary
Abrir →Engineering Knowledge Base 2
Ingeniería
ADRs, architecture notes, experiments and postmortems connected back to the public graph.
Generation, approval, promotion and release are separate authorities
Creative pipeline state is modeled explicitly so technical validity and internal promotion cannot silently grant publication authority.
governancereviewrelease
Abrir →Deterministic state remains authoritative over model-assisted language
Replayable state transitions remain authoritative while generated language is treated as a presentation and narrative layer.
determinismreplaygames
Abrir →Camera language as a gameplay variable
Perspective, framing, distance and occlusion are compared as repeatable gameplay variables rather than fixed presentation choices.
cameragameplayhorror
Abrir →Durable review state for creative operations
Candidate identity, review decisions, technical QA and publication gates are represented as durable state rather than inferred from files alone.
creative-opsreviewevidence
Abrir →Explainable role-based model routing
Routing is represented as role classification, provider candidates, evidence gating and a trace rather than a single opaque model choice.
routingmodelsevidence
Abrir →Model intent is not system authority
Sensitive local operations remain behind explicit policy and approval boundaries instead of being authorized solely by generated model intent.
local-firstapprovalsecurity
Abrir →Atlas 12.0 production certification hardening
The 12.0 release gate exposed production-only CSP, asset and Lighthouse issues; each was corrected without reducing the release thresholds before the immutable tag was created.
releaselighthousepwacsp
Abrir →Exactly one production workflow may create immutable site release tags
Deployment, production verification, certification and immutable tagging remain ordered gates; legacy tag automation is read-only and cannot create or move tags.
releasegovernanceprovenance
Abrir →Public Platform 13.0 production certification
The certified production baseline passed production E2E, three-sample Lighthouse across eight routes, release-certificate creation and immutable tag verification without reducing thresholds.
releaseproductionlighthousecertificate
Abrir →