Seeded personal organization control repo

AGENT_RULES.md

@@ -0,0 +1,57 @@
+# Agent Rules
+
+## Purpose
+
+This document defines how AI coding and writing agents may assist within `tegwick-control`.
+
+## General Principle
+
+Agents may help clarify, structure, draft, refactor, and prepare work. They must not silently turn options into commitments.
+
+## Allowed Agent Activities
+
+Agents may:
+
+- draft documents;
+- improve structure and wording;
+- create task breakdowns;
+- propose repository structures;
+- classify items by activation level;
+- summarize open decisions;
+- propose next actions;
+- generate templates;
+- prepare implementation prompts for other repositories.
+
+## Requires Human Approval
+
+Agents must request approval before:
+
+- marking a topic as critical;
+- deleting significant content;
+- changing project activation levels;
+- converting options into commitments;
+- changing legal, tax, financial, or company-related conclusions;
+- publishing external-facing claims;
+- creating production deployment instructions;
+- touching secrets, credentials, payment systems, or legal documents.
+
+## Forbidden
+
+Agents must not:
+
+- create artificial urgency;
+- overload the task list;
+- treat all ideas as work;
+- optimize for output volume over personal sustainability;
+- make legal, tax, or financial decisions;
+- act on behalf of the company externally without explicit instruction.
+
+## Preferred Output Style
+
+Agent outputs should be:
+
+- concise;
+- structured;
+- explicit about assumptions;
+- clear about next actions;
+- careful to separate facts, options, and recommendations.

DECISIONS.md

@@ -0,0 +1,37 @@
+# Decisions
+
+## Open Decisions
+
+### DEC-001 — Confirm initial activation levels
+
+Should the initial activation levels in `PROJECT_LANDSCAPE.md` remain as drafted?
+
+Current proposal:
+
+- binky: A3 Critical
+- tegwick: A2 Active
+- helix: A2 Active
+- coulomb: A1/A2 Controlled
+- sloppers: A1 Incubating
+- whywhynot: A1 Incubating
+- plenitude: A1 Incubating
+
+Status: open
+
+---
+
+### DEC-002 — Confirm whether `tegwick-control` is the root control repo
+
+Should `tegwick-control` be treated as the root control repo for the whole landscape?
+
+Status: open
+
+---
+
+## Resolved Decisions
+
+None yet.
+
+## Decision Record Format
+
+Use `templates/decision-record.md` for structured decision records.

INTENT.md

@@ -0,0 +1,45 @@
+# INTENT
+
+## Purpose
+
+`tegwick-control` exists to serve as the personal control repository for organizing private life, major projects, commitments, decisions, and agent-assisted progress.
+
+It anchors the broader project landscape by providing a stable place to collect, clarify, prioritize, and sequence work without turning every idea into an immediate obligation.
+
+## Primary Utility
+
+The repository helps the user:
+
+- reduce decision fatigue;
+- maintain a clear overview of active and inactive topics;
+- distinguish commitments from options;
+- coordinate personal, corporate, technical, community, prototype, and commercial initiatives;
+- prepare work so agentic coding systems can assist safely and productively.
+
+## Strategic Role
+
+`tegwick-control` is the root personal operating layer for the wider forge-based landscape.
+
+It does not implement the major projects directly. Instead, it defines their relationship, activation state, next actions, and governance boundaries.
+
+## Operating Principle
+
+A topic may exist, matter, and have a place without demanding action today.
+
+## Initial Scope
+
+The initial scope is to establish a lightweight but reliable structure for:
+
+- personal organization;
+- project landscape mapping;
+- Binky company stabilization;
+- Helix-based product development;
+- Coulomb migration planning;
+- prototype and community incubation;
+- commercial activation through Plenitude.
+
+## Out of Scope
+
+This repository is not the implementation home for product code, production infrastructure, accounting systems, payment systems, or public-facing community operations.
+
+Those concerns belong in their respective organizations and repositories once sufficiently clarified.

OPERATING_MODEL.md

