Prove bounded workspace observation through durable settlement

[flyingrobots]

Outcome

Hello Effect observes one bounded workspace file or snapshot through the Edict request → Echo history → adapter settlement boundary.

Acceptance

• exact Edict source constructs the declared observation request;
• Echo admits the request before the adapter reads the workspace;
• path/root scope, byte budget, symlink policy, and source basis are explicit;
• the adapter returns schema-bound bytes or content references plus basis evidence;
• Echo admits the settlement before the Edict state machine resumes;
• duplicate identical settlement is idempotent and conflicting settlement obstructs;
• unauthorized and escaped paths obstruct before the read;
• restart recovers an unclaimed or claimed request without inventing an outcome;
• ambiguous execution records outcome_unknown rather than failed;
• replay consumes the recorded settlement and does not reread the workspace;
• the compiler/provider seam remains capability-denied.

Dependencies

• Prove durable scheduler-owned Hello Echo execution #3 — Pure Hello Echo runtime proof;
• Specify durable external-action request and settlement protocol echo#694 — durable request/claim/settlement protocol;
• Declare typed external-action request values edict#172 — typed external request construction;
• Emit canonical external-request application artifacts edict#176 — canonical public external-request application artifacts;
• Host bounded workspace observation through external-action settlement echo#705 — bounded workspace-observation adapter and generic host witness.

Native blocked by edges are maintained through GraphQL.

[coderabbitai]

🔗 Related PRs

#6 - Establish delivery-loop hosting feasibility [merged]
#15 - Restore Pure Hello Echo as Roadmap A [merged]
#17 - Prove durable Hello Echo execution [merged]
#20 - Record dependency-satisfied review outcomes [merged]
#21 - Prove typed Hello Echo result recovery [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!