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).

decisions/DEC-001-activation-levels.md

@@ -0,0 +1,53 @@
+# 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.

decisions/DEC-002-root-control-repo.md

@@ -0,0 +1,46 @@
+# Decision: Confirm tegwick-control as root control repo
+
+Status: Open  
+Date: 2026-06-22  
+Record: DEC-002
+
+## Context
+
+Multiple organizations (binky, helix, coulomb, sloppers, whynot, plenitude)
+each may eventually have their own control repositories. The landscape needs a
+single personal operating layer that coordinates without absorbing all work.
+
+## Options
+
+### Option 1 — tegwick-control is the root control repo
+
+`tegwick-control` holds the personal landscape map, cross-org priorities, and
+intake pipeline. Organization-specific control repos (e.g. `whynot-control`)
+handle domain-specialized intake.
+
+### Option 2 — Shared neutral repo
+
+A non-personal-named repo serves as root; tegwick-control becomes one area
+among equals.
+
+### Option 3 — Defer
+
+Operate with tegwick-control as provisional root until another structure proves
+necessary.
+
+## Decision
+
+Pending human confirmation.
+
+## Rationale
+
+(To be filled when accepted or rejected.)
+
+## Consequences
+
+If Option 1 is accepted, landscape reviews, activation guardrails, and
+cross-org workstream priority default to this repository.
+
+## Review
+
+Revisit if a second root-level control repo creates conflicting priorities.

decisions/README.md

@@ -0,0 +1,57 @@
+# Decision Log
+
+Structured, append-only decision records for `tegwick-control`.
+
+## Purpose
+
+Decisions that affect activation levels, commitments, governance, or landscape
+priority belong here — not only as inbox notes or task bullets.
+
+## Layout
+
+```text
+decisions/
+├── README.md                    this file
+├── DEC-NNN-<slug>.md            individual decision records
+└── archive/                     superseded records (optional)
+```
+
+## Naming
+
+```text
+DEC-NNN-<slug>.md
+```
+
+- `NNN` — three-digit sequence (`001`, `002`, …)
+- `slug` — short kebab-case topic (`activation-levels`, `root-control-repo`)
+
+## Registry
+
+`DECISIONS.md` at the repo root is the **index**: open decisions, resolved
+decisions, and pointers to full records in this folder.
+
+When creating a new decision:
+
+1. Allocate the next `DEC-NNN` id from `DECISIONS.md`.
+2. Copy `templates/decision-record.md` into `decisions/DEC-NNN-<slug>.md`.
+3. Add a summary entry to `DECISIONS.md` under Open or Resolved.
+
+## Status values
+
+| Status | Meaning |
+|---|---|
+| Open | Under consideration; no choice yet |
+| Accepted | Decision made and in effect |
+| Rejected | Option explicitly declined |
+| Superseded | Replaced by a later decision |
+
+Update both the record file and `DECISIONS.md` when status changes.
+
+## Intake path
+
+```text
+inbox/ or area card → triage → decisions/DEC-NNN-<slug>.md → DECISIONS.md index
+```
+
+Agents may draft decision records but must not mark `Accepted` without human
+approval per `AGENT_RULES.md`.