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

INTAKE.md

@@ -0,0 +1,128 @@
+# Intake Pipeline
+
+## Purpose
+
+This document defines how personal projects, commitments, and agent work enter
+`tegwick-control` without turning every idea into immediate obligation.
+
+## Principle
+
+Capture is not commitment. Items move through explicit stages; each stage has
+a home and a clear exit criterion.
+
+## Stages
+
+### Stage 0 — Capture
+
+Save loose material without classifying it.
+
+| Location | Use for |
+|---|---|
+| `inbox/` | Rough notes, pasted thoughts, urgent fragments, questions |
+
+**Exit:** Item is saved and no longer held in memory.
+
+---
+
+### Stage 1 — Triage
+
+During weekly or monthly review, decide what the item is.
+
+| Question | Guides toward |
+|---|---|
+| Is this a one-off action? | `TASKS.md` |
+| Does it belong to a known area? | `areas/<area>.md` |
+| Does it need a choice before action? | `decisions/` |
+| Is it multi-step structured work? | `workplans/` |
+| Is it bounded agent work in this repo? | `agent-tasks/` |
+| Is it implementation work in another repo? | Agent task + target repo |
+| Is it interesting but not active? | Area card options, or park |
+| Is it noise? | Delete or archive from inbox |
+
+**Outcomes:** route, park, merge, or reject. Do not create commitments during
+capture.
+
+---
+
+### Stage 2 — Classify
+
+Assign a work class (see `OPERATING_MODEL.md`):
+
+| Class | Typical home |
+|---|---|
+| Commitment | `TASKS.md` + area card |
+| Option | Area card `Options` section |
+| Exploration | Area card or `inbox/` until clearer |
+| Decision | `decisions/DEC-NNN-<slug>.md` |
+| Waiting | `TASKS.md` (Waiting section) |
+| Routine | Area card or `REVIEW_RHYTHM.md` |
+| Someday | Area card, A0/A1 only |
+
+---
+
+### Stage 3 — Prepare
+
+Before agent delegation or activation:
+
+1. Confirm activation level in `PROJECT_LANDSCAPE.md` and the area card.
+2. Define boundaries (allowed/forbidden changes, approval gates).
+3. For repo work: name target repo, expected output, acceptance criteria.
+4. For decisions: write options and consequences before choosing.
+
+**Agent tasks** use `templates/agent-task.md`.  
+**Decisions** use `templates/decision-record.md`.  
+**Multi-task work** uses `workplans/TEGWICK-WP-NNNN-<slug>.md`.
+
+---
+
+### Stage 4 — Activate
+
+A item becomes active work only when it has:
+
+- an owner;
+- a clear next action;
+- a reason for acting now;
+- a defined review surface.
+
+Commitments appear in `TASKS.md`. Structured strands appear in `workplans/`.
+Bounded agent prompts appear in `agent-tasks/`.
+
+---
+
+### Stage 5 — Review and Close
+
+| Surface | Review question |
+|---|---|
+| `TASKS.md` | Still a true commitment? |
+| `decisions/` | Resolved, superseded, or still open? |
+| `agent-tasks/` | Done, blocked, or needs rescoping? |
+| `workplans/` | Tasks progressing; workstream still aligned? |
+| `areas/` | Activation level and next surface still correct? |
+
+Use `templates/weekly-review.md` for the weekly pass.
+
+## Folder Map
+
+```text
+inbox/              temporary capture (Stage 0)
+areas/              per-topic control cards (organizations and life domains)
+TASKS.md            current commitments index
+decisions/          structured decision records (append-only log)
+DECISIONS.md        decision registry (open + resolved index)
+agent-tasks/        bounded, approval-aware agent prompts for this repo
+workplans/          State Hub–synced multi-task workstreams
+templates/          blank forms for cards, tasks, decisions, reviews
+```
+
+## Activation Guardrail
+
+Do not promote A1 Incubating topics to A2 Active or A3 Critical without an
+explicit decision in `decisions/` and human approval per `AGENT_RULES.md`.
+
+## Current Prioritized Workstream
+
+After intake scaffold (TEGWICK-WP-0002), the first prioritized workstream is
+**Binky critical path visibility** — see `workplans/TEGWICK-WP-0003-binky-critical-path.md`.
+
+This follows `PROJECT_LANDSCAPE.md` current focus: stabilize `tegwick-control`,
+then make Binky's survival situation explicit without solving everything at once.

OPERATING_MODEL.md

@@ -43,9 +43,13 @@ The purpose is continuous progress, not constant pressure.
 | Surface | Purpose |
 |---|---|
 | `TASKS.md` | Current actionable work |
-| `DECISIONS.md` | Open and resolved decisions |
+| `DECISIONS.md` | Decision registry (index) |
+| `decisions/` | Structured decision records |
+| `INTAKE.md` | Capture-to-commitment pipeline |
 | `PROJECT_LANDSCAPE.md` | Major topic map |
 | `areas/` | Per-topic notes and control cards |