@@ -0,0 +1,65 @@
+# Operating Model
+
+## Purpose
+
+This operating model defines how `tegwick-control` is used to reduce decision fatigue, keep important topics visible, and enable safe agent-assisted progress.
+
+## Core Rules
+
+### 1. Everything has a place
+
+Unplaced topics create mental load. Every relevant topic should eventually have a home.
+
+### 2. Not everything is active
+
+A topic may be important without being active.
+
+### 3. Commitments are different from options
+
+Options can be collected freely. Commitments require ownership, next actions, and consequences.
+
+### 4. Agentic work must be bounded
+
+Agents should receive clearly scoped tasks with explicit allowed changes, expected outputs, and approval boundaries.
+
+### 5. The system must protect energy
+
+The purpose is continuous progress, not constant pressure.
+
+## Work Classes
+
+| Class | Meaning |
+|---|---|
+| Commitment | Something that must be done |
+| Option | Something that may be valuable |
+| Exploration | Something unclear that needs investigation |
+| Decision | Something that requires choosing |
+| Waiting | Something blocked by another person/system |
+| Routine | Something recurring |
+| Someday | Valuable but inactive |
+
+## Review Surfaces
+
+| Surface | Purpose |
+|---|---|
+| `TASKS.md` | Current actionable work |
+| `DECISIONS.md` | Open and resolved decisions |
+| `PROJECT_LANDSCAPE.md` | Major topic map |
+| `areas/` | Per-topic notes and control cards |
+| `WORKPLAN.md` | Sequenced setup plan |
+| `inbox/` | Temporary capture area |
+
+## Commitment Rule
+
+No item becomes a commitment merely because it is interesting, important, or emotionally charged.
+
+A commitment should have:
+
+- an owner;
+- a clear next action;
+- a reason for acting now;
+- a defined review surface.
+
+## Agentic Coding Rule
+
+No implementation work should be delegated to an agent until the target repo, intended outcome, boundaries, and approval requirements are clear.

PROJECT_LANDSCAPE.md

@@ -0,0 +1,113 @@
+# Project Landscape
+
+## Purpose
+
+This document organizes the user's personal, corporate, technical, community, prototype, and commercial initiatives into a coherent forge-based operating model designed to enable continuous agent-assisted progress without decision fatigue or burnout.
+
+## Organizations
+
+| Organization | Domain | Role | Activation |
+|---|---|---|---|
+| tegwick | personal | Personal information space and operating system | A2 Active |
+| binky | company | Corporate information space and company rescue | A3 Critical |
+| helix | forge | Information products factory / intent-to-product engine | A2 Active |
+| coulomb | ideation | Ideas and knowledge exploration webapp | A1/A2 Controlled |
+| sloppers | community | Directors of Abundance community | A1 Incubating |
+| whywhynot | prototypes | Weird/useful prototypes and market-signal space | A1 Incubating |
+| plenitude | store | Commercial point of sale and offer hub | A1 Incubating |
+
+## Activation Levels
+
+| Level | Name | Meaning |
+|---|---|---|
+| A0 | Dormant | Exists, but no active work expected |
+| A1 | Incubating | May collect notes and options, but no delivery pressure |
+| A2 | Active | Has current tasks and may receive structured work |
+| A3 | Critical | Needs regular attention until stabilized |
+
+## Dependency Model
+
+```text
+tegwick stabilizes the person
+binky stabilizes the company
+helix creates the production capability
+coulomb becomes the flagship exploratory product
+whywhynot validates ideas and collects market signal
+sloppers creates community gravity
+plenitude converts value into revenue
+```
+
+## Layer Model
+
+```text
+Survival / Legitimacy Layer
+└── binky
+    ├── tax/accounting/legal cleanup
+    ├── business model activation
+    ├── income generation
+    └── company operating structure
+
+Personal Stability Layer
+└── tegwick
+    ├── private life organization
+    ├── stress reduction
+    ├── commitments
+    └── decision hygiene
+
+Production Engine Layer
+└── helix
+    ├── intent-to-product workflow
+    ├── agentic coding infrastructure
+    ├── reusable repo patterns
+    └── automation backbone
+
+Product / Exploration Layer
+├── coulomb
+│   └── reimplemented idea/knowledge exploration product
+└── whywhynot
+    └── prototypes, experiments, beta feedback, market signal
+
+Community / Market Layer
+├── sloppers
+│   └── community, discourse, shared abundance narrative
+└── plenitude
+    └── commercial offers, payment, store, services
+```
+
+## Flow
+
+```text
+tegwick
+   │
+   ▼
+binky
+   │
+   ▼
+helix
+ ┌─┼─────────┐
+ ▼ ▼         ▼
+coulomb  whywhynot  plenitude
+   │        │         ▲
+   ▼        ▼         │
+sloppers ────────────┘
+```
+
+## Current Focus
+
+1. Stabilize `tegwick-control`.
+2. Stabilize Binky's legal, tax, and business situation.
+3. Establish Helix as the approved production path.
+4. Plan Coulomb migration away from Bubble through Helix.
+5. Keep Sloppers, WhyWhyNot, and Plenitude incubating until activation is safe.
+
+## Naming Roles
+
+| Name | Functional Role |
+|---|---|
+| Superslop / Sloppers | Community energy |
+| Plenitude | Commercial trust |
+| Binky | Legal and business vehicle |
+| Helix | Production engine |
+| Coulomb | Exploration product |
+| WhyWhyNot | Prototype and signal capture |
+| Tegwick | Personal operating base |

