You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Choose the delivery boundary for file-content matches #40
Given the OpenCode v1.x feasibility findings, what delivery and persistence boundary should the specification require for a rule newly selected by a file observation? Decide whether immediate next-dispatch durable delivery belongs in this feature, how it fits the existing delivery coordinator and ledger, and what limitation remains if v1.x cannot support that boundary.
File-content matching will not own a special delivery path. It depends on Specify earliest-dispatch delivery for every newly matched rule, which will define one implementation-ready OpenCode v1.x contract for every rule newly matched from any supported session-context change.
A rule must be visible at the earliest applicable provider dispatch: the current initial dispatch when its context is already known, or the immediately following dispatch after a mid-session context change.
Rule lifetime is preserved: durable rules are persisted in history; transient rules remain dispatch-local.
The existing RuleDelivery coordinator remains authoritative for per-session serialization, identity deduplication, history reconciliation, and ledger acknowledgement. Tool hooks and other context producers submit matches but do not maintain parallel delivery state.
If durable synthetic persistence fails, pending content is still exposed through the message transform for the next dispatch, remains unacknowledged, and is retried later.
Concurrent matches may produce multiple synthetic messages with unspecified cross-tool order. The contract requires per-identity deduplication and visibility before the next dispatch, not batching.
Delivery failures are isolated from successful tool execution: they retain pending state and must not turn a successful tool result into a failure.
Activity
frap129 commentedon Aug 28, 2026
Resolution
File-content matching will not own a special delivery path. It depends on Specify earliest-dispatch delivery for every newly matched rule, which will define one implementation-ready OpenCode v1.x contract for every rule newly matched from any supported session-context change.
RuleDeliverycoordinator remains authoritative for per-session serialization, identity deduplication, history reconciliation, and ledger acknowledgement. Tool hooks and other context producers submit matches but do not maintain parallel delivery state.Every remaining file-content decision is blocked on the universal delivery contract by request.