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

Close WP-0036 on natural heartbeat evidence; declare emission cadence
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details

Browse source 
WP-0036-T04: rein-aharness 44f5bb9 heartbeats immediately after claim and
returned a natural claim/heartbeat/complete trace (hub message c217e92f).
With the 2026-08-23 authenticated claim and spoofed-identity 403, the
acceptance is met. The late-close smoke stays an optional rein-side follow-up.

Add a source-owned Emission Cadence declaration for scheduled evidence events
(INFO-WP-0029-T03), with a recorded incompatibility: expected-rate cannot
express the weekday-only SBOM catch-up schedule.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 151606@bnt-lap001
Assistant-Session: 3c0a4ad5-bb8b-4bf7-b9f0-fa5f29204e48
This commit is contained in:
tegwick 2026-09-22 22:44:58 +02:00
parent 51689bf323
commit f20db478f5
3 changed files with 96 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

25
docs/evidence/ACTIVITY-WP-0036-queue-boundary-rollout-2026-08-23.md
View file

@ -41,3 +41,28 @@ rejection. No run was actively leased during the rollout window, so a natural
production heartbeat plus a rejected late close remains the final T04 evidence.
This does not weaken the deployed enforcement; it avoids changing unrelated
production work solely to create a demonstration row.
## Natural heartbeat evidence (2026-09-22)
Reported by rein-aharness in State Hub message
`c217e92f-0968-416f-9def-fd8ab4a436f3` (thread
`1250c36a-9fe8-45dc-bb5a-d5fa85e49fd0`):
- rein-aharness `44f5bb9` heartbeats once immediately after claim and before
dispatch; a 409 on that heartbeat fails closed before dispatch
(`stage=pre-dispatch-heartbeat`). Deployed on railiance01 in claim-loop tree
`11020e8`; `rein-aharness-claim-loop.service` active since
2026-09-13 20:52:18 UTC.
- 19 natural claims since then logged an accepted initial heartbeat, and none
were rejected.
- Natural trace, run `a19455cd-2d25-43f5-a0af-1a6af0910d37`
(fi-research-brief, 2026-09-14): `05:30:25.388` heartbeat HTTP 200, then
`05:30:29.138` complete HTTP 200, state `succeeded`.
This is evidence the counterparty attested. It was not re-read from actcore-api logs or
the production database in this session. The T04 acceptance (authenticated
claim, active heartbeat, and a rejected mismatched *or* expired mutation) is
met: claim and 403 mismatch above, heartbeat here. Server-side expiry
rejection is proven by the deterministic suite. rein-aharness's labelled
late-close smoke remains an optional follow-up on their side and does not gate this
workplan.