+| `agent-tasks/` | Bounded agent prompts |
+| `workplans/` | Prioritized multi-task workstreams |
 | `WORKPLAN.md` | Sequenced setup plan |
 | `inbox/` | Temporary capture area |
 

README.md

@@ -10,9 +10,20 @@ Start here:
 
 1. Read `INTENT.md`.
 2. Review `PROJECT_LANDSCAPE.md`.
-3. Use `WORKPLAN.md` to establish the repository step by step.
-4. Capture loose thoughts in `inbox/`.
-5. Convert only selected items into commitments in `TASKS.md`.
+3. Read `INTAKE.md` for how items move from capture to commitment.
+4. Use `WORKPLAN.md` to establish the repository step by step.
+5. Capture loose thoughts in `inbox/`.
+6. Convert only selected items into commitments in `TASKS.md`.
+
+## Intake Surfaces
+
+| Surface | Role |
+|---|---|
+| `inbox/` | Temporary capture |
+| `INTAKE.md` | Triage and routing pipeline |
+| `decisions/` | Structured decision log |
+| `agent-tasks/` | Bounded agent prompts |
+| `workplans/` | Prioritized multi-task workstreams |
 
 ## Core Principle
 

agent-tasks/README.md

@@ -0,0 +1,82 @@
+# Agent Tasks
+
+Bounded, approval-aware prompts for agents working in `tegwick-control`.
+
+## When to use
+
+Create an agent task when:
+
+- the work stays inside this repository (drafting, structuring, summarizing);
+- boundaries and forbidden changes are clear;
+- human approval gates are explicit;
+- the task is ready to hand to an agent without further triage.
+
+Do **not** use agent tasks for:
+
+- implementation work in other repos (prepare the prompt here, execute elsewhere);
+- legal, tax, or financial conclusions;
+- converting options into commitments without approval.
+
+## Layout
+
+```text
+agent-tasks/
+├── README.md                          this file
+├── <area>-<action>-<subject>.md       ready agent prompts
+└── archive/                           completed or superseded tasks
+```
+
+Flat layout by default. Move finished tasks to `archive/` during review.
+
+## Naming
+
+```text
+<area>-<action>-<subject>.md
+```
+
+| Segment | Examples |
+|---|---|
+| area | `tegwick`, `binky`, `helix`, `coulomb` |
+| action | `review`, `surface`, `draft`, `classify` |
+| subject | `critical-path`, `area-cards`, `migration-slice` |
+
+Examples:
+
+- `binky-surface-critical-path.md`
+- `tegwick-review-area-cards.md`
+
+## File format
+
+Copy `templates/agent-task.md` and fill every section. Required sections:
+
+- Goal
+- Context
+- Allowed Changes
+- Forbidden Changes
+- Expected Output
+- Acceptance Criteria
+- Human Approval Required For
+
+## Lifecycle
+
+| State | Meaning | Location |
+|---|---|---|
+| Seed | Bootstrap or historical reference | root or `archive/` |
+| Ready | Approved for agent execution | root |
+| Done | Completed; move to `archive/` | `archive/` |
+
+Track state in the task file header:
+
+```markdown
+Status: ready | done | superseded
+Workplan: TEGWICK-WP-NNNN (if linked)
+Area: binky | tegwick | helix | ...
+```
+
+## Intake path
+
+```text
+inbox/ → triage (INTAKE.md) → agent-tasks/ → agent session → archive/
+```
+
+See `INTAKE.md` for the full pipeline.

agent-tasks/binky-surface-critical-path.md

@@ -0,0 +1,72 @@
+# Agent Task: Surface Binky critical path
+
+Status: ready  
+Workplan: TEGWICK-WP-0003  
+Area: binky
+
+## Goal
+
+Populate `areas/binky-company.md` with an initial critical-path view: open
+obligations, survival risks, business model options, and the next visible
+surfaces — without making legal, tax, or financial conclusions.
+
+## Context
+
+Binky is A3 Critical in `PROJECT_LANDSCAPE.md`. The area card is still seed
+content. TEGWICK-WP-0003 breaks visibility work into structured tasks. This
+agent task covers the drafting pass across T01–T03.
+
+Human must supply or confirm factual details (dates, amounts, filing status).
+Use `[NEEDS HUMAN INPUT]` markers where facts are unknown.
+
+## Inputs
+
+- `areas/binky-company.md`
+- `PROJECT_LANDSCAPE.md`
+- `WORKPLAN.md` (Phase 2)
+- `workplans/TEGWICK-WP-0003-binky-critical-path.md`
+- `INTAKE.md`, `AGENT_RULES.md`
+
+## Allowed Changes
+
+The agent may:
+
+- edit `areas/binky-company.md` (Current State, Commitments, Options, Risks,
+  Open Decisions, Next Surface);
+- add clearly marked placeholders for unknown facts;
+- propose draft entries for `TASKS.md` (T04, T05) as commented suggestions in
+  the area card, not as live commitments.
+
+## Forbidden Changes
+
+The agent must not:
+
+- state legal, tax, or accounting conclusions as facts;
+- create payment, filing, or contract instructions;
+- add secrets, credentials, or private account data;
+- mark items as commitments in `TASKS.md` without explicit human approval;
+- change Binky's activation level;
+- create or modify other repositories.
+
+## Expected Output
+
+Updated `areas/binky-company.md` containing:
+
+1. **Open obligations** — legal, tax, accounting (with unknowns marked).
+2. **Survival risks** — ranked by urgency where possible.
+3. **Business model options** — separated from commitments.
+4. **Next surface** — what human review should tackle first.
+
+## Acceptance Criteria
+
+- Area card is no longer generic seed text in the critical-path sections.
+- Options and commitments are clearly separated.
+- No item is presented as resolved fact without source or human confirmation.
+- TEGWICK-WP-0003 T01–T03 can be marked done after human review of the draft.
+
+## Human Approval Required For
+
+- Converting any draft item into a `TASKS.md` commitment;
+- Changing activation level;
+- Any statement presented as legal, tax, or financial fact;
+- Contacting advisors, authorities, or third parties.

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

