Skip to content

[CA-01-S1] Define trusted causal-anchor admission boundary #662

Closed
Closed
[CA-01-S1] Define trusted causal-anchor admission boundary#662
Labels
coreEcho Core TechnologiesenhancementNew feature or requestpriority:highMethod priority high.runtimeRuntime coretaskSmall, 1–3h tasktype:enhancementMethod work type enhancement.work-in-progressSomeone is actively working this issue.
Milestone
CA-01 - Trusted causal anchor admission

Description

@flyingrobots
flyingrobots
opened on Jul 14, 2026

Goal

Define the durable authority boundary for application-requested, Echo-admitted causal anchors.

Acceptance criteria

  • An accepted ADR distinguishes canonical anchor value construction from trusted admission.
  • The app request does not supply or self-issue an Echo admission receipt.
  • Echo owns admission identity, receipt identity, ordering, and publication.
  • Domain root semantics remain application-owned; Echo validates only generic causal support and declared root policy.
  • Causal anchors, materialization caches, and physical retention pins remain separate concepts.
  • Deterministic contract witnesses fail before implementation and pass after it.

Activity

  1. flyingrobots
    added this to the CA-01 - Trusted causal anchor admission milestone on Jul 14, 2026
  2. flyingrobots
    added
    runtimeRuntime core
    coreEcho Core Technologies
    priority:highMethod priority high.
    type:enhancementMethod work type enhancement.
    on Jul 14, 2026

  3. coderabbitai commented on Jul 14, 2026

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

    #358 - feat(core): add admission evidence boundaries [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
    taskSmall, 1–3h task
    work-in-progressSomeone is actively working this issue.
    on Jul 14, 2026

  5. flyingrobots commented on Jul 15, 2026

    @flyingrobots
    flyingrobots
    on Jul 15, 2026
    OwnerAuthor

    Implemented in d89db8d. ADR 0022 and deterministic witnesses now separate application claims from Echo-owned admission, remove caller-issued receipt identity, define generic root-support policy, and keep anchors distinct from materializations and retention pins.

  6. flyingrobots
    closed this as completedon 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

    coreEcho Core TechnologiesenhancementNew feature or requestpriority:highMethod priority high.runtimeRuntime coretaskSmall, 1–3h tasktype:enhancementMethod work type enhancement.work-in-progressSomeone is actively working this issue.

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions