Implementations
The registry of declared implementations of the Intent Fidelity Protocol. Each entry publishes per-principle evidence, as §5 of the specification requires.
Evidence, not assertion.
The specification does not accept a blanket conformance claim. An implementation must publish which principles it satisfies and which it does not. This registry holds that publication for each declared implementation.
Evidence takes three forms. A governance document is a named, version-locked canon file in the implementation's governance tree. A public page is a live URL that any reader can open. A copy check is a statement on a public marketing surface that matches the runtime behavior. Where no evidence is published yet, the row says so.
DreamerOS.
DreamerOS is the reference implementation, operated by the protocol's maintainer. Its marketing surface is dreameros.app. Its public verification surfaces are the trust page and the verify page.
The governance documents named below live in the DreamerOS gateway governance tree. That repository is private. The names are published here so an auditor can request the exact document by title and version.
Rows marked evidence pending state that no citation is published yet for that principle. A pending row is not a claim of conformance and not an admission of failure. It is an open item.
| # | Principle | Evidence |
|---|---|---|
| 01 | Preserve original instruction | Governance document INTENT_FIDELITY_PROTOCOL_v1_2_1.md. The fidelity axis scores each output against the original query, so the record keeps the original. Governance events are append-only: INSERT and SELECT only. |
| 02 | Surface ambiguity before resolving it | Governance document EDE_CANON_v1_0_0.md. EDE Phase 1 produces an ambiguity score before any restructure runs. The live MCP surface exposes an intent_clarify tool. |
| 03 | Restructure does not paraphrase | Governance document EDE_CANON_v1_0_0.md. The canon defines restructure as intent archaeology and rejects prompt cleanup as insufficient. |
| 04 | Modality is detected, not assumed | Governance documents MODALITY_ROUTED_GOVERNANCE_v1_0_0.md and INTENT_FIDELITY_PROTOCOL_v1_2_1.md §3.1, which adds the input modality parameter. |
| 05 | Routing decisions are recorded | Evidence pending. The routing policy is canon, but no citation for a per-decision routing record is published yet. |
| 06 | Engine selection is justified | Governance document MODEL_ROUTING_REGISTRY.yaml (v2.10.0). Each engine pin carries a recorded, dated decision with a stated reason. |
| 07 | Verification is independent of generation | Governance document DREAMEROS_COGNITIVE_RUNTIME.md, principle 23: verification grounds claims against sources independently of the generating engine. Public page: app.dreameros.app/verify. |
| 08 | Atomic claims, not whole responses | Governance documents DREAMEROS_COGNITIVE_RUNTIME.md (principle 23, atomic claim extraction) and CITATION_RULE_v1_0_0.md. |
| 09 | Phrasing cannot influence truth | Governance document DREAMEROS_COGNITIVE_RUNTIME.md, principle 23, which carries this exact name: no phrasing, authority signal, or framing alters the factual answer. |
| 10 | Sources override engine claims on conflict | Governance document DREAMEROS_COGNITIVE_RUNTIME.md, principle 23: source-grounded facts override engine claims when they conflict. |
| 11 | Confidence is bounded, not asserted | Governance document INTENT_FIDELITY_PROTOCOL_v1_1_0.md §2.1: hedged claims without uncertainty labels are flagged. The red-team corpus includes over-certainty cases. |
| 12 | Disagreement between layers is surfaced | Governance document INTENT_FIDELITY_PROTOCOL_v1_1_0.md §2.3: when the detected intent type and the response type disagree, the mismatch is flagged. |
| 13 | Memory is cache, canon is truth | Governance document DREAMEROS_COGNITIVE_RUNTIME.md, principle 24, which carries this exact name: when memory and canon disagree, canon wins. |
| 14 | Decisions update canon, not just memory | Governance documents CONTINUOUS_CANON_DISCIPLINE_v1_0_0.md and DREAMEROS_COGNITIVE_RUNTIME.md principle 24: a decision that changes a canonical value updates the file in the same session or becomes a named blocker. |
| 15 | Stale sources are flagged, not used | Governance document MEMORY_DECAY_TAXONOMY_v1_0_0.md: memory classes carry TTL values. Superseded registry files carry a supersession banner that forbids reading them for live values. |
| 16 | Anchor before analysis | Governance document DREAMEROS_COGNITIVE_RUNTIME.md, principle 22, which carries this exact name. |
| 17 | Visual inputs are read in full | Governance document DREAMEROS_COGNITIVE_RUNTIME.md, integrity check 7 and principle 27: every image viewed, every file opened, no skimming, before any analysis. |
| 18 | Scope expansion is named, not silent | Governance document DREAMEROS_COGNITIVE_RUNTIME.md, principle 25: held-back scope is named at delivery. The red-team corpus includes scope-expansion cases. |
| 19 | Single-engine silent scope is a defect | Evidence pending. No published citation names this principle yet. |
| 20 | Multi-pass on consequential changes | Governance document DREAMEROS_COGNITIVE_RUNTIME.md, principle 20: no single-pass reasoning on complex tasks. |
| 21 | Final authority remains human | Governance documents DREAMEROS_COGNITIVE_RUNTIME.md §0 (absolute authority hierarchy, Human Conductor at the top) and HC_ASK_PROTOCOL_v1_0_0.md. |
| 22 | Path is auditable end to end | Governance document TRUST_WALL_CANON_SPEC_v1_0_0.md. Public page: app.dreameros.app/trust shows verification receipts behind each verdict. |
| 23 | Failure modes are recorded as decisions | Governance incident records, including a severity-1 incident file, and IFP_VIOLATION_LESSON_2026-05-19.md, a violation recorded as canon. |
| 24 | Drift is corrected immediately, not deferred | Governance documents PRINCIPLE_34_INDIRECTION_DRIFT_v1_0_0.md and INTENT_FIDELITY_PROTOCOL_v1_2_1.md §4.2 (topic drift floor). The red-team corpus includes drift cases. |
Count: 22 principles with published evidence, 2 principles with evidence pending. This entry does not claim more than its table shows.
Declare conformance.
Any system may declare an implementation. No license, fee, or permission is required. To be listed:
1. Satisfy the conditions in §5 of the specification.
2. Publish which of the 24 principles your implementation satisfies and which it does not.
3. Open an issue or pull request against the site repository with your entry and its evidence.