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

Validate cadence contract and require functional MFA verification
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ea3-7939-7b63-8125-699f8b50bedd
This commit is contained in:
tegwick 2026-09-05 01:28:05 +02:00
parent d4d61b722e
commit 4e07d60ff1
34 changed files with 1640 additions and 364 deletions
Download patch file Download diff file Expand all files Collapse all files

27
tools/emission-cadence-profile/README.md Normal file
View file

@ -0,0 +1,27 @@
# Emission Cadence Security Profile Checker
This checker applies the NetKingdom security overlay in
`canon/standards/emission-cadence-security-profile_v0.1.md` only after the
declaration passes an explicitly supplied InfoTechCanon contract schema.
It deliberately contains no fallback copy of the generic schema. The event
classes passed with `--load-bearing`, `--rare-load-bearing`, and
`--attributive` come from the source's authoritative inventory; the checker
does not infer them from names, payloads, or observed traffic.
Run its tests with:
```bash
make emission-cadence-profile-test
```
Supply `../info-tech-canon/infospace/schemas/emission-cadence.schema.yaml`
with `--contract-schema`. The canon profile records its version and SHA-256.
Security fields are under each entry's `extensions.netkingdom` namespace.
The test suite runs contract integration tests directly against a sibling
InfoTechCanon checkout; these tests explicitly skip when it is unavailable.
The small unit-test schema is a test double, not a fallback contract.
The profile is proposed: current approval-engine and qonto-assistant owner
instances still require migration. Passing a worked example is not adoption.