T-RCXA-sdlc-lite-foreman-peer-assess-the-boundary
State: planning/backlog · Impact: low · Complexity: medium
simple-dispatch-plan.html framed itself as “an interim TypeScript peer to Foreman (PR-FRMN) … possibly part of a TypeScript-only sdlc lite.” With simple-dispatch folded into the sdlc 0.8 roadmap as design input rather than a separate track (RM-E2L0), the sdlc-lite packaging question and the Foreman peer relationship are parked, not decided. This task holds that open question until someone picks it up.
Approach
Section titled “Approach”- none yet — this is a backlog placeholder, not a scoped task. Whoever picks it up should re-read simple-dispatch-plan.html’s Goal and “sdlc wrapper and lite packaging” (P5) sections, and Foreman’s own doc, before scoping.
- n/a — a decision/research item, not implementation
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: A decision record (or a short doc) states whether sdlc-lite is built,
and if so, what it is relative to the full
solutions/ontologicalproduct and to Foreman.
Out of scope
Section titled “Out of scope”- implementing sdlc-lite or Foreman itself
Dependencies
Section titled “Dependencies”- none