README.md

@@ -0,0 +1,19 @@
+# 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. 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`.
+
+## Core Principle
+
+A topic may exist, matter, and have a place without demanding action today.

REVIEW_RHYTHM.md

@@ -0,0 +1,47 @@
+# Review Rhythm
+
+## Purpose
+
+The review rhythm keeps the system useful without turning it into bureaucracy.
+
+## Daily Capture
+
+Goal: remove pressure from memory.
+
+Suggested practice:
+
+- Capture loose items in `inbox/`.
+- Do not classify everything immediately.
+- Do not convert ideas into commitments during capture.
+
+## Weekly Review
+
+Goal: restore orientation.
+
+Suggested checks:
+
+- What is active?
+- What is critical?
+- What is waiting?
+- What became noisy but not important?
+- What should be moved from inbox into an area card?
+- What should be explicitly parked as incubating?
+
+Use `templates/weekly-review.md`.
+
+## Monthly Landscape Review
+
+Goal: prevent drift.
+
+Suggested checks:
+
+- Are activation levels still correct?
+- Is Binky still A3, or has it stabilized?
+- Is Helix moving the production capability forward?
+- Is Coulomb migration clearer?
+- Are Sloppers, WhyWhyNot, and Plenitude still safely incubating?
+- Are any repos/projects creating stress without clear value?
+
+## Burnout Guardrail
+
+If the system feels heavy, reduce the number of active commitments before adding structure.

SCOPE.md

@@ -0,0 +1,47 @@
+# SCOPE
+
+## Current Reality
+
+`tegwick-control` is the first control repository for establishing a personal and project-wide operating model.
+
+It currently serves as a place to:
+
+- map the major organizations and initiatives;
+- define activation levels;
+- hold initial workplans;
+- track open tasks and decisions;
+- define how agents may assist;
+- prevent important but inactive ideas from becoming stressful obligations.
+
+## In Scope
+
+- Personal organization model.
+- Project landscape overview.
+- Area cards for major topics.
+- Task and decision tracking.
+- Agent task preparation.
+- Review rhythm definition.
+- Lightweight governance for activation levels and commitments.
+
+## Out of Scope
+
+- Product implementation code.
+- Production infrastructure.
+- Legal/tax/accounting execution.
+- Payment infrastructure.
+- Public community operations.
+- Customer-facing store operations.
+- Secrets, credentials, or live system administration.
+
+## Known Adjacent Areas
+
+- `binky`: company operations, tax/accounting, business model, commercial survival.
+- `helix`: intent-to-product engine and information products factory.
+- `coulomb`: idea and knowledge exploration webapp.
+- `sloppers`: community hub and Directors of Abundance community.
+- `whywhynot`: prototypes and market-signal capture.
+- `plenitude`: commercial store and offer hub.
+
+## Scope Guardrail
+
+This repository coordinates and clarifies. It does not absorb all work.

TASKS.md

