Skip to content

W1: Schema hash chain pinning (SDL→IR→bundle) recorded in receipts #193

Description

@flyingrobots

Pulse context: bi-directional compiler loop.

Goal

  • Prevent drift by pinning schema artifacts via a hash chain (SDL hash → IR hash → codegen bundle hash), and recording those hashes in receipts/events.

Scope

  • Define the hash boundaries and where they are recorded.
  • Identify the minimal receipt/event surfaces that must include these pins.

Acceptance criteria

  • Spec describes the hash chain and failure mode (fail closed when pins mismatch).
  • Any prototype codegen bundle can report its bundle hash.

Parent

Activity

  1. flyingrobots commented on Jun 1, 2026

    @flyingrobots
    OwnerAuthor

    Closing from Echo triage: schema/hash-chain work is not blocking current GraphQL-schema -> generated Rust usage in echo-wesley-gen.

    Current Echo source anchors:

    • crates/echo-wesley-gen/tests/generation.rs:1513 asserts generated SCHEMA_SHA256 output.
    • crates/echo-registry-api/src/lib.rs:56 defines host verification policy fields including expected schema hash and generator metadata.
    • crates/echo-registry-api/src/lib.rs:358 verifies generated artifacts against host policy.

    A full SDL -> IR -> bundle hash chain is Wesley/compiler-product work unless Echo has a concrete verification surface to consume.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureFeature umbrella (epic)specSpec/Design document

    Projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions