coulomb/informed-decision
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Reconcile Staff evidence readiness and retain exact verification residual

Browse source 
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a126e1-76f8-7643-8cf3-e93336539ade
This commit is contained in:
tegwick 2026-10-11 04:17:59 +02:00
parent 716e95e8dd
commit 9268c9ac0b
7 changed files with 234 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

51
docs/evidence/2026-10-11-staff-evidence-source-reconciliation.md Normal file
View file

@ -0,0 +1,51 @@
# Staff evidence source reconciliation — 2026-10-11
Derived source-owner review of accepted bounded GH-DEC-2026-025 handoff and
accepted NetKingdom security-layer-model_v0.8.md §9.6/11; proposed successor
adoption/publication remains NET-IN-0004. Owner HEAD716e95e8dd97aa6638a08a694481fdb0fa336dd4.
No native data, credentials, live changes or conformance promotion occurred.
| Declared class | Wire class | Actual source mechanism | Retained native evidence | Remaining verification |
| --- | --- | --- | --- | --- |
| presentation: load-bearing/volume | informed-decision.presentation | atomic record/evidence/outbox; heartbeat86400s; pump30s; reconciliation300s | Oct5 receipt:2 selected delivered records with receiver refs and matching class counts | full cadence/detection declaration and time-basis-aware native reconciliation/monitoring; rate monitoring is not declared |
| disposition: load-bearing/rare | informed-decision.disposition | same transactional/heartbeat/reconciliation mechanism | Oct5 receipt:2 selected delivered records with receiver refs; aggregate audit-core.heartbeat2 | per-target rare heartbeat plus reconciliation/detection operating proof; aggregate heartbeat count identifies no target class |
| stance-application: load-bearing/rare | informed-decision.stance_application | commit_stance_application/Store record_unreachable; same86400s heartbeat and reconciliation mechanism | selected Oct5 native receipt contains no stance-class record/count; existing synthetic tests cover stance and backlog-safe per-class heartbeat | per-target heartbeat, stance-class native operation and reconciliation/detection proof; no missing-emission finding inferred from an empty historical window |
Source: informed_decision/evidence.py HEARTBEAT_CLASSES declares86400s per
class. Store queues no nothing-to-report heartbeat when that class or its prior
heartbeat is undelivered. Actual native class spellings use stance_application;
this maps the existing declaration's stance-application, not a fourth class.
AuditPump30s ticks drain bounded batches, write private300s reconciliation and
close readiness for retry/blocked/pending delivery. A ready pump is not §11
whole-class completeness or independently monitored cadence proof.
OutboxWorker.reconcile verifies scope/window/shape and compares source occurred_at
to receiver accepted_at. It explicitly returns automatic_loss_finding=false,
completeness_proven=false and reconstructability_proven=false. Delayed acceptance
can shift a legitimate event between windows; matching counts do not establish
matching membership, complete emission or truthful display. Current source has
no standalone cadence.yaml; code intervals are a mechanism inventory, not a
returned fully verified per-class guarantee. Existing tests enforce backlog-safe
class heartbeats and honest nonclaiming reconciliation; no new test run was
needed for this documentation-only source review.
Native supporting receipt:
docs/evidence/2026-10-05-lifecycle-cutover/native-audit-after-acceptance.json.
Its selected source/receiver totals match, including aggregate heartbeat2,
presentation2 and disposition2; they do not prove per-target heartbeat or
stance-class completeness. Additional memo.posed/lifecycle classes in that
receipt are not substitutes for these three independently classified classes.
Local outbox/scheduling and sender/receiver delivery are implemented, so old
layer.yaml outbox/AUDIT-WP-0009 blockers are stale. Remaining truthful declaration
and operating verification are retained once as INFD-IN-0009, an unpromoted
residual from finished INFD-WP-0007 with related finished INFD-WP-0005. Both
finished plans remain finished. There is no guarantee/conformance upgrade.
GH-DEC-2026-025 answers INFD-IN-0007 by carrying unresolved §3.4 tension explicitly;
NET-IN-0004 holds pending separately accepted successor standard voice. Staff/
PEP-shaped classification, no approval current-state/verdict/consume boundary,
independent evidence path, view_hash/digest authority and GH-DEC-2026-014
commitment-only content-availability/compromised-source residuals persist.
Recording accepted doctrine and actual implementation mechanisms does not resolve
that tension or accept the successor standard as a whole.