@@ -0,0 +1,68 @@
+# Tasks
+
+## Active
+
+### TEG-001 — Create `tegwick-control` repository
+
+Create the initial repository in the `tegwick` Gitea organization.
+
+Status: open  
+Class: commitment  
+Area: tegwick  
+Activation: A2  
+
+### TEG-002 — Add initial control documents
+
+Add the core documents:
+
+- `INTENT.md`
+- `SCOPE.md`
+- `PROJECT_LANDSCAPE.md`
+- `OPERATING_MODEL.md`
+- `WORKPLAN.md`
+- `TASKS.md`
+- `DECISIONS.md`
+- `AGENT_RULES.md`
+
+Status: open  
+Class: commitment  
+Area: tegwick  
+Activation: A2  
+
+### TEG-003 — Create area cards
+
+Create initial area cards for:
+
+- private life
+- binky company
+- helix forge
+- coulomb
+- sloppers
+- whywhynot
+- plenitude
+
+Status: open  
+Class: commitment  
+Area: tegwick  
+Activation: A2  
+
+### TEG-004 — Review Binky critical path
+
+Create an initial list of legal, tax, accounting, and business activation issues in `areas/binky-company.md`.
+
+Status: open  
+Class: commitment  
+Area: binky  
+Activation: A3  
+
+## Waiting
+
+None yet.
+
+## Options
+
+- Add weekly review automation.
+- Add task tagging standard.
+- Add issue templates.
+- Add agent prompt templates.
+- Add a lightweight CLI helper for repo review.

WORKPLAN.md

@@ -0,0 +1,147 @@
+# Workplan
+
+## Goal
+
+Establish `tegwick-control` as the first working control repository for the broader personal, corporate, technical, and commercial project landscape.
+
+## Phase 0 — Create the Repository
+
+### Objective
+
+Create the initial repo structure and seed the core documents.
+
+### Tasks
+
+- Create `tegwick-control` in the `tegwick` Gitea organization.
+- Add `INTENT.md`.
+- Add `SCOPE.md`.
+- Add `PROJECT_LANDSCAPE.md`.
+- Add `OPERATING_MODEL.md`.
+- Add `WORKPLAN.md`.
+- Add `TASKS.md`.
+- Add `DECISIONS.md`.
+- Add `AGENT_RULES.md`.
+- Create `areas/`, `inbox/`, `agent-tasks/`, and `templates/`.
+
+### Done When
+
+The repository exists and provides a first usable overview of the project landscape.
+
+---
+
+## Phase 1 — Establish Area Cards
+
+### Objective
+
+Create one area card for each major organization/topic.
+
+### Tasks
+
+- Create `areas/private-life.md`.
+- Create `areas/binky-company.md`.
+- Create `areas/helix-forge.md`.
+- Create `areas/coulomb.md`.
+- Create `areas/sloppers.md`.
+- Create `areas/whywhynot.md`.
+- Create `areas/plenitude.md`.
+
+### Done When
+
+Each major topic has a clear purpose, activation level, current state, and next surface.
+
+---
+
+## Phase 2 — Stabilize Binky Visibility
+
+### Objective
+
+Make the company rescue situation explicit without trying to solve everything at once.
+
+### Tasks
+
+- List open legal/accounting/tax obligations.
+- List known business model options.
+- List urgent company survival risks.
+- Identify the first accountant/tax-advisor reactivation step.
+- Identify first revenue-oriented offer candidate.
+
+### Done When
+
+Binky has a clear critical path list and no longer exists only as diffuse pressure.
+
+---
+
+## Phase 3 — Define Helix as Production Path
+
+### Objective
+
+Clarify that serious product implementation should move through Helix rather than ad-hoc tooling.
+
+### Tasks
+
+- Document Helix's role as intent-to-product engine.
+- Define how product ideas become implementation candidates.
+- Define how agentic coding tasks should be prepared.
+- Identify required repo templates and task formats.
+
+### Done When
+
+There is a clear path from idea to structured implementation task.
+
+---
+
+## Phase 4 — Plan Coulomb Migration
+
+### Objective
+
+Turn Coulomb from a Bubble.io timesink into a controlled migration target.
+
+### Tasks
+
+- Capture current Bubble.io functionality.
+- Identify must-keep features.
+- Identify obsolete/friction-heavy features.
+- Define first Helix-based replacement slice.
+- Define migration risks.
+
+### Done When
+
+Coulomb has a migration plan and no longer depends on open-ended Bubble evolution.
+
+---
+
+## Phase 5 — Incubate Market and Community Layers
+
+### Objective
+
+Keep WhyWhyNot, Sloppers, and Plenitude alive without letting them become premature obligations.
+
+### Tasks
+
+- Define WhyWhyNot prototype intake model.
+- Define Sloppers/Zulip community hypothesis.
+- Define Plenitude commercial offer categories.
+- Mark all three as A1 Incubating unless explicitly activated.
+
+### Done When
+
+The market/community/store layer is visible but not stressful.
+
+---
+
+## Phase 6 — Establish Review Rhythm
+
+### Objective
+
+Create a light review cycle that supports progress without creating bureaucracy.
+
+### Tasks
+
+- Define daily capture habit.
+- Define weekly review template.
+- Define monthly landscape review.
+- Define agent-assisted review prompts.
+
+### Done When
+
+There is a simple rhythm for keeping the system current.

