Skip to content

Expose independently comparable typed result recovery evidence #702

Closed
#703
Closed
Expose independently comparable typed result recovery evidence#702
#703
Labels
enhancementNew feature or requestfeatureFeature umbrella (epic)legend:testMethod legend test.needs-witnessMethod closeout state needs-witness.priority:highMethod priority high.roadmap-aRoadmap A: standalone Hello Echo deliveryruntimeRuntime corespecSpec/Design documenttoolingTooling/CI/CLItype:enhancementMethod work type enhancement.
Milestone
Hello Echo Scheduler Runtime

Description

@flyingrobots
flyingrobots
opened on Jul 29, 2026

Outcome

Expose schema-neutral result evidence from original execution, fresh-host recovery, and recovered WAL outcome so an external application can independently compare the exact compiler-authored typed result across recovery.

Acceptance criteria

  • The generic runner reports the original, fresh-host recovered, and WAL-recovered application-result evidence as typed schema-neutral fields.
  • Each report carries the projection identity, output type, canonical bytes, and result identity already admitted by Echo.
  • A passing witness requires all three reports to be byte-identical.
  • Negative runner coverage proves substituted recovery or WAL result evidence cannot produce a passing witness.
  • No Hello Echo vocabulary, native callback, or application-specific decoder enters Echo production code.

Downstream

Blocks flyingrobots/hello-echo#18.

Activity

  1. flyingrobots
    added this to the Hello Echo Scheduler Runtime milestone on Jul 29, 2026
  2. flyingrobots
    added
    roadmap-aRoadmap A: standalone Hello Echo delivery
    on Jul 29, 2026
  3. flyingrobots
    marked this as blocking on Jul 29, 2026

  4. coderabbitai commented on Jul 29, 2026

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

    #609 - feat(warp-core): project WAL recovery evidence [merged]
    #683 - Execute admitted data-only operations in Echo [merged]
    #695 - Run compiler-produced Edict operations through durable Ticks [merged]
    #700 - Expose duplicate state evidence from the generic runner [merged]
    #701 - Evaluate package-declared typed application results [open]

    📝 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!

  5. coderabbitai
    added
    enhancementNew feature or request
    featureFeature umbrella (epic)
    legend:testMethod legend test.
    needs-witnessMethod closeout state needs-witness.
    priority:highMethod priority high.
    runtimeRuntime core
    specSpec/Design document
    toolingTooling/CI/CLI
    type:enhancementMethod work type enhancement.
    on Jul 29, 2026
  6. flyingrobots
    closed this as completedin #703on Jul 29, 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

    enhancementNew feature or requestfeatureFeature umbrella (epic)legend:testMethod legend test.needs-witnessMethod closeout state needs-witness.priority:highMethod priority high.roadmap-aRoadmap A: standalone Hello Echo deliveryruntimeRuntime corespecSpec/Design documenttoolingTooling/CI/CLItype:enhancementMethod work type enhancement.

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions