Gate A - Continuum Participant Conformance

[flyingrobots]

Contract

Echo 1.0 must attain Continuum participation status. Echo must be a lawful Continuum participant with explicit descriptor, profile posture, capability posture, registration/admission/invocation receipt chains, and participant-neutral obstruction semantics.

Owner

Canonical repository: echo for the Echo release gate.

Contract partner: continuum owns the protocol/conformance definitions.

Executable check

A conformance workflow or command must run the Echo Continuum participant fixture suite and return pass/fail.

Expected final shape:

cargo xtask test-slice echo-1.0-continuum-participant

Required evidence

• Versioned Echo participant descriptor.
• Declared profile/capability posture.
• Registration receipt chain.
• Admission receipt chain.
• Invocation receipt chain.
• Obstruction vocabulary report.
• Continuum conformance report tied to exact Echo and Continuum commits.

Negative cases

• Self-asserted participant-kind labels do not expand authority.
• Registration without admission cannot invoke.
• Admission without sufficient presented capability cannot invoke.
• Revoked or stale authority blocks invocation.
• Obstruction class remains participant-kind neutral under equal effective authority.

Compatibility set

Must pin exact Echo and Continuum commits, participant profile versions, receipt schema versions, obstruction vocabulary version, and conformance fixture version.

Pass rule

Pass only when the conformance report is published, references exact commits, and every required positive and negative fixture passes.

[coderabbitai]

🔗 Related PRs

#323 - Witnessed suffix admission evaluator [merged]
#368 - feat(core): connect installed contract intent pipeline [merged]
#371 - feat(core): advance v0.1 contract evidence and retention [merged]
#380 - feat(core): expose retained evidence posture on readings [merged]
#529 - Add Hello Echo demo and docs lifecycle policy [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!