Repository navigation
Implement the self-hosted delivery loop capstone #14
Description
Activity
🔗 Related PRs
#6 - Establish delivery-loop hosting feasibility [open]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand 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!
Roadmap Ω outcome
Execute the committed phase graph as an Edict program over proven Echo external-action and schema-validated judgment adapters.
Success criterion
Edict emits only declared, bounded requests. Echo records every request before execution and every settlement before resumption. Adapters alone possess external authority. Replay never reissues settled effects. Ambiguous outcomes become typed obstructions. Model output is admitted only as schema-validated proposal data.
Unauthorized operation families fail compilation or package verification. Unauthorized runtime instances fail closed through typed admission obstructions before adapter execution.
Prerequisites
The native dependency edge to #13 is maintained through GraphQL.
Non-goals