agent-tasks/seed-tegwick-control.md

@@ -0,0 +1,64 @@
+# Agent Task: Seed tegwick-control
+
+## Goal
+
+Create the initial `tegwick-control` repository structure and populate the first control documents from the provided draft material.
+
+## Context
+
+`tegwick-control` is the first control repository for organizing the broader personal, corporate, technical, community, prototype, and commercial project landscape.
+
+It should reduce decision fatigue and support safe agent-assisted progress.
+
+## Allowed Changes
+
+The agent may:
+
+- create Markdown files;
+- create folders;
+- add the initial documents;
+- improve formatting;
+- fix obvious typos;
+- keep the structure lightweight.
+
+## Forbidden Changes
+
+The agent must not:
+
+- create implementation repositories;
+- expand the task list beyond the initial setup unless asked;
+- convert incubating topics into active commitments;
+- introduce production deployment instructions;
+- create legal, tax, financial, or payment conclusions;
+- add secrets, credentials, or private account data.
+
+## Expected Output
+
+A repository containing:
+
+- `README.md`
+- `INTENT.md`
+- `SCOPE.md`
+- `PROJECT_LANDSCAPE.md`
+- `OPERATING_MODEL.md`
+- `WORKPLAN.md`
+- `TASKS.md`
+- `DECISIONS.md`
+- `AGENT_RULES.md`
+- `REVIEW_RHYTHM.md`
+- `areas/`
+- `templates/`
+- `inbox/`
+- `agent-tasks/`
+
+## Acceptance Criteria
+
+The repository should be understandable without additional context and useful as a first control surface.
+
+## Human Approval Required For
+
+- changing activation levels;
+- changing the purpose of an organization;
+- creating new commitments;
+- creating additional repositories;
+- publishing or external communication.

areas/binky-company.md

@@ -0,0 +1,55 @@
+# Area: binky company
+
+## Purpose
+
+Corporate information space and rescue/control surface for the GmbH founded in 2019.
+
+## Strategic Role
+
+This area contributes to the broader landscape by holding a distinct role in the personal, corporate, technical, community, prototype, or commercial operating model.
+
+## Activation Level
+
+A3 Critical
+
+## Current State
+
+Initial area card created during `tegwick-control` seeding. Needs review and refinement.
+
+## Commitments
+
+- Clarify current state.
+- Identify true commitments separately from options.
+- Define the next useful surface.
+
+## Options
+
+- Collect ideas without activating them.
+- Prepare future repo structures if needed.
+- Create agent tasks only after boundaries are clear.
+
+## Open Decisions
+
+- Is the activation level correct?
+- What is the first next action?
+- Which existing repos, notes, or systems belong here?
+
+## Risks
+
+- Treating this area as urgent merely because it is interesting.
+- Creating too many repos before the control surface is stable.
+- Delegating agent work without clear boundaries.
+
+## Agentic Suitability
+
+Agents may help draft, organize, summarize, classify, and prepare scoped tasks.
+
+Agents must not convert options into commitments without explicit approval.
+
+## Next Surface
+
+Review this area card and replace placeholders with actual current state, commitments, options, and risks.
+
+## Notes
+
+Initial seed content.