workplans/TEGWICK-WP-0002-personal-project-intake.md

@@ -4,11 +4,11 @@ type: workplan
 title: "Personal project intake scaffold"
 domain: consumer
 repo: tegwick-control
-status: ready
+status: finished
 owner: codex
 topic_slug: consumer
 created: "2026-06-22"
-updated: "2026-06-22"
+updated: "2026-06-24"
 state_hub_workstream_id: "5aaec153-30f4-4978-bca8-af6e0e87712a"
 ---
 
@@ -20,9 +20,19 @@ Establish the personal control-plane intake pattern for projects and commitments
 
 ```task
 id: TEGWICK-WP-0002-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "85f808b2-d9a6-4638-a8a6-c7a276c09a33"
 ```
 
-Define folder/layout for `agent-tasks/`, decision log, and first prioritized workstream.
+Result 2026-06-24:
+
+- Added `INTAKE.md` — capture-to-commitment pipeline (Stages 0–5).
+- Added `agent-tasks/README.md` — layout, naming, lifecycle.
+- Added `decisions/README.md` — decision log layout and registry rules.
+- Seeded `decisions/DEC-001-activation-levels.md` and `DEC-002-root-control-repo.md`.
+- Updated `DECISIONS.md`, `README.md`, and `OPERATING_MODEL.md` cross-references.
+- Created first prioritized workstream: `workplans/TEGWICK-WP-0003-binky-critical-path.md`.
+- Seeded `agent-tasks/binky-surface-critical-path.md` for WP-0003 execution.
+
+Define folder/layout for `agent-tasks/`, decision log, and first prioritized workstream.

workplans/TEGWICK-WP-0003-binky-critical-path.md

@@ -0,0 +1,80 @@
+---
+id: TEGWICK-WP-0003
+type: workplan
+title: "Binky critical path visibility"
+domain: consumer
+repo: tegwick-control
+status: ready
+owner: codex
+topic_slug: consumer
+created: "2026-06-24"
+updated: "2026-06-24"
+state_hub_workstream_id: "093004ac-5683-4599-bea2-7b0670728bdb"
+---
+
+# Binky critical path visibility
+
+Make the company rescue situation explicit without trying to solve everything at
+once. First prioritized workstream after intake scaffold (TEGWICK-WP-0002).
+
+Aligns with `PROJECT_LANDSCAPE.md` current focus #2 and `WORKPLAN.md` Phase 2.
+
+## Surface legal and tax obligations
+
+```task
+id: TEGWICK-WP-0003-T01
+status: todo
+priority: high
+state_hub_task_id: "cf83e727-029e-4ab4-a23b-e9064aa2b257"
+```
+
+List open legal, accounting, and tax obligations in `areas/binky-company.md`.
+Use placeholders where facts are unknown; mark items needing human input.
+
+## Surface business model options
+
+```task
+id: TEGWICK-WP-0003-T02
+status: todo
+priority: medium
+state_hub_task_id: "ed901e89-2df6-45ce-b802-8d9731627032"
+```
+
+List known business model options and revenue paths in `areas/binky-company.md`.
+Distinguish options from commitments.
+
+## Identify survival risks
+
+```task
+id: TEGWICK-WP-0003-T03
+status: todo
+priority: high
+state_hub_task_id: "95bad704-f1f3-48a3-88ee-6becad22b66d"
+```
+
+List urgent company survival risks (cash, compliance, contracts, liability).
+No legal conclusions — visibility only.
+
+## First advisor reactivation step
+
+```task
+id: TEGWICK-WP-0003-T04
+status: todo
+priority: high
+state_hub_task_id: "73bae17c-383b-406a-8dab-97bebf056846"
+```
+
+Identify the smallest next step to re-engage accountant or tax advisor.
+Record as a single actionable item in `TASKS.md` when ready.
+
+## First revenue offer candidate
+
+```task
+id: TEGWICK-WP-0003-T05
+status: todo
+priority: medium
+state_hub_task_id: "a70f6ae8-22f3-461e-9527-f1fcbbcfdbe7"
+```
+
+Identify one revenue-oriented offer candidate worth exploring.
+Keep as option until explicitly promoted to commitment.