maturity-engine/README.md

# maturity-engine

**Computes, deterministically, how far a thing has progressed against declared
criteria and submitted evidence — and keeps the history of that progression.**

An Engine (PIP) in the NetKingdom security layer model v0.7. Given the same
criteria and the same evidence it returns the same level; that property is
what makes it an engine rather than an opinion. It supplies facts a decision
consumes as claims. It does not decide.

> **gate-house judges and proposes. maturity-engine computes and remembers.**

It exists because NetKingdom is full of maturity that nothing owns — the Canon's
ASM-0…ASM-6 ladder, the layer model's four conformance states and gap register,
ops-warden's delegated lanes, kings-guard's advisory-until-gaps-close posture,
PEP stance maps parked in the statute, the State Hub's DoX quality debt — and
because `gate-house` was catalogued as owning conformance review with no engine
to act through, the same defect kings-guard found for containment.

**Guardrail:** a maturity level must never gate a decision directly, and must
never be compiled into registry content. If a level determines an outcome it
reaches `access-engine` as an input claim or a versioned policy rule, never by
a consumer branching on a fetched level. Compiled data that determines an
outcome is still deciding.

**Scoring:** blocked-clean MUST NOT rank below conforming.

Maturity here is graded, evidence-based, open-ended, and revisable — levels can
fall when evidence expires. The closed, binary, replay-proof state machine of an
approval belongs to `approval-engine`; the two engines are deliberate opposites.

See [INTENT.md](INTENT.md) and [SCOPE.md](SCOPE.md). The claim contract is
[docs/claim-contract.md](docs/claim-contract.md).

```bash
python3 -m pip install -e ".[dev]"   # or: PYTHONPATH=src
make test
make check-layer
PYTHONPATH=src python3 -m maturity_engine bootstrap --at 2026-08-29T12:00:00Z
PYTHONPATH=src python3 -m maturity_engine review --subject kings-guard --at 2026-08-29T12:00:00Z
```
Initial commit 2026-08-28 20:28:58 +00:00			`# maturity-engine`

Seed INTENT and README maturity-engine computes a level deterministically from declared criteria and submitted evidence, and keeps the progression history. It owns model registration, evidence validity, level computation, the gap register, and capability readiness. It closes a defect in gate-house's own catalog claim: gate-house is catalogued as owning conformance review with no engine to act through, which is the standard section 9.1 problem kings-guard raised for containment. Staff acts only through Engine APIs. Carries one guardrail from day one: a maturity level must never gate a decision directly, or the estate acquires a second decision point by the graded back door. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 2564823@bnt-lap001 Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9 2026-08-28 22:34:02 +02:00			`**Computes, deterministically, how far a thing has progressed against declared`
			`criteria and submitted evidence — and keeps the history of that progression.**`

Align INTENT and SCOPE with security-layer-model v0.7 Declare Engine/PIP in INTENT frontmatter against the accepted statute and working companion v0.2. Add SCOPE as the evidenced seed boundary, a demand review of the remaining seed-to-engine gap, and MAT-WP-0001 to stand up the assessment surface, gap register, and stance-map inventory the catalog already assigns. Assistant: grok Assistant-Session: 01a04ceb-150e-7e80-a542-ec8b1372e164 2026-08-29 11:56:26 +02:00			`An Engine (PIP) in the NetKingdom security layer model v0.7. Given the same`
			`criteria and the same evidence it returns the same level; that property is`
			`what makes it an engine rather than an opinion. It supplies facts a decision`
			`consumes as claims. It does not decide.`
Seed INTENT and README maturity-engine computes a level deterministically from declared criteria and submitted evidence, and keeps the progression history. It owns model registration, evidence validity, level computation, the gap register, and capability readiness. It closes a defect in gate-house's own catalog claim: gate-house is catalogued as owning conformance review with no engine to act through, which is the standard section 9.1 problem kings-guard raised for containment. Staff acts only through Engine APIs. Carries one guardrail from day one: a maturity level must never gate a decision directly, or the estate acquires a second decision point by the graded back door. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 2564823@bnt-lap001 Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9 2026-08-28 22:34:02 +02:00
			`> gate-house judges and proposes. maturity-engine computes and remembers.`

			`It exists because NetKingdom is full of maturity that nothing owns — the Canon's`
