Goalpost: Continuum protocol observation evidence and capability proofs

[flyingrobots]

Goalpost

Make the Continuum protocol compendium executable as profile fixtures, evidence posture vocabulary, conformance reports, and cryptographic/capability proof shapes.

Continuum is a protocol suite for lawful causal interoperability over witnessed causal history. It is not a runtime, database, scheduler, debugger UI, app framework, or Jim/Echo transport layer.

Slices

• Slice: Add continuum.participant.hello.v1 descriptor fixture #54 Slice: Add continuum.participant.hello.v1 descriptor fixture
• Slice: Standardize multidimensional evidence posture vocabulary #56 Slice: Standardize multidimensional evidence posture vocabulary
• Slice: Add continuum.contract.index.v1 profile fixture #68 Slice: Add continuum.contract.index.v1 profile fixture
• Slice: Add continuum.observation.v1 profile fixture #55 Slice: Add continuum.observation.v1 profile fixture
• Slice: Add protocol compatibility matrix and witness cuts #57 Slice: Add protocol compatibility matrix and witness cuts
• Slice: Add qw doctor conformance report fixture #69 Slice: Add qw doctor conformance report fixture
• Slice: Add WARP TTD participant discovery consumer fixture #70 Slice: Add WARP TTD participant discovery consumer fixture
• Goalpost: Cryptographic observer evidence and capability proofs #58 Goalpost: Cryptographic observer evidence and capability proofs

Doctrine Locked Here

• Continuum participants are not only runtimes. Apps, debuggers, observers, membranes, compilers, agent hosts, warpspaces, adapters, fixture runtimes, and conformance harnesses may speak profiles.
• Profiles are separate from contract-family shape.
• Evidence posture is mandatory and multidimensional.
• Observation reveals; it does not author.
• WARP TTD compatibility is a profile/tier, not an automatic property.
• Jim is an Echo app; Jim/Echo integration does not go through Continuum.
• Jim, Echo, WARP TTD, Graft, WARP DRIVE, Wesley, and agents may use Continuum profiles to exchange or inspect evidence-bearing causal claims when the relevant profiles are implemented.

Done When

• continuum.participant.hello.v1 has a descriptor fixture.
• continuum.contract.index.v1 has a fixture.
• continuum.observation.v1 proves one ObservationRequest to ReadingEnvelope path.
• Evidence posture can represent native, translated, fixture, descriptor, synthetic, redacted, credential-required, partial, unsupported, and obstructed states.
• A conformance report fixture can drive qw doctor-style output.
• WARP TTD or a fixture consumer can discover a participant without app-specific code.
• Cryptographic/capability proof posture is tracked as protocol vocabulary without blocking plain evidence witnesses.

[coderabbitai]

🔗 Related PRs

#18 - Align Continuum sibling runtime doctrine [merged]
#38 - docs: adopt reader-task documentation standard as a hub 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!