Inference core
Adaptive ensemble engine Severity, continuity, recovery windows, and mission pressure scoringAdmin CMS
Operate the studio like a product.
Sign in to manage brand copy, projects, editorial content, leads, and account security from one place.
Authenticated
Architrov Nova-Operative (ANO) Control Room
Auth active
SQLite online
CMS writable
Model surface
Graphs, engines, and guardrails should remain visible while operators work.
Risk model
Confidence lattice Feature weighting, uncertainty bands, and escalation traceabilityGraph mesh
Dependency network Facilities, corridors, suppliers, substations, ports, and infrastructure lanesPolicy compiler
Guardrail state Approvals, response windows, delivery posture, and escalation controlsRuntime posture
Live operators
Inference, graph, evidence, and channel controls remain visible during active operations.Decision trace
Auditable
Signals, constraints, and dispatch actions stay linked before execution and after delivery.Executive surface
Brief-ready
Leadership outputs, receipts, recovery posture, and recommendation status stay attached to runtime state.Scenario library
Persisted operating scenarios and dependency graphs
Dependency graph
Service, supplier, and facility dependency map
Operations layer
Geospatial operating picture and time-sequenced incident rail
Geospatial board
Facility and supplier theater
Decision pack
Generate executive and operator briefings from a saved scenario
Run history
Stored outputs
Delivery control plane
Durable jobs, provider health, attempts, and audit history
Outbox
Scenario delivery jobs
Selected delivery
State, reroute, cancel, retry
Provider health
Pause and resume adapters
Attempts
Execution history
Webhook receipts
Provider delivery confirmations
Audit
Immutable operator and system events
Environment
Runtime configuration and optional provider keys
No key required for current engine
The adaptive ensemble scenario engine, dependency graph, SQLite persistence, and admin workflows run locally without external API keys.
Typical future keys
`OPENAI_API_KEY`, `MAPBOX_TOKEN`, `WORKOS_API_KEY`, `RESEND_API_KEY`, and sector-specific intelligence feed credentials if you add live external signals.
Local file
The server will read optional runtime settings from `.env.local` at the repo root before startup.
Studio content
Public-facing copy and content blocks
Projects
Featured work and case studies
Lead pipeline
Inbound project briefs
Security