coulomb/maturity-engine
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Align INTENT and SCOPE with security-layer-model v0.7

Browse source 
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
This commit is contained in:
tegwick 2026-08-29 11:56:26 +02:00
parent 8545e229eb
commit bf0c7d98fd
5 changed files with 800 additions and 38 deletions
Download patch file Download diff file Expand all files Collapse all files

29
README.md
View file

@ -3,26 +3,31 @@
**Computes, deterministically, how far a thing has progressed against declared
criteria and submitted evidence — and keeps the history of that progression.**
An Engine in the NetKingdom security layer model. 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.
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 conformance states and gap register,
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,
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.
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. If a level
determines an outcome it reaches `access-engine` as an input claim, never by a
consumer branching on a fetched level. Compiled data that determines an outcome
is still deciding.
**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).
This repository is seeded, not yet an engine surface. See [INTENT.md](INTENT.md)
and [SCOPE.md](SCOPE.md). The work to stand up the surface is `MAT-WP-0001`.