B-5S6Z-model-external-out-of-corpus-triggers-as-first-class-task
Status: closed/abandoned
Today a task’s depends_on only references internal entity wikilinks (tasks/milestones), so a task
blocked by something OUTSIDE the corpus can only note it in prose — invisible to
readiness/orchestration.
Motivating case: T-3TAJ (under M-0008) is blocked by an upstream tagged release in the separate markdown-contract repo (the text-constraints feature); there is no wikilink for it. Other examples: a third-party API reaching GA, a manual human approval/sign-off, a date/scheduled event.
Idea: make external blockers first-class and machine-trackable so tooling can surface “blocked on external X” instead of burying it in prose. Two shapes to weigh:
- a new entity type (e.g. external-trigger / external-dependency) that a task
depends_onlike any other entity, or - an additional task field (e.g.
external_blockers: [{kind, ref, note, satisfied?}]).
Capture only — the exact shape (new entity vs field), how ‘satisfied’ is signalled, and how readiness/orchestrate consume it are TBD/to-design.
Closed 2026-08-16: absorbed by ledger phase E6 of D-VSLI-distributed-work-runner-architecture. External events are one of the engine’s trigger sources, so an out-of-corpus blocker is modelled as a trigger rather than a new dependency field on the work order.