Files
tegwick-control/PROJECT_LANDSCAPE.md

3.4 KiB

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

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

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

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