coulomb/maturity-engine
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Modelling, tracking and enabling maturity
9 commits 1 branch 0 tags 128 KiB
Find a file
tegwick 30236955c6 Apply GH-DEC-2026-017: INTENT.md governs, the sidecar is derived, no version 
- Remove standard_version from layer.yaml and INTENT.md frontmatter (§5, A12).
- Mark layer.yaml derived: true, derived_from: INTENT.md (§1, A11).
- Checker and tests change in the same commit: standard_version is no longer
  a required key (it is now rejected in either form), the derived marking is
  required, both layer values are checked against the closed four-token
  vocabulary, and the two forms are compared after an ASCII case fold (A9).
  A disagreement surviving the fold is reported as a finding.
- Nothing re-spelled: INTENT.md keeps "Engine", layer.yaml keeps "engine".

Scope check (§9.5 / GH-DEC-2026-017 §4): maturity-engine does not score
layer declarations anywhere. scoring.py grades gap-register conformance
states, and seed gaps concern capabilities, not §11 declarations, so no
non-§4 repository is graded. No scoring change required.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
2026-09-21 07:35:40 +02:00
docs Stand up the Engine/PIP surface for MAT-WP-0001 2026-08-29 12:54:37 +02:00
history Align INTENT and SCOPE with security-layer-model v0.7 2026-08-29 11:56:26 +02:00
scripts Apply GH-DEC-2026-017: INTENT.md governs, the sidecar is derived, no version 2026-09-21 07:35:40 +02:00
src/maturity_engine Stand up the Engine/PIP surface for MAT-WP-0001 2026-08-29 12:54:37 +02:00
tests Apply GH-DEC-2026-017: INTENT.md governs, the sidecar is derived, no version 2026-09-21 07:35:40 +02:00
workplans Stand up the Engine/PIP surface for MAT-WP-0001 2026-08-29 12:54:37 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-08-29 12:55:27 +02:00
.gitignore Stand up the Engine/PIP surface for MAT-WP-0001 2026-08-29 12:54:37 +02:00
AGENTS.md Stand up the Engine/PIP surface for MAT-WP-0001 2026-08-29 12:54:37 +02:00
INTENT.md Apply GH-DEC-2026-017: INTENT.md governs, the sidecar is derived, no version 2026-09-21 07:35:40 +02:00
layer.yaml Apply GH-DEC-2026-017: INTENT.md governs, the sidecar is derived, no version 2026-09-21 07:35:40 +02:00
Makefile Stand up the Engine/PIP surface for MAT-WP-0001 2026-08-29 12:54:37 +02:00
pyproject.toml Stand up the Engine/PIP surface for MAT-WP-0001 2026-08-29 12:54:37 +02:00
README.md Stand up the Engine/PIP surface for MAT-WP-0001 2026-08-29 12:54:37 +02:00
SCOPE.md Stand up the Engine/PIP surface for MAT-WP-0001 2026-08-29 12:54:37 +02:00
WORK-RECORDS.md chore(consistency): refresh work-record index after MAT-WP-0001 2026-08-29 12:55:39 +02:00

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 and SCOPE.md. The claim contract is docs/claim-contract.md.

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