Track typed Hello Echo result lifting

Outcome

Prove that the standalone application receives the exact Edict-authored GreetingCreated result through generic compiler and runtime data, without native application semantics.

Dependencies

Blocked by: flyingrobots/edict#173

Blocked by: flyingrobots/echo#698

Acceptance criteria

The compiler-emitted package retains the exact result projection from src/hello_echo.edict.
Independent verification rejects rebound or mutated result projections.
The standalone witness asserts key == "greeting" and message == "Hello Echo" from the admitted Action result.
The result and its schema identity survive WAL recovery exactly.
No Hello-specific callback or result reconstruction exists in Echo production code.

Scope

This extends Pure Hello Echo result evidence. It does not add external effects or block the durability claims proved by #3.

🔗 Related PRs

#17 - Prove durable Hello Echo execution [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!

Navigation Menu

Repository navigation

Track typed Hello Echo result lifting #18

Outcome

Dependencies

Acceptance criteria

Scope

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Track typed Hello Echo result lifting #18

Description

Outcome

Dependencies

Acceptance criteria

Scope

Activity

coderabbitai commented on Jul 28, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions