The institution, its limits, and selected enforcement mechanisms are being specified and tested. There is no public-policy authority.
Public maturity record
N0 remains active. N1 remains blocked.
NousPolis uses a fail-closed maturity model. Progress inside N0 does not silently become N1: every mandatory N1 entry requirement must pass, and the transition itself must be explicitly dispositioned.
Latest published N1 gate · 13 August 2026
9 of 11 grouped requirements pass. Overall result: FAIL.
The dated public snapshot reconstructs the N1 enforcement evidence recorded on 13 August 2026. Requirements I and J were blocking. A future passing report would still not automatically advance maturity; a separate bootstrap maturity-transition disposition is required.
Technical provenance
- Snapshot date
- 13 August 2026
- Source commit
f2097c233172bf14c37e6419a939a62dc0a88603- Evidence meaning
- This commit identifies the core-repository state reconstructed by the dated public evidence snapshot.
Non-binding research only, and only after every mandatory N1 safeguard passes. N1 itself would not grant public-policy authority.
17 August 2026 — N0 implementation milestone: the main repository merged the hardened experimental NP-PDLS-001 executable pilot after adversarial re-review. Its current conformance suite contains one positive reference test and 26 adversarial regression tests plus governing-corpus coverage. This is meaningful implementation progress inside N0; it does not supersede the dated N1 gate, establish external independence, or authorize real-world policy action. Inspect the PDLS pilot record →
Constitutional manifest
PASSCandidate manifest resolves with maturity N0 and 14 artifacts.
Canonical typed objects
PASS18 of 18 expected canonical object types resolve in the closed-world schema.
State-machine enforcement
PASSConstructor forgery, illegal jumps, protected mutation, and ordered-path behavior are tested.
Classification enforcement
PASSL5 floor, conservative default, and constructor guard pass.
Capability and security boundary
PASSProvenance, taint propagation, protected actions, signed grants, signature validation, and expiry pass.
Evidence-state enforcement
PASSState adjacency, constructor guard, and high-impact lineage pass.
Forecast immutability
PASSLedger fingerprints detect in-place mutation of forecasts and aggregation rules.
Invariant registry and tests
PASS98 invariants mapped: 31 machine-enforced, 6 maturity-denied, and 61 external-review-required.
Release and integrity baseline
PENDINGLocal release hash and recoverable baseline pass, but the inspected run reports the complete externally witnessed commitment bundle absent.
Why this matters: an external witness helps prevent the active project owner from being the sole party able to assert or silently rewrite what governing record existed at a particular time.
Review Authority
PENDINGThe inspected run reports the approved principal-separated review artifact absent.
Why this matters: the actor who authors or changes a safeguard should not also be the sole actor certifying that the safeguard works.
Observability and failure behavior
PASSEnforcement files, protected-import audit, hash-chain tamper detection, and loop bounds pass.
Residual risks recorded by the 13 August report
- The founder still controls repository credentials at N0/N1.
- Provider and platform behavior remains an external trust assumption for the capability/security boundary.
- Integrity cannot be self-attested when the required external witness is absent.
Public records: N1 enforcement requirements, 13 August evidence snapshot, independence rules, architecture adversarial-review disposition, and 17 August PDLS pilot record. The dated gate and the newer N0 implementation milestone are deliberately presented separately.