coordination-engine/docs/coordination-frame.md

Ecosystem coordination frame

Founder decision in the NK-WP-0035 sitting, 2026-10-15: use a configurable base frame for long-term ecosystem coordination, initially f = 1 hour, replacing the daily pace. Authoritative configuration: config/coordination-frame.json. frame_seconds is the one operator setting. coordination_engine.timing validates it and derives durations and timezone-bound deadlines in frames.

PYTHONPATH=src python3 -m coordination_engine.timing --config config/coordination-frame.json

Coordination wait stages are expressed as 2f and 3f. Owners adopt the frame explicitly and retain the configuration digest in generated artifacts. The first adoption is NK-WP-0035: source heartbeat f, receiver registration 2f, then Audit Core's existing 1.5 grace gives an effective deadline of 3f. At the current setting those durations are 1h, 2h and 3h. Changing f to 24h reproduces the former 24h/48h/72h cadence without changing the multipliers.

NetKingdom's tools/coordination-frame/render.py checks or regenerates the first source/runtime bindings. Generated consumer values are compiled copies of this configuration, with provenance; they are not independent knobs. Runtime owners review and deploy those artifacts through their normal change paths. A configuration edit or a local deadline calculation does not enable workers, apply a deployment, change a credential lifetime, or establish that any other ecosystem timer has adopted this frame. New owners must name their multipliers and verify adoption rather than silently scaling every timeout.

Worker transport polling, leases, retry backoff, credential TTLs and approval validity are separate owner contracts. This parameter paces coordination and cadence; it grants no authority and does not extend security validity.