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 inspected N1 gate · 23 August 2026
9 of 11 grouped A–K requirements pass. Overall result: FAIL.
The latest N1 enforcement run keeps NousPolis at N0. Requirements I and J remain blocking and are now reported directly as FAIL: the required external integrity witness is absent, and the required principal-separated review artifact is absent. A future passing report would still not automatically advance maturity; a separate bootstrap maturity-transition disposition is required.
Technical provenance
- Snapshot date
- 23 August 2026
- Source branch
n1/normalization-r0.22- Source commit
ef93f0db98be661f3a0b96ff07cd1642c071675e- GitHub Actions run
32650741895- Normalization status
BLOCKED_GOVERNANCE- Evidence meaning
- This commit identifies the core-repository state evaluated by the latest inspected N1 enforcement run.
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 establish N1 maturity, external independence, evidentiary truth, legal authority, policy correctness, or authorization for 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, deterministic construction, protected mutation, and ordered-path behavior are tested.
Classification enforcement
PASSL5 floor, conservative default, and constructor guard pass.
Capability and security boundary
PASSFactory-bound provenance, 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; no missing probe bindings.
Release and integrity baseline
FAILThe local release hash and recoverable baseline pass for the inspected commit, but the complete externally witnessed commitment bundle is 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
FAILThe approved principal-separated review artifact is 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
PASSLocal enforcement files, Tier-2 chokepoint scan, hash-chain tamper detection, and loop bounds pass.
Additional normalization checks in the 23 August report
- Normalization module presence: PASS — 16 of 16 modules are present.
- Required governing pins: WARN — six governance pins remain absent.
- Constitutional genesis declaration: WARN — absent.
- Normalization adversarial-suite collection: FAIL because
pytestwas not installed in the gate job environment.
These L.* checks are not included in the 9-of-11 A–K count and do not create or imply N1 maturity.
Residual risks recorded by the latest 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 while the required external witness is absent.
- Required normalization governance pins and constitutional genesis are not yet adopted.
Public records: N1 enforcement requirements, 23 August evidence snapshot, independence rules, architecture adversarial-review disposition, and 17 August PDLS pilot record. The N1 gate result and the N0 implementation milestone are deliberately presented separately.