Boundary model
A representation is not canonical knowledge. A mapping is not execution authority. A signed package is not automatically semantically correct.
The architecture keeps separate:
- Origin access — retrieve bounded public representations.
- Observation and evidence — preserve bytes and retrieval metadata.
- Adapter compilation — propose and validate extraction behavior.
- Semantic canon — version concepts and mappings.
- Typed Web IR — define finite operational contracts.
- Execution — run admitted deterministic plans.
- Interface bindings — expose operations through transports.
- Trust and admission — decide what may become canonical.
Canonical-write rule
Fetchers, browser workers, adapters, and future models may produce candidates. They may not promote their own candidates.
Genesis expresses this rule socially through reviewed repository changes. A later registry will enforce it through a separate admission service and trust state machine.Last modified on August 10, 2026