coulomb/info-tech-canon
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Implement canon conformance and maintenance optimizations
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06e82-3e08-7042-a79d-438ac6eed8db
This commit is contained in:
tegwick 2026-09-05 00:50:09 +02:00
parent a2e7f22d8d
commit b081d39da1
64 changed files with 4491 additions and 373 deletions
Download patch file Download diff file Expand all files Collapse all files

14
infospace/assimilation/emission-cadence/open-questions.md Normal file
View file

@ -0,0 +1,14 @@
# Open questions — EmissionCadenceDeclaration
No question blocks adoption.
The following promotion questions remain for the draft's future review:
1. Do two independent source implementations need interval tolerance or grace
fields in the generic core, or can profiles carry them in `extensions`?
2. Should schema 1.0 retain the handed-over name `sources` for cadence entries,
or migrate to the clearer `cadences` with explicit compatibility tooling?
3. Does reconciliation eventually need a generic typed counter-selector
language, or are owner-defined field references sufficient?
These are review triggers, not deferred implementation tasks.