areas/coulomb.md

@@ -0,0 +1,55 @@
+# Area: coulomb
+
+## Purpose
+
+Ideas and knowledge exploration webapp; currently on Bubble.io and intended for controlled reimplementation through Helix.
+
+## Strategic Role
+
+This area contributes to the broader landscape by holding a distinct role in the personal, corporate, technical, community, prototype, or commercial operating model.
+
+## Activation Level
+
+A1/A2 Controlled
+
+## Current State
+
+Initial area card created during `tegwick-control` seeding. Needs review and refinement.
+
+## Commitments
+
+- Clarify current state.
+- Identify true commitments separately from options.
+- Define the next useful surface.
+
+## Options
+
+- Collect ideas without activating them.
+- Prepare future repo structures if needed.
+- Create agent tasks only after boundaries are clear.
+
+## Open Decisions
+
+- Is the activation level correct?
+- What is the first next action?
+- Which existing repos, notes, or systems belong here?
+
+## Risks
+
+- Treating this area as urgent merely because it is interesting.
+- Creating too many repos before the control surface is stable.
+- Delegating agent work without clear boundaries.
+
+## Agentic Suitability
+
+Agents may help draft, organize, summarize, classify, and prepare scoped tasks.
+
+Agents must not convert options into commitments without explicit approval.
+
+## Next Surface
+
+Review this area card and replace placeholders with actual current state, commitments, options, and risks.
+
+## Notes
+
+Initial seed content.

areas/helix-forge.md

@@ -0,0 +1,55 @@
+# Area: helix forge
+
+## Purpose
+
+Information products factory and intent-to-product engine for agent-assisted product creation.
+
+## Strategic Role
+
+This area contributes to the broader landscape by holding a distinct role in the personal, corporate, technical, community, prototype, or commercial operating model.
+
+## Activation Level
+
+A2 Active
+
+## Current State
+
+Initial area card created during `tegwick-control` seeding. Needs review and refinement.
+
+## Commitments
+
+- Clarify current state.
+- Identify true commitments separately from options.
+- Define the next useful surface.
+
+## Options
+
+- Collect ideas without activating them.
+- Prepare future repo structures if needed.
+- Create agent tasks only after boundaries are clear.
+
+## Open Decisions
+
+- Is the activation level correct?
+- What is the first next action?
+- Which existing repos, notes, or systems belong here?
+
+## Risks
+
+- Treating this area as urgent merely because it is interesting.
+- Creating too many repos before the control surface is stable.
+- Delegating agent work without clear boundaries.
+
+## Agentic Suitability
+
+Agents may help draft, organize, summarize, classify, and prepare scoped tasks.
+
+Agents must not convert options into commitments without explicit approval.
+
+## Next Surface
+
+Review this area card and replace placeholders with actual current state, commitments, options, and risks.
+
+## Notes
+
+Initial seed content.

areas/plenitude.md

@@ -0,0 +1,55 @@
+# Area: plenitude
+
+## Purpose
+
+Commercial point of sale for offers, support, operations, and information products emerging from Helix, Coulomb, and WhyWhyNot.
+
+## Strategic Role
+
+This area contributes to the broader landscape by holding a distinct role in the personal, corporate, technical, community, prototype, or commercial operating model.
+
+## Activation Level
+
+A1 Incubating
+
+## Current State
+
+Initial area card created during `tegwick-control` seeding. Needs review and refinement.
+
+## Commitments
+
+- Clarify current state.
+- Identify true commitments separately from options.
+- Define the next useful surface.
+
+## Options
+
+- Collect ideas without activating them.
+- Prepare future repo structures if needed.
+- Create agent tasks only after boundaries are clear.
+
+## Open Decisions
+
+- Is the activation level correct?
+- What is the first next action?
+- Which existing repos, notes, or systems belong here?
+
+## Risks
+
+- Treating this area as urgent merely because it is interesting.
+- Creating too many repos before the control surface is stable.
+- Delegating agent work without clear boundaries.
+
+## Agentic Suitability
+
+Agents may help draft, organize, summarize, classify, and prepare scoped tasks.
+
+Agents must not convert options into commitments without explicit approval.
+
+## Next Surface
+
+Review this area card and replace placeholders with actual current state, commitments, options, and risks.
+
+## Notes
+
+Initial seed content.

