Delivery Plan¶
The review created two milestones and eight remediation issues. It retained existing useful issue owners and updated current scope notes where needed. Implementation still uses the owning repository's requirement and workflow rules; no requirement status or PR merge is implied by this plan.
TechVault already lives in OpenRAE/env-packs/packs/techvault for now. #880's remaining role in this graph is consumer integration and residual APTL cleanup/parity, not an outstanding physical pack relocation. Pack authoring belongs with the existing env-packs content; backend fixes and qualification remain with the same product while its technical APTL identities are dispositioned for the LilRAE rename.
Milestones¶
| Milestone | Exit gate | Principal work |
|---|---|---|
| Local Docker isolation hardening | Exact supported local profile has enforceable authority, owned state and tested failure behavior | #955–#958, #963–#968, #856, #939, #491, #455/#456 |
| Quickstart from released artifacts | Existing packaged APTL path has truthful docs/catalog, bounded artifact availability and actionable failed-start recovery | #949, #952–#954; the tiny Hub journey remains LilRAE #10 |
| LilRAE rename: capability boundary | One product with scenario-independent lifecycle behavior, optional scenario-pack integrations, and explicit technical-identity migration | #934, #970, #878–#880, #591/#592, with LilRAE #3/#6 |
| LilRAE adoption: release qualification | Required evidence gates and exact released tiny/advanced journeys on claimed platforms | #969, #870/#685, #961, scoped user-doc work in #851; LilRAE #4/#9/#10 and Hub #3 |
The existing realization follow-up milestone owns #909/#910/#912/#915–#918 and optional scenario slices. The Arsenal milestone retains workshop delivery. Research, operator UI and broad capability milestones remain optional tracks; the backlog ledger identifies items to narrow, route or supersede.
A milestone does not itself enforce ordering. The following diagram summarizes actual GitHub dependency relationships; prerequisite points to dependent.
flowchart TD
envelope["LilRAE #6: envelope design"] --> migration["LilRAE #3: history-preserving technical cutover"]
inventory["APTL #934: ownership inventory"] --> core["APTL #970: lifecycle separation"]
ownership["APTL #964: owned resources"] --> core
core --> migration
migration --> conformance["LilRAE #4: conformance"]
envelope --> conformance
lifecycle["LilRAE #7/#8: realization and CLI"] --> security["LilRAE #9: lifecycle/security proof"]
defects["APTL #956/#963–#966/#968"] --> security
conformance --> tiny["LilRAE #10: tiny journey"]
security --> tiny
gates["APTL #969: required evidence gates"] --> tiny
gates --> advanced["APTL #870: full TechVault proof"]
advancedfixes["TechVault parity, mutation, pack and isolation fixes"] --> advanced
advanced --> platforms["APTL #685: advanced platform proof"]The full TechVault mutation backlog does not block #970 or the tiny core migration. #915 remains a prerequisite for full TechVault qualification. Likewise optional agent-control mechanisms and paired BigRAE research are not global quickstart dependencies. An unsupported capability must be omitted/rejected until its profile-specific evidence exists.
Issue definitions¶
- #963: fix: enforce participant process deadlines and descendant cleanup.
- #964: fix: refuse foreign containers before reuse or replacement.
- #965: fix: require operator grants for pack-to-container credential bindings.
- #966: fix: write generated container env files without following links.
- #967: fix: validate MCP tool arguments at the server boundary.
- #968: feat: enforce and disclose egress for the ordinary local range.
- #969: ci: gate adoption on platform security and declared conformance evidence.
- #970: refactor: separate generic lab lifecycle from scenario-pack startup hooks.
Dependency changes¶
45 new blocking relationships were read back from GitHub. One obsolete relationship was removed: LilRAE #6 (envelope design) previously waited for LilRAE #4 (conformance proof). Design now precedes migration and conformance. Existing unrelated dependencies were retained. The inspected graph passes a cycle check, and GitHub accepted every added relationship.
The exact delta and verified targets are recorded in
dependency-changes.json. Dependencies use GitHub's
native REST issue-dependency endpoints through gh api, not body text alone.
These relationships make prerequisites visible and queryable; GitHub does not
thereby prevent an authorized user from closing an issue or merging a PR. The
implementation/release workflow must check dependency completion as part of its
own gate. GitHub issue dependency API.
Work that can start now¶
- Fix the independently reproduced #963–#967 defects and #956 admission bypass.
- Decide the capability/ownership boundaries in LilRAE #6 and APTL #934 using the proposed ADRs and this baseline; prepare contract and negative tests.
- Build #969 gate infrastructure while fixes proceed; qualification cannot pass a profile whose required fixes and evidence remain incomplete.
- Prepare acquired-pack, clean-machine and failure-path test harnesses without treating preparation as proof of a successful live run.
No code fix, release, branch promotion, feature-PR closure or merge was performed by the review. Existing issue supersession/closure remains a recommendation until its replacement owner and acceptance evidence are reconciled.