Objective
Establish the trustworthy baseline for ZASI — Zero-Entropy Autonomous Superintelligence Infrastructure v33 before adding more autonomous capability.
Source-grounded findings
backend/server.py is the active standard-library HTTP/WebSocket server and allows ZASI_API_KEY to be empty.
src/api_server.py is a second HTTP server with a hard-coded default bearer token and public bind behavior.
main.py still prints v30/168-subsystem status while README/docs advertise v32/176.
/api/status, telemetry, README badges, and several JARVIS responses use hard-coded operational claims such as 176 Online.
- Current docs mix implemented modules, simulations, research prototypes, and speculative capability names.
Scope
- Select one authoritative ASGI application as the production runtime owner.
- Move legacy servers behind explicit compatibility/development adapters.
- Add dependency-aware
/ready and /health semantics.
- Define typed immutable runtime configuration and fail closed for production auth/CORS/bind errors.
- Add capability maturity + runtime state + evidence state to the subsystem registry.
- Replace hard-coded
all online/operational claims with registry-derived evidence-backed state.
- Normalize version/subsystem-count reporting across CLI, API, installer, README, changelog, and cockpit.
Acceptance criteria
Priority
P0 / release blocker for v33.
Objective
Establish the trustworthy baseline for ZASI — Zero-Entropy Autonomous Superintelligence Infrastructure v33 before adding more autonomous capability.
Source-grounded findings
backend/server.pyis the active standard-library HTTP/WebSocket server and allowsZASI_API_KEYto be empty.src/api_server.pyis a second HTTP server with a hard-coded default bearer token and public bind behavior.main.pystill prints v30/168-subsystem status while README/docs advertise v32/176./api/status, telemetry, README badges, and several JARVIS responses use hard-coded operational claims such as176 Online.Scope
/readyand/healthsemantics.all online/operationalclaims with registry-derived evidence-backed state.Acceptance criteria
176 onlinewithout evidence for each relevant capability.simulated,research_only,unavailable, orunknownas appropriate.Priority
P0 / release blocker for v33.