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).
31 lines
1021 B
Markdown
31 lines
1021 B
Markdown
# tegwick-control
|
|
|
|
Personal control repository for organizing life, commitments, projects, decisions, and agent-assisted progress.
|
|
|
|
This repository anchors the user's personal information space and provides the operating model for gradually establishing the wider forge organization landscape without creating decision fatigue or burnout.
|
|
|
|
## Initial Use
|
|
|
|
Start here:
|
|
|
|
1. Read `INTENT.md`.
|
|
2. Review `PROJECT_LANDSCAPE.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
|
|
|
|
A topic may exist, matter, and have a place without demanding action today.
|