Align INTENT and SCOPE with security-layer-model v0.7 Declare Engine/PIP in INTENT frontmatter against the accepted statute and working companion v0.2. Add SCOPE as the evidenced seed boundary, a demand review of the remaining seed-to-engine gap, and MAT-WP-0001 to stand up the assessment surface, gap register, and stance-map inventory the catalog already assigns. Assistant: grok Assistant-Session: 01a04ceb-150e-7e80-a542-ec8b1372e164 2026-08-29 11:56:26 +02:00			`ASM-0…ASM-6 ladder, the layer model's four conformance states and gap register,`
Seed INTENT and README maturity-engine computes a level deterministically from declared criteria and submitted evidence, and keeps the progression history. It owns model registration, evidence validity, level computation, the gap register, and capability readiness. It closes a defect in gate-house's own catalog claim: gate-house is catalogued as owning conformance review with no engine to act through, which is the standard section 9.1 problem kings-guard raised for containment. Staff acts only through Engine APIs. Carries one guardrail from day one: a maturity level must never gate a decision directly, or the estate acquires a second decision point by the graded back door. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 2564823@bnt-lap001 Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9 2026-08-28 22:34:02 +02:00			`ops-warden's delegated lanes, kings-guard's advisory-until-gaps-close posture,`
Align INTENT and SCOPE with security-layer-model v0.7 Declare Engine/PIP in INTENT frontmatter against the accepted statute and working companion v0.2. Add SCOPE as the evidenced seed boundary, a demand review of the remaining seed-to-engine gap, and MAT-WP-0001 to stand up the assessment surface, gap register, and stance-map inventory the catalog already assigns. Assistant: grok Assistant-Session: 01a04ceb-150e-7e80-a542-ec8b1372e164 2026-08-29 11:56:26 +02:00			`PEP stance maps parked in the statute, the State Hub's DoX quality debt — and`
			because `gate-house` was catalogued as owning conformance review with no engine
			`to act through, the same defect kings-guard found for containment.`
Seed INTENT and README maturity-engine computes a level deterministically from declared criteria and submitted evidence, and keeps the progression history. It owns model registration, evidence validity, level computation, the gap register, and capability readiness. It closes a defect in gate-house's own catalog claim: gate-house is catalogued as owning conformance review with no engine to act through, which is the standard section 9.1 problem kings-guard raised for containment. Staff acts only through Engine APIs. Carries one guardrail from day one: a maturity level must never gate a decision directly, or the estate acquires a second decision point by the graded back door. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 2564823@bnt-lap001 Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9 2026-08-28 22:34:02 +02:00
Align INTENT and SCOPE with security-layer-model v0.7 Declare Engine/PIP in INTENT frontmatter against the accepted statute and working companion v0.2. Add SCOPE as the evidenced seed boundary, a demand review of the remaining seed-to-engine gap, and MAT-WP-0001 to stand up the assessment surface, gap register, and stance-map inventory the catalog already assigns. Assistant: grok Assistant-Session: 01a04ceb-150e-7e80-a542-ec8b1372e164 2026-08-29 11:56:26 +02:00			`Guardrail: a maturity level must never gate a decision directly, and must`
			`never be compiled into registry content. If a level determines an outcome it`
			reaches `access-engine` as an input claim or a versioned policy rule, never by
			`a consumer branching on a fetched level. Compiled data that determines an`
			`outcome is still deciding.`

			`Scoring: blocked-clean MUST NOT rank below conforming.`
Seed INTENT and README maturity-engine computes a level deterministically from declared criteria and submitted evidence, and keeps the progression history. It owns model registration, evidence validity, level computation, the gap register, and capability readiness. It closes a defect in gate-house's own catalog claim: gate-house is catalogued as owning conformance review with no engine to act through, which is the standard section 9.1 problem kings-guard raised for containment. Staff acts only through Engine APIs. Carries one guardrail from day one: a maturity level must never gate a decision directly, or the estate acquires a second decision point by the graded back door. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 2564823@bnt-lap001 Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9 2026-08-28 22:34:02 +02:00
			`Maturity here is graded, evidence-based, open-ended, and revisable — levels can`
			`fall when evidence expires. The closed, binary, replay-proof state machine of an`
			approval belongs to `approval-engine`; the two engines are deliberate opposites.

Stand up the Engine/PIP surface for MAT-WP-0001 Declare layer.yaml, add a Python engine over a local SQLite store, and cover deterministic assessment, the §13 gap register, stance-map inventory, claim guardrails, and the gate-house review path with tests. Assistant: grok Assistant-Session: 01a04ceb-150e-7e80-a542-ec8b1372e164 2026-08-29 12:54:37 +02:00			`See [INTENT.md](INTENT.md) and [SCOPE.md](SCOPE.md). The claim contract is`
			`[docs/claim-contract.md](docs/claim-contract.md).`

			```bash
			`python3 -m pip install -e ".[dev]" # or: PYTHONPATH=src`
			`make test`
			`make check-layer`
			`PYTHONPATH=src python3 -m maturity_engine bootstrap --at 2026-08-29T12:00:00Z`
			`PYTHONPATH=src python3 -m maturity_engine review --subject kings-guard --at 2026-08-29T12:00:00Z`
			```