@zalom/plastic 2.0.0-alpha.2 → 2.0.0-alpha.21

package/templates/node-decision.md

@@ -0,0 +1,11 @@
+---
+node: d1
+kind: decision
+files: []
+budget: 20000
+---
+# d1 - <the decision to make>
+
+## Question
+<The question needing an owner ruling, framed so a yes/no answer or a pick
+from a short list settles it.>

package/templates/node-research.md

@@ -0,0 +1,11 @@
+---
+node: r1
+kind: research
+files: []
+budget: 60000
+---
+# r1 - <what to find out>
+
+## Deposit
+<Where the finding lands: a resources/ file, an artifact URL, or a ruling
+recorded in the intent's ## Decisions.>

package/templates/node-verify.md

@@ -0,0 +1,13 @@
+---
+node: v1
+kind: verify
+files: []
+budget: 40000
+---
+# v1 - <what this node verifies>
+
+<What this node checks, and why it gates the work nodes it needs.>
+
+## Criteria
+- <acceptance criterion one>
+- <acceptance criterion two>

package/templates/node-work.md

@@ -0,0 +1,22 @@
+---
+node: n1
+kind: work
+files: [path/to/file.rb, test/path_to_file_test.rb]
+budget: 100000
+---
+# n1 - <one-line description of what this node builds>
+
+<Why this node exists and what it changes, in a sentence or two.>
+
+## n1 failure-mode matrix
+| Operation | Failure mode | Test |
+| --- | --- | --- |
+| <operation> | <what goes wrong without this code, and its consequence> | `some_test#test_name` |
+
+## Steps
+1. Red: the matrix's tests above, committed before any code.
+2. Write the code that makes them pass.
+3. Green, then the whole suite at its baseline.
+
+## Proven by
+(filled at close from the ledger: commit, suite counts, review verdict)

package/templates/outcome.md

@@ -7,10 +7,28 @@ disposition: delivered|abandoned
 (what was delivered)
 
 ## Delivered
-- ...
+<!-- One row per thing delivered, in plain wording a reader recognizes, not
+an implementation summary; the technical detail belongs in ## Summary. Each
+row's label must appear as a standalone token in an actions/*.md OR
+nodes/*.md heading that owns the matrix table (for example "### S1 - ..."
+with a table beneath it proves row S1, or "## n1 failure-mode matrix" proves
+row n1); that heading's matrix rows become the row's Proven-by cell on the
+delivered screen (intent 317 D19, 317a, 322 D1r, 334 D10r). Readers resolve
+actions/ first, then nodes/ (334 D15r). A label with no owning heading falls
+back to a matrix row cell that carries it, when one under a heading named
+"matrix" exists (322 D3r). -->
+| Row | What |
+| --- | --- |
+| S1 | ... |
 
 ## Verification
 - <acceptance criterion> — verified by ... → result
 
+## Needs you
+<!-- The literal None, or a table shaped | N | What | Why | with one row per
+open owner action. Prose is tolerated by the reader but renders as a single
+untyped row - write the table. -->
+None
+
 ## Follow-ups
 None

package/templates/report-plan.md

@@ -0,0 +1,15 @@
+## ▶ {{id}} · {{name}} · plan
+
+| | | |
+| --- | --- | --- |
+{{fields.rows}}
+
+**Steps**
+
+| Step | Action | Detail |
+| --- | --- | --- |
+{{steps.rows}}
+
+**Risks**
+
+{{risks.block}}

package/templates/report-roadmap-delivered.md

@@ -0,0 +1,10 @@
+## ✔ {{slug}} · roadmap · delivered
+{{meta}}
+
+**Delivered**
+
+{{delivered.table}}
+
+**Log**
+
+{{log.table}}

package/templates/report-roadmap-plan.md

@@ -0,0 +1,9 @@
+## ▶ {{slug}} · roadmap · plan
+
+| | | |
+| --- | --- | --- |
+{{fields.rows}}
+
+**Batches**
+
+{{entries.table}}{{tree}}

package/templates/report-roadmap-state.md

@@ -0,0 +1,9 @@
+## ▶ {{slug}} · roadmap
+
+| | | |
+| --- | --- | --- |
+{{fields.rows}}
+
+**Batches**
+
+{{entries.table}}

package/templates/report-state.md

@@ -0,0 +1,11 @@
+## ▶ {{id}} · {{name}}
+
+| | | |
+| --- | --- | --- |
+{{fields.rows}}
+
+**Steps**
+
+| Step | Status | Detail |
+| --- | --- | --- |
+{{steps.rows}}

package/templates/roadmap.md

@@ -9,6 +9,19 @@ roadmap's goal is reached, move this file from `roadmaps/{slug}.md` to
 (a checkable prose condition — one or a few sentences a human or coordinator reads to decide the
 roadmap is done. Not an executable checker.)
 
+## Graph
+Edges, `needs` only; the head needs the tail done. The literal target `nothing` declares a root
+(an entry needing nothing). Batches below are computed from these edges, not hand-ordered; run
+`roadmap-graph check <this file>` to see the computed batches and `roadmap-graph render <this
+file>` to write them back, or `roadmap-graph migrate <this file>` on an existing graphless
+roadmap to derive edges from its current batch order instead of hand-writing them here.
+
+Grammar (fenced below so this example is never read as a real edge):
+```
+- <intent-id> needs nothing
+- <intent-id> needs <intent-id>
+```
+
 ## Batches
 Entries in a batch are parallel-safe; batches run top to bottom. The checkbox is checked once an
 entry is delivered, unchecked otherwise; the trailing token after the em-dash is the precise