Evaluate declared emission cadence and close AUDIT-WP-0009 (T05)
The contract T05 waited on is published: info-tech-canon emission-cadence wire schema 0.1, contract digest b08b4d95fc4b0bd3. A source-owned declaration now travels as emission_cadence on the sender registration; expected-rate entries raise below_declared_cadence on /v1/stream-findings from the same counts /v1/reconciliation returns. heartbeat-or-reconciliation entries are validated and left to T04/T06. Records the observer evaluation of net-kingdom's local-identity declaration: structurally clean, not operationally evaluated, one heartbeat event_class mapping incompatibility. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 151986@bnt-lap001 Assistant-Session: ccd02b6b-80ae-48e5-8cad-9c8f74d21a67
This commit is contained in:
parent
3b7bedc8e0
commit
01468ffc41
8 changed files with 645 additions and 22 deletions
|
|
@ -4,12 +4,12 @@ type: workplan
|
|||
title: "Evidence-role conformance under Security Layer Model v0.7"
|
||||
domain: infotech
|
||||
repo: audit-core
|
||||
status: active
|
||||
status: finished
|
||||
flavor: implementation
|
||||
owner: claude
|
||||
topic_slug: railiance
|
||||
created: "2026-08-29"
|
||||
updated: "2026-09-21"
|
||||
updated: "2026-09-22"
|
||||
depends_on:
|
||||
- AUDIT-WP-0007
|
||||
state_hub_workstream_id: "46a96b03-bc08-53b5-9c93-4071adabf734"
|
||||
|
|
@ -201,10 +201,27 @@ itself go missing, which rate monitoring can never produce.
|
|||
|
||||
```task
|
||||
id: AUDIT-WP-0009-T05
|
||||
status: wait
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "382575ca-1801-5a32-a93d-90a8b9c8adbf"
|
||||
```
|
||||
Done 2026-09-22. The wait ended when info-tech-canon published the contract
|
||||
(message `368e54bf`): `emission-cadence.schema.yaml`, wire schema 0.1, read at
|
||||
contract digest `b08b4d95fc4b0bd3`. No competing shape was invented.
|
||||
`audit_core/emission_cadence.py` validates a source-owned declaration carried
|
||||
as `emission_cadence` on the sender registration; `expected-rate` entries are
|
||||
evaluated against the same per-class counts `/v1/reconciliation` returns and
|
||||
surface as `below_declared_cadence` on `GET /v1/stream-findings`.
|
||||
`heartbeat-or-reconciliation` entries are validated and left to T04/T06. The
|
||||
scope overlay may not touch a declaration. Thirty-nine tests in
|
||||
`tests/test_emission_cadence.py`.
|
||||
|
||||
Observer evaluation of net-kingdom's `local-identity` declaration: structurally
|
||||
clean, operationally not evaluated (no such sender is registered here), and one
|
||||
incompatibility recorded — the contract's `heartbeat.event_class` names a
|
||||
distinct heartbeat class, where audit-core's heartbeat is one class carrying
|
||||
the vouched-for class in `data.class`. See `docs/stream-completeness.md`.
|
||||
|
||||
Accept and evaluate a declared emission cadence per source, and raise a finding
|
||||
when the stream falls below it. **Waiting on** the §17 emission-cadence
|
||||
declaration schema, which `kings-guard` is drafting and Taxonomy will own; do
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue