Gate C - Native Jedit-on-Edict Execution

[flyingrobots]

Contract

Echo 1.0 must execute designated Jedit operations natively through Edict artifacts. Jedit operations must compile through Edict, be admitted by Echo, invoke through deterministic envelopes, and mutate Echo history without a bespoke Jedit bypass path.

Owner

Canonical repository: echo for the Echo release gate.

Contract partners: edict owns artifact/compiler semantics; jedit owns the product operation set and client proof.

Executable check

A release-gate workflow or command must run the native Jedit-on-Edict fixture and return pass/fail.

Expected final shape:

cargo xtask test-slice echo-1.0-jedit-edict

Required evidence

• Jedit operation source/provenance.
• Edict bundle digest and schema version.
• Echo admission receipt.
• Invocation envelope digest.
• Echo mutation receipt/outcome.
• End-to-end trace from authored operation to Echo mutation.
• Negative-test receipts proving bypass rejection.
• Pinned Echo, Edict, and Jedit commits.

Negative cases

• Unauthorized Edict artifact rejected.
• Malformed artifact rejected.
• Incompatible artifact rejected.
• Direct legacy Jedit bypass rejected or unreachable.
• Replay/idempotency behavior is deterministic.

Compatibility set

Must pin exact Echo, Edict, and Jedit commits, artifact schema version, operation set, and bundle digest.

Pass rule

Pass only when all designated Jedit operations execute through Edict, the old bypass cannot execute, and the trace links authored operation -> bundle -> admission -> invocation -> Echo mutation.

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• Echo 1.0: Edict Native Invocation in Echo #583

🔗 Related PRs

#329 - Stack Witness 0001 fixture-backed jedit walking skeleton [merged]
#369 - docs: add Echo v0.1.0 release plan [merged]
#371 - feat(core): advance v0.1 contract evidence and retention [merged]
#380 - feat(core): expose retained evidence posture on readings [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!