feat(posture): add deterministic feedback proposals
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02929-244b-7391-b933-c04010e8eedb
This commit is contained in:
tegwick 2026-08-23 13:16:34 +02:00
parent dc8da422f8
commit cfc9e7d0cb
19 changed files with 1428 additions and 16 deletions

View file

@ -0,0 +1,47 @@
# Posture feedback estate baseline
Date: 2026-08-23
Workplan: NK-WP-0031
Mode: read-only, proposal-only
## Evaluation
The proposed Posture Feedback v0.1 evaluator was run with:
- `as_of`: `2026-08-23T11:05:14Z`
- `horizon_days`: `30`
- `fail_on`: `none`
- inputs: the tenancy declarations in `adaptive-pricing`, `audit-core`,
`flex-auth`, `ops-warden`, `railiance-platform`, `rapp-postgres`, and
`tenant-engine`
The report digest was
`sha256:66174f08cf5feb1e5618477a374975100a4712bcaa354fcb1b1702103482b6c1`.
It contained 34 proposals: one high, six medium, and 27 low. All 34 owners were
`unknown`, which is the required result because these declarations do not yet
carry the new authoritative `responsible_repo` fields.
## High finding
`NKFB-c08b78e82248bf27` reports `audit-core` E2 evidence freshness as
`unknown`. The declaration describes the Whitehat run and its 24-hour validity
in prose but does not yet supply the machine-readable `evidence_freshness.E2`
authority. NetKingdom did not infer timestamps, ownership, scope, or a
replacement action from that prose.
Adoption was routed to `audit-core` in State Hub message
`874e5fa5-e05c-4b1a-a915-26c4dba07b87`.
## Declaration validation errors
The `railiance-platform` declaration did not enter evaluation because its
`apps-pg` service declares current R2 and V1 without the evidence entries
required for current non-zero levels. Remediation was routed to
`railiance-platform` in State Hub message
`d65f8383-bdab-488e-a36f-f8cabd8a5f65`.
## Safety result
The evaluator changed no declaration, policy, workplan, State Hub record, or
runtime. The two State Hub messages above were explicit operator-process
handoffs after inspection of the report; they were not emitted by the tool.

View file

@ -145,3 +145,13 @@ deterministic provider pins, trust ordering, responsibility mapping, and
readiness handoff without executing provider actions. G1 remains open for the
lightweight SSO path until the KeyCape/Railiance owners publish conformant C1
and C2 declarations.
NK-WP-0031 subsequently implemented the first bounded G2 increment: proposed
Posture Feedback v0.1 canon and a deterministic evaluator that turns explicit
review dates, evidence freshness, implemented-but-unevidenced controls, and
declared gaps into owner-routed remediation proposals. Time is an explicit
input; missing ownership or freshness resolves to `unknown`; and the report
forbids external, declaration, and policy writes. G2 remains open because the
tool does not create work, change policy, close remediation, or consume runtime
telemetry autonomously. Those powers require separate authority, rollback, and
review decisions.