Goalpost: Echo Edict Provider Walking Skeleton

[flyingrobots]

Integration checkpoint

Echo owns and ships a real edict-echo provider assembled from generated semantic artifacts and Echo-owned lowerer/verifier components. Edict consumes it through the landed runtime-neutral provider boundary without learning Echo semantics.

The observable proof is:

Echo semantic sources
  -> Echo-Wesley generated lawpack/profile/facts/schemas
  -> digest-locked Echo provider package
  -> Edict Core
  -> external Echo lowerer
  -> canonical echo.span-ir/v1
  -> Echo verifier
  -> semantically identical contract bundle

Landed Edict inputs

• Feature: Provider generated-artifact provenance contract edict#139: generated-artifact provenance contract
• Feature: Built-in provider compatibility wrappers edict#140: built-in compatibility and byte/digest baseline
• Feature: WIT provider host alpha edict#141: capability-denied edict:target-provider@1.0.0 host
• Feature: Freeze authority-facts canonical CBOR ABI edict#157: canonical authority-facts CBOR/CDDL ABI

Required slices

• Freeze Echo provider semantic-source and artifact-domain contract #651 - Freeze Echo provider semantic-source and artifact-domain contract
• Generate Echo Edict lawpack, target profile, authority facts, and provenance #652 - Generate Echo lawpack, target profile, authority facts, schemas, and provenance
• Implement the Echo Edict WIT lowerer component #653 - Implement the Echo Edict WIT lowerer component
• Implement the Echo Target IR semantic verifier component #654 - Implement the Echo Target IR semantic verifier component
• Assemble the digest-locked Echo Edict provider package #655 - Assemble the digest-locked Echo Edict provider package
• Generate Target-IR-bound Echo registration and invocation helpers #656 - Generate Target-IR-bound Echo registration and invocation helpers
• Prove Edict and external Echo provider conformance and semantic parity #657 - Prove Edict/external-provider conformance and semantic parity

Generic Wesley enabler: flyingrobots/wesley#728.

The native subissue and blocked-by graph is authoritative; the checklist is a readable projection.

Definition of done

• Echo names one authoritative source for every semantic fact in the minimal slice.
• Echo-Wesley deterministically generates the lawpack, target profile, authority facts, schemas, provenance, and review projections.
• Echo owns exact WIT lowerer and verifier components with no ambient capabilities.
• A provider manifest binds every generated artifact, schema, and component by exact digest and provenance.
• Generated registration/invocation helpers bind exact Target IR and bundle identities.
• Edict compiles one reviewed fixture using only the generated Echo artifacts.
• External provider Target IR bytes/digest and semantic bundle digest equal the built-in compatibility baseline.
• Negative fixtures prove refusal, tamper rejection, no overclaim, and no silent semantic loss.

Boundaries

• No handwritten lawpack or target-profile file is a semantic source of truth.
• No Echo semantics move into Edict.
• No generic provider registry, remote resolution, or publication system.
• No runtime admission or execution claim in this goalpost.
• Browser delivery and native Echo execution remain downstream under Echo 1.0: Edict Native Invocation in Echo #583, Gate C - Native Jedit-on-Edict Execution #589, and JS/WASM/Browser Client Release Surface #516.

Cross-repo handoff

This is the Echo-owned implementation family requested by flyingrobots/edict#142 and a prerequisite for #583. Completion of #657 closes the provider/conformance handoff; #583 then owns admitted runtime execution, while #516 owns app-safe JS/WASM/browser delivery.

[coderabbitai]

🔗 Related PRs

#326 - Echo contract hosting roadmap [merged]
#329 - Stack Witness 0001 fixture-backed jedit walking skeleton [merged]
#344 - feat(wesley): consume canonical requirements artifacts [merged]
#365 - feat(wesley): emit query observer host helpers [merged]
#582 - docs: define the Echo 1.0 release contract and move live planning to GitHub [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!