Skip to content

Slice: Define Jim-to-Echo CausalAnchor API boundary #219

Closed
#265
Closed
Slice: Define Jim-to-Echo CausalAnchor API boundary#219
#265
Labels
causal-ropeCausal rope text authority roadmapenhancementNew feature or requestsliceImplementable roadmap slicetext-authorityText authority and storage invariantswork-in-progressCycle or PR is intentionally in progress and not ready to merge
Milestone
CR-01 - Echo CausalAnchor integration

Description

@flyingrobots
flyingrobots
opened on Jul 6, 2026

Goal

Define a narrow Jim-facing capability for requesting Echo-owned causal-anchor admission without making Echo know about ropes or copying Echo protocol semantics into Jim.

Acceptance criteria

  • Jim validates checkpoint identity, worldline, rope head, checkpoint reason, and optional materialization-root roles before invoking the capability.
  • The capability returns opaque Echo anchor, fact, and receipt identities.
  • Jim does not derive Echo basis frontiers, identity algorithms, digest domains, receipts, WAL evidence, support policy, or retention policy.
  • Operations that require anchor admission require explicit capability injection and fail closed when unavailable.
  • The handwritten port is documented as a transitional single-operation seam to be replaced by a generated Edict client.

Activity

  1. flyingrobots
    added this to the CR-01 - Echo CausalAnchor integration milestone on Jul 6, 2026
  2. flyingrobots
    added
    causal-ropeCausal rope text authority roadmap
    sliceImplementable roadmap slice
    text-authorityText authority and storage invariants
    on Jul 6, 2026

  3. coderabbitai commented on Jul 6, 2026

    @coderabbitai
    coderabbitaibot
    on Jul 6, 2026 – with coderabbitai
    🔗 Related PRs

    #205 - Document graph-backed rope runtime gate [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!

  4. coderabbitai
    added
    enhancementNew feature or request
    work-in-progressCycle or PR is intentionally in progress and not ready to merge
    on Jul 6, 2026
  5. flyingrobots
    closed this as completedin #265on Jul 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    causal-ropeCausal rope text authority roadmapenhancementNew feature or requestsliceImplementable roadmap slicetext-authorityText authority and storage invariantswork-in-progressCycle or PR is intentionally in progress and not ready to merge

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions