coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

docs: record repo-manager as consistency sweep engine
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
ACTIVITY-WP-0029 keeps the 15-minute schedule in activity-core and
treats State Hub as the dual-run adapter until REPO_MANAGER_URL is set.
This commit is contained in:
codex 2026-08-18 10:53:03 +02:00
parent 5331f9af68
commit 1e2199ddc7
1 changed files with 16 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

38
activity-definitions/state-hub-consistency-sweep.md
View file

@ -27,14 +27,13 @@ context_sources:
## Purpose ## Purpose
This definition is the activity-core handoff point for This definition is the activity-core handoff point for the 15-minute
`STATE-WP-0064 - Move State Hub consistency sync to Railiance01`. ADR-001 reconciliation sweep (STATE-WP-0064, ACTIVITY-WP-0029).
It schedules the 15-minute ADR-001 reconciliation sweep across all activity-core owns the cron schedule and ActivityRun audit trail.
registered repos with local paths on the workstation State Hub host. **repo-manager** owns the C-rule engine. State Hub
State Hub owns `scripts/consistency_check.py`, lock semantics, and the `POST /consistency/sweep/remote-all` is the dual-run adapter until
`consistency_sweep_remote_all` progress event; activity-core owns the `REPO_MANAGER_URL` / `CONSISTENCY_SWEEP_URL` points at repo-manager.
cron schedule and ActivityRun audit trail.
## Runner Status ## Runner Status
@ -59,24 +58,19 @@ is skipped rather than replayed as a burst after the host returns.
## Deterministic State Hub Invocation ## Deterministic State Hub Invocation
The `consistency_sweep_remote_all` State Hub context resolver issues: The `consistency_sweep_remote_all` resolver issues:
- `POST /consistency/sweep/remote-all` - `POST {sweep_base}/consistency/sweep/remote-all`
- payload: `{"max_seconds": 300}` - payload: `{"max_seconds": 300, "source": "activity-core"}`
The context source is marked `required: true`. A failed State Hub call `sweep_base` is `CONSISTENCY_SWEEP_URL` or `REPO_MANAGER_URL` or
fails the activity-core workflow visibly instead of silently binding an `STATE_HUB_URL` (default dual-run adapter). The context source is
empty context. On success, the response is stored in the ActivityRun `required: true`. A failed call fails the workflow visibly. On success,
`context_snapshot` under `consistency_sweep_remote_all`. the ActivityRun snapshot includes `engine_owner`, `adapter`, and
`sweep_url`.
State Hub runs `consistency_check.py --remote --all --json` on the `STATE_HUB_URL` (adapter default) must point at the workstation State Hub
workstation host and records a compact progress event with event type through the ops-bridge tunnel, not a cluster-local checkout path.
`consistency_sweep_remote_all`, including processed repos and skip
metadata.
`STATE_HUB_URL` must point at the workstation State Hub through the
ops-bridge tunnel service (for example `actcore-state-hub-bridge`), not
at a cluster-local checkout path.
## Output Contract ## Output Contract