Complete TEGWICK-WP-0002 personal project intake scaffold
Establish the capture-to-commitment pipeline with INTAKE.md, structured agent-tasks/ and decisions/ layouts, and seed the first prioritized workstream (TEGWICK-WP-0003 Binky critical path visibility).
This commit is contained in:
18
DECISIONS.md
18
DECISIONS.md
@@ -1,5 +1,14 @@
|
||||
# Decisions
|
||||
|
||||
## Registry
|
||||
|
||||
Structured records live in `decisions/`. This file is the index.
|
||||
|
||||
| ID | Title | Status | Record |
|
||||
|---|---|---|---|
|
||||
| DEC-001 | Confirm initial activation levels | open | `decisions/DEC-001-activation-levels.md` |
|
||||
| DEC-002 | Confirm tegwick-control as root control repo | open | `decisions/DEC-002-root-control-repo.md` |
|
||||
|
||||
## Open Decisions
|
||||
|
||||
### DEC-001 — Confirm initial activation levels
|
||||
@@ -16,7 +25,8 @@ Current proposal:
|
||||
- whywhynot: A1 Incubating
|
||||
- plenitude: A1 Incubating
|
||||
|
||||
Status: open
|
||||
Status: open
|
||||
Record: `decisions/DEC-001-activation-levels.md`
|
||||
|
||||
---
|
||||
|
||||
@@ -24,7 +34,8 @@ Status: open
|
||||
|
||||
Should `tegwick-control` be treated as the root control repo for the whole landscape?
|
||||
|
||||
Status: open
|
||||
Status: open
|
||||
Record: `decisions/DEC-002-root-control-repo.md`
|
||||
|
||||
---
|
||||
|
||||
@@ -34,4 +45,5 @@ None yet.
|
||||
|
||||
## Decision Record Format
|
||||
|
||||
Use `templates/decision-record.md` for structured decision records.
|
||||
Copy `templates/decision-record.md` into `decisions/DEC-NNN-<slug>.md` and add
|
||||
a registry row above. See `decisions/README.md` for layout and lifecycle.
|
||||
Reference in New Issue
Block a user