areas/private-life.md

@@ -0,0 +1,55 @@
+# Area: private life
+
+## Purpose
+
+Personal operating stability, private commitments, family/life admin, routines, and decision hygiene.
+
+## Strategic Role
+
+This area contributes to the broader landscape by holding a distinct role in the personal, corporate, technical, community, prototype, or commercial operating model.
+
+## Activation Level
+
+A2 Active
+
+## Current State
+
+Initial area card created during `tegwick-control` seeding. Needs review and refinement.
+
+## Commitments
+
+- Clarify current state.
+- Identify true commitments separately from options.
+- Define the next useful surface.
+
+## Options
+
+- Collect ideas without activating them.
+- Prepare future repo structures if needed.
+- Create agent tasks only after boundaries are clear.
+
+## Open Decisions
+
+- Is the activation level correct?
+- What is the first next action?
+- Which existing repos, notes, or systems belong here?
+
+## Risks
+
+- Treating this area as urgent merely because it is interesting.
+- Creating too many repos before the control surface is stable.
+- Delegating agent work without clear boundaries.
+
+## Agentic Suitability
+
+Agents may help draft, organize, summarize, classify, and prepare scoped tasks.
+
+Agents must not convert options into commitments without explicit approval.
+
+## Next Surface
+
+Review this area card and replace placeholders with actual current state, commitments, options, and risks.
+
+## Notes
+
+Initial seed content.

areas/sloppers.md

@@ -0,0 +1,55 @@
+# Area: sloppers
+
+## Purpose
+
+Directors of Abundance community hub, likely using Zulip and tight integration with forge repos and Coulomb spaces.
+
+## Strategic Role
+
+This area contributes to the broader landscape by holding a distinct role in the personal, corporate, technical, community, prototype, or commercial operating model.
+
+## Activation Level
+
+A1 Incubating
+
+## Current State
+
+Initial area card created during `tegwick-control` seeding. Needs review and refinement.
+
+## Commitments
+
+- Clarify current state.
+- Identify true commitments separately from options.
+- Define the next useful surface.
+
+## Options
+
+- Collect ideas without activating them.
+- Prepare future repo structures if needed.
+- Create agent tasks only after boundaries are clear.
+
+## Open Decisions
+
+- Is the activation level correct?
+- What is the first next action?
+- Which existing repos, notes, or systems belong here?
+
+## Risks
+
+- Treating this area as urgent merely because it is interesting.
+- Creating too many repos before the control surface is stable.
+- Delegating agent work without clear boundaries.
+
+## Agentic Suitability
+
+Agents may help draft, organize, summarize, classify, and prepare scoped tasks.
+
+Agents must not convert options into commitments without explicit approval.
+
+## Next Surface
+
+Review this area card and replace placeholders with actual current state, commitments, options, and risks.
+
+## Notes
+
+Initial seed content.

areas/whywhynot.md

@@ -0,0 +1,55 @@
+# Area: whywhynot
+
+## Purpose
+
+Prototype and market-signal space for discovering the weird and the useful through early feedback, closed betas, and early investment opportunities.
+
+## Strategic Role
+
+This area contributes to the broader landscape by holding a distinct role in the personal, corporate, technical, community, prototype, or commercial operating model.
+
+## Activation Level
+
+A1 Incubating
+
+## Current State
+
+Initial area card created during `tegwick-control` seeding. Needs review and refinement.
+
+## Commitments
+
+- Clarify current state.
+- Identify true commitments separately from options.
+- Define the next useful surface.
+
+## Options
+
+- Collect ideas without activating them.
+- Prepare future repo structures if needed.
+- Create agent tasks only after boundaries are clear.
+
+## Open Decisions
+
+- Is the activation level correct?
+- What is the first next action?
+- Which existing repos, notes, or systems belong here?
+
+## Risks
+
+- Treating this area as urgent merely because it is interesting.
+- Creating too many repos before the control surface is stable.
+- Delegating agent work without clear boundaries.
+
+## Agentic Suitability
+
+Agents may help draft, organize, summarize, classify, and prepare scoped tasks.
+
+Agents must not convert options into commitments without explicit approval.
+
+## Next Surface
+
+Review this area card and replace placeholders with actual current state, commitments, options, and risks.
+
+## Notes
+
+Initial seed content.

