Skip to main content

​
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:
  1. Origin access — retrieve bounded public representations.
  2. Observation and evidence — preserve bytes and retrieval metadata.
  3. Adapter compilation — propose and validate extraction behavior.
  4. Semantic canon — version concepts and mappings.
  5. Typed Web IR — define finite operational contracts.
  6. Execution — run admitted deterministic plans.
  7. Interface bindings — expose operations through transports.
  8. 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