Clear the shared pipeline dependency blocker

This commit is contained in:
2026-09-14 23:48:26 +00:00
parent 7d92867ba7
commit fa348e9376
4 changed files with 21 additions and 21 deletions

View File

@@ -1,6 +1,6 @@
# Feature 0009: Shared Pipeline Filesystem and Execution
Status: ready
Status: in_progress
## Summary

View File

@@ -844,9 +844,10 @@ The final handoff must:
## Progress Notes
No implementation stages have begun. Record only concise stage commit hashes
and blockers here during execution; preserve detailed evidence in the stage
commits and final handoff.
Stages 1 through 4 and the dependency-publication checkpoint are complete.
Resume at Stage 5. Continue recording only concise stage commit hashes and
blockers here; preserve detailed evidence in the stage commits and final
handoff.
- [x] Stage 1 complete — `ansible-role-audita` commit `66ebea9`; full
integration, native validation, and clean repeats passed. No deviations.
@@ -858,9 +859,6 @@ commits and final handoff.
deviations.
- [x] Stage 4 complete — `ansible-role-narratio` commit `eeb1105`; full
integration, native validation, and clean repeats passed. No deviations.
- Blocked before Stage 5: fresh canonical-origin fetches cannot resolve
Audita `66ebea9a47ce82bfdbdc5e2855f3dfaaff8e2a16`, Notarius
`e9ae2dc34023e1e8462bf0991de62b97d8c0e0ee`, Scriptorium
`8b4c86e48e7d8655e479b26dc510bf01683a0c8f`, or Narratio
`eeb1105590e638c1f46b42c98a5dbbce4ddeea86`. Publication is required;
implementation does not push.
- [x] Dependency publication checkpoint complete — the four Stage 1–4 commits
are available from their canonical `origin/main` branches at the exact
immutable revisions listed above. Stage 5 may begin.

View File

@@ -19,11 +19,12 @@ documents the interface. No redundant inspection, corrective convergence,
private state, or unrelated application behavior was introduced. All four
repository-local integration suites passed independently during review.
Feature 0009 as a whole is not implemented. The active implementation plan and
workspace status correctly record a publication blocker after Stage 4. The
pipeline repository remains at pre-feature commit `3e253d7`; Stages 5 through
8 have not been executed. The following findings therefore describe missing
target architecture rather than defects in the completed standalone commits.
Feature 0009 as a whole is not implemented. The pipeline repository remains at
pre-feature commit `3e253d7`; Stages 5 through 8 have not been executed. The
publication blocker encountered after Stage 4 has now been cleared: all four
standalone commits are available from their canonical origins. The following
findings therefore describe the remaining target architecture rather than
defects in the completed standalone commits.
## Finding 1: The Pipeline Does Not Select the Shared Configuration Policy
@@ -45,8 +46,8 @@ before the other configuration-bearing dependencies run.
### Required Remediation
- Publish the four reviewed standalone-role commits so immutable dependency
installation can resolve them; do not replace commit pins with branches.
- Use the four published, immutable standalone-role commits recorded above;
do not replace their commit pins with branches.
- Execute Stage 5 of `docs/roadmap/implementation.md` in full.
- Add the four suite defaults and argument-spec entries, run Narratio first,
pass the selected identity and modes through every generic role interface,
@@ -166,3 +167,5 @@ implementation repositories remained clean after testing.
The pipeline suite was not presented as Feature 0009 validation evidence
because the pipeline repository contains no Feature 0009 implementation
commits. Its current test suite exercises the prior Feature 0008 architecture.
After review, each standalone commit was pushed to its canonical `origin/main`
branch and the local and remote-tracking revisions were confirmed identical.

View File

@@ -4,8 +4,7 @@ Last updated: 2026-09-14
Current milestone: M1-03 suite-level pipeline role
Current focus: Publish the completed standalone-role commits required to resume
the Feature 0009 implementation sprint.
Current focus: Resume the Feature 0009 implementation sprint at Stage 5.
| ID | Deliverable | Owner | State | Evidence or next step |
| --- | --- | --- | --- | --- |
@@ -16,7 +15,7 @@ the Feature 0009 implementation sprint.
| M0-05 | Suite-level role repository | ansible-role-dnd-pipeline | done | Repository created and added to `workspace.yml` |
| M1-01 | Remaining MVP design decisions | workspace | done | Feature 0003 roadmap fixes the Notarius configuration interface |
| M1-02 | Standalone application roles | role repositories | done | All five standalone roles implemented and independently reviewed |
| M1-03 | Suite-level pipeline role | ansible-role-dnd-pipeline | blocked | Await publication of Feature 0009 standalone-role commits before pipeline dependency installation |
| M1-03 | Suite-level pipeline role | ansible-role-dnd-pipeline | in_progress | Execute Feature 0009 Stages 5–8 using the published standalone-role commits |
| M1-04 | Collection assembly | ansible-collection-dnd | proposed | Select and implement the pipeline-role incorporation mechanism |
| F0001 | Install Seriatim from pinned source | ansible-role-seriatim | done | Implementation, integration coverage, and final remediation completed through `fb8dc41` |
| F0002 | Install and configure Audita | ansible-role-audita | done | Field-specific configuration completed in `e61f02f` and `847c4c3`; full suite passed |
@@ -26,7 +25,7 @@ the Feature 0009 implementation sprint.
| F0006 | Establish pipeline-role composition | ansible-role-dnd-pipeline | done | Implemented and validated through remediation commit `4ea4358` |
| F0007 | Deploy D&D campaigns and prompt assets | ansible-role-dnd-pipeline, campaigns, and narratio-prompts | done | Implemented and validated through remediation commit `7572fa3` |
| F0008 | Define opinionated D&D processing configuration | ansible-role-dnd-pipeline | done | Implemented and independently reviewed through remediation commit `3e253d7` |
| F0009 | Establish shared pipeline filesystem and execution | configuration-bearing application roles and ansible-role-dnd-pipeline | blocked | Stages 1–4 passed; publish their commits before Stage 5 can install immutable dependencies |
| F0009 | Establish shared pipeline filesystem and execution | configuration-bearing application roles and ansible-role-dnd-pipeline | in_progress | Stages 1–4 are published; resume at Stage 5 in `docs/roadmap/implementation.md` |
| F0010 | Integrate D&D Notarius extraction | ansible-role-notarius and ansible-role-dnd-pipeline | proposed | Depends on Feature 0009; review `docs/roadmap/features/0010-dnd-notarius-extraction-integration.md` |
| A0001 | Audit completed standalone-role test suites | workspace and standalone roles | done | Findings recorded in `docs/roadmap/test-suite-audit-findings.md` |
| R0001 | Simplify completed standalone-role test suites | workspace and standalone roles | done | Role commits `e08c63c`, `d2d0b9d`, and `cfecf37` passed implementation and independent review |