net-kingdom/tools/coordination-frame/README.md
tegwick 2d0681f361
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
Adopt shared hourly coordination frame and prepare guarded runtime patches
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a13eab-1e6a-7b33-9c37-372e90ada3a2
2026-10-15 20:45:06 +02:00

42 lines
2.3 KiB
Markdown

# Coordination-frame bindings
The ecosystem frame is owned by coordination-engine at
`coordination-engine/config/coordination-frame.json`. Its initial value is
`frame_seconds: 3600`, selected by the founder on 2026-10-15. Change that one
setting to change the pace. The owner API validates positive integer frames
and derives timezone-bound deadlines; this tool imports that API, with no
fallback config or duplicated reader.
For cadence adoption the formulas are heartbeat **f**, registered receiver
wait **2f**, and effective missing-heartbeat deadline **3f** after Audit Core's
existing 1.5 grace. At f=1h those are 3600, 7200 and 10800 seconds. A return
to f=24h produces 24h/48h/72h through the same formulas.
From net-kingdom:
```sh
python3 tools/coordination-frame/render.py # read-only source plan
python3 tools/coordination-frame/render.py --check # fail on derived-file drift
python3 tools/coordination-frame/render.py --write # regenerate source artifacts
python3 -m pytest -q tools/coordination-frame/tests
```
`--write` changes only the listed source files. It prepares Approval Engine
and Qonto declarations, generated Python defaults, both deployment heartbeat
settings, and a non-secret proposed Approval Engine receiver registration.
The compiler preserves image pins, identity, secret references, other source
classifications and the lack of a completeness claim. Each generated consumer
records the frame source and SHA-256. Runtime consumers import their generated
values rather than opening an adjacent coordination-engine checkout.
Check generated artifacts after changing the frame, review/commit each owner
source, then use the owner's approved release and registry procedures. This
tool performs no login, credential operation, registry update or deployment.
It cannot replace a source collector or provide operational observer evidence.
All five binding tests require the sibling owner checkouts and explicitly skip
when they are unavailable; no substitute owner contract is used.
This is the first rollout of a shared coordination setting. Other ecosystem
coordination consumers must adopt explicit frame multipliers through their own
configuration. Transport polling, security validity and credential leases are
not silently rescaled by a coordination setting.