tegwick
d4080de393
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).
53 lines
1.1 KiB
Markdown
53 lines
1.1 KiB
Markdown
# Decision: Confirm initial activation levels
|
|
|
|
Status: Open
|
|
Date: 2026-06-22
|
|
Record: DEC-001
|
|
|
|
## Context
|
|
|
|
`PROJECT_LANDSCAPE.md` assigns activation levels to each organization in the
|
|
forge landscape. These levels govern how much delivery pressure each topic
|
|
receives and which items may become commitments.
|
|
|
|
## Options
|
|
|
|
### Option 1 — Accept draft levels as proposed
|
|
|
|
| Organization | Level |
|
|
|---|---|
|
|
| binky | A3 Critical |
|
|
| tegwick | A2 Active |
|
|
| helix | A2 Active |
|
|
| coulomb | A1/A2 Controlled |
|
|
| sloppers | A1 Incubating |
|
|
| whywhynot | A1 Incubating |
|
|
| plenitude | A1 Incubating |
|
|
|
|
### Option 2 — Adjust before accepting
|
|
|
|
Change one or more levels after review of current energy, obligations, and
|
|
survival priorities.
|
|
|
|
### Option 3 — Defer
|
|
|
|
Keep levels as draft annotations until Binky critical path is visible
|
|
(TEGWICK-WP-0003).
|
|
|
|
## Decision
|
|
|
|
Pending human confirmation.
|
|
|
|
## Rationale
|
|
|
|
(To be filled when accepted or rejected.)
|
|
|
|
## Consequences
|
|
|
|
Accepted levels flow into area cards, `TASKS.md` prioritization, and agent task
|
|
approval boundaries.
|
|
|
|
## Review
|
|
|
|
Revisit during monthly landscape review or when Binky stabilization changes
|
|
survival pressure. |