inbox/README.md

@@ -0,0 +1,17 @@
+# Inbox
+
+This folder is for temporary capture.
+
+Use it for:
+
+- rough notes;
+- pasted thoughts;
+- unclassified ideas;
+- urgent fragments;
+- questions for later review.
+
+## Rule
+
+Capture is not commitment.
+
+An item in the inbox does not become a task until it is reviewed and intentionally moved into `TASKS.md`, an area card, or another appropriate place.

templates/agent-task.md

@@ -0,0 +1,33 @@
+# Agent Task: {{title}}
+
+## Goal
+
+What should the agent accomplish?
+
+## Context
+
+Relevant background.
+
+## Inputs
+
+Files, documents, repos, or notes the agent should use.
+
+## Allowed Changes
+
+What the agent may change.
+
+## Forbidden Changes
+
+What the agent must not change.
+
+## Expected Output
+
+What the agent should produce.
+
+## Acceptance Criteria
+
+How to know the task is done.
+
+## Human Approval Required For
+
+Any areas where the agent must stop and ask.

templates/area-card.md

@@ -0,0 +1,45 @@
+# Area: {{name}}
+
+## Purpose
+
+What this area exists for.
+
+## Strategic Role
+
+How this area contributes to the larger landscape.
+
+## Activation Level
+
+A0 Dormant / A1 Incubating / A2 Active / A3 Critical
+
+## Current State
+
+Brief description of the current situation.
+
+## Commitments
+
+Things that actually need to happen.
+
+## Options
+
+Interesting possibilities that are not yet commitments.
+
+## Open Decisions
+
+Decisions that need to be made.
+
+## Risks
+
+Things that could create harm, stress, delay, cost, or confusion.
+
+## Agentic Suitability
+
+What agents may safely help with in this area.
+
+## Next Surface
+
+Where the next useful action should appear.
+
+## Notes
+
+Additional context.

templates/decision-record.md

@@ -0,0 +1,43 @@
+# Decision: {{title}}
+
+## Status
+
+Open / Accepted / Rejected / Superseded
+
+## Date
+
+YYYY-MM-DD
+
+## Context
+
+What situation created the need for this decision?
+
+## Options
+
+### Option 1
+
+Description.
+
+### Option 2
+
+Description.
+
+### Option 3
+
+Description.
+
+## Decision
+
+What was decided?
+
+## Rationale
+
+Why this option was chosen.
+
+## Consequences
+
+What follows from this decision?
+
+## Review
+
+When or under what condition should this decision be reviewed?

templates/project-card.md

@@ -0,0 +1,45 @@
+# Project: {{name}}
+
+## Purpose
+
+What this project exists to achieve.
+
+## Parent Area
+
+Which area or organization owns this project.
+
+## Status
+
+Proposed / Incubating / Active / Paused / Complete / Deprecated
+
+## Activation Level
+
+A0 / A1 / A2 / A3
+
+## Desired Outcome
+
+What success would look like.
+
+## Current State
+
+Where the project stands now.
+
+## Next Action
+
+The smallest useful next action.
+
+## Dependencies
+
+Other projects, people, services, accounts, or decisions needed.
+
+## Risks
+
+Known risks or uncertainty.
+
+## Agentic Suitability
+
+What agents may safely do.
+
+## Notes
+
+Additional context.

templates/weekly-review.md

@@ -0,0 +1,43 @@
+# Weekly Review
+
+## Week
+
+YYYY-WW
+
+## Orientation
+
+What feels most important this week?
+
+## Active Commitments
+
+- [ ] ...
+
+## Critical Issues
+
+- [ ] ...
+
+## Waiting For
+
+- ...
+
+## Inbox Items to Process
+
+- ...
+
+## Decisions Needed
+
+- ...
+
+## Energy Check
+
+What should be reduced, parked, or simplified?
+
+## Agent Tasks to Prepare
+
+- ...
+
+## Next Week Focus
+
+1. ...
+2. ...
+3. ...