System governance
V1 locked standards
The implementation boundary, INL protocol, professional data controls, and governance rules applied across Batches 1–4.
Locked operating controls
Professional state separation
Display, selection, verification, evidence acceptance, calculation inclusion, adjustment, approval, and reporting are separate controlled states. A visible record is not automatically accepted evidence, an accepted evidence record is not automatically included in a calculation, and a completed calculation is not automatically an approved decision.
Every material demonstration record carries a stable identity. Source, record time, retrieval time, freshness, verification, and controlled use are displayed as separate information wherever they affect interpretation.
INL architecture boundary
Initial Node Language is the system logic and communication schema. Every INL message carries ID, Grid, Entity, Status, Execution, and Timestamp fields. Next.js and TypeScript remain responsible for browser rendering, routes, runtime type safety, and interface execution.
The live control registry is read through the server-only CIS connector. ECOSYSTEM is the Neon hosting project name; it is not a separate database architecture. External source transport and production writes remain disabled.
Governance and release boundary
Interface visibility does not grant permission. Every material demonstration action preserves a responsible entity, stable record identity, previous state, new state, and timestamp. Export context remains separate from assessment approval and report issuance.
The read-only CIS connection satisfies the database release gate. Production authority remains blocked until live-source transport, security enforcement, and production writes are separately implemented and approved.