Files
tegwick-control/decisions
tegwick d4080de393 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).
2026-06-24 15:25:54 +02:00
..

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

decisions/
├── README.md                    this file
├── DEC-NNN-<slug>.md            individual decision records
└── archive/                     superseded records (optional)

Naming

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

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.