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

Verify live reporting repair and monthly review readiness

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e738-9e15-7600-87e6-90dec3a7beef
This commit is contained in:
tegwick 2026-09-28 11:31:52 +02:00
parent 58e8ef675e
commit 80dc3e5d85
11 changed files with 217 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

34
docs/ActivityCoreLoop.md
View file

@ -1,9 +1,10 @@
# Activity-core receipt loop
Current diagnosis (2026-09-28): the first natural daily run fired but failed because
the replacement worker image lacks the domain resolver. A tested repair image is
published and awaits the scoped attended-release exception; prior smoke success
is historical. See [repair evidence](evidence/2026-09-28-reporting-repair.json).
Current state (2026-09-28): repaired through the user-approved, scoped GitOps
exception. The grant-aware worker now includes the domain resolver; daily, weekly
and monthly scheduled smoke runs produced validated receipts. The first natural
daily failure remains historical evidence; subsequent natural cadence and the
October 1 packet remain due. See [live proof](evidence/2026-09-28-reporting-live.json).
FEP-WP-0008 owns this integration. The initial delivery is deterministic collection
and reporting. Automatic investigation and publication are a separate, outstanding
@ -170,3 +171,28 @@ Hosted discovery is still unregistered (404) and its routed write credential is
unavailable to the current operator session. Public source publication passed.
The [consumer hook](../feedback/ConsumerIntegration.md) is prepared, but no real
consumer was fabricated or enrolled. These obligations remain WP-0008 T01/T02.
## Approved repair completed — 2026-09-28
User decision `abdea390-1039-4da1-b129-33aad00b4396` approved the exact attended
repair. Activity Core source `4bd07a4` and platform pin `986b002` were pushed;
ArgoCD root synced only the activity-core Application, then the child synced only
its worker Deployment. ArgoCD is Synced/Healthy at the intended revision. Live
Python source hashes, resolver registry and grant identity match the tested image.
All three Temporal scheduled smokes completed with no tasks or model calls, and
all three State Hub receipts validate. Temporary smoke schedules are removed;
recurring schedules remain active. [Live evidence](evidence/2026-09-28-reporting-live.json)
and [next fires](evidence/2026-09-28-reporting-postrepair-schedules.json).
The monthly sink now carries review health, decisions/defaults and measured effort
with unknown-cycle counts. Today's actual monthly smoke covers August; the separately
labeled October fixture checks September data. October 1 09:00 Berlin remains the
first natural monthly packet, not completed early. Health fields are explicitly dated
owner snapshots, not independently sampled live attestations. The current input is
[versioned here](../feedback/monthly-review-input.json); stale snapshots are flagged.
ACTIVITY-WP-0040 T02 retains natural cadence evidence; ACTIVITY-WP-0041 and
RPF-WP-0048 retain continuous-health observation and standing release authority.
Their old September 27 observation interval is invalidated by the reporting failure.
The scoped exception does not enable automatic pattern editing or routine releases.