Repository navigation
Feature: Publish canonical target-profile contract resources #158
Copy link
Copy link
Closed
Labels
domain: backendCompiler/backend implementation workCompiler/backend implementation workenhancementNew feature or requestNew feature or requestrelease:target-profilesTarget-profile contract and authority source release workTarget-profile contract and authority source release workstate: activeCurrently being implemented or reviewedCurrently being implemented or reviewedstate: frontierOpen and currently unblocked on the execution frontierOpen and currently unblocked on the execution frontiertype: featureFeature issue for a cohesive capabilityFeature issue for a cohesive capability
Description
Cohesive Capability
Edict publishes canonical, content-addressable contract artifacts for every Edict-owned resource slot required by edict.target-profile/v1: canonical CBOR rules, component sandbox requirements, fuel accounting, diagnostics ABI, and deterministic-execution policy.
These are authority artifacts, not illustrative prose identifiers. Runtime-owned target-profile generators can accept exact trusted bytes and expected digests instead of blessing arbitrary caller bytes under an Edict coordinate.
Cross-repo prerequisite for flyingrobots/echo#652.
Scope
- Define one authoritative byte artifact for each Edict-owned target-profile resource coordinate:
edict.canonical-cbor/v1edict.wasm-component/v1edict.fuel/v1edict.diagnostics/v1edict.determinism/v1
- Give every artifact an exact repository source, canonical encoding, stable coordinate, and reproducible SHA-256 digest.
- Publish executable checks that regenerate or verify all bytes and digests.
- State how provider generators receive trusted artifacts without registry lookup or mutable-name resolution.
- Add compatibility evidence showing a conforming target profile can bind the published resources.
Acceptance Criteria
- Repeated generation produces byte-identical artifacts and digests.
- Any semantic change moves the relevant digest.
- Wrong coordinate, bytes, digest, or provenance rejects before a target profile is emitted.
- The artifacts are runtime-neutral and contain no Echo-specific policy.
- Documentation distinguishes semantic contract resources from provider-owned lowerer/verifier component selection.
Boundaries
- No network registry, signatures, participant trust policy, or runtime execution.
- Do not embed a particular Echo lowerer or verifier.
- Do not make target-profile generators discover repository files implicitly.
Dependency Graph
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
domain: backendCompiler/backend implementation workCompiler/backend implementation workenhancementNew feature or requestNew feature or requestrelease:target-profilesTarget-profile contract and authority source release workTarget-profile contract and authority source release workstate: activeCurrently being implemented or reviewedCurrently being implemented or reviewedstate: frontierOpen and currently unblocked on the execution frontierOpen and currently unblocked on the execution frontiertype: featureFeature issue for a cohesive capabilityFeature issue for a cohesive capability
Activity
coderabbitai commentedon Jul 13, 2026
🔗 Related PRs
#2 - docs: apply Phase 0 design review + nail five yellow-light joints [merged]
#108 - Freeze canonical Target IR artifacts [merged]
#132 - Lower obstruction requirements to Echo Target IR [merged]
#144 - Add built-in lowerer compatibility seam [merged]
#156 - Add generation provenance provider artifact kind [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 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:💬 Have feedback or questions? Drop into our discord!