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
Layer Model
Flow
Current Focus
- Stabilize
tegwick-control.
- Stabilize Binky's legal, tax, and business situation.
- Establish Helix as the approved production path.
- Plan Coulomb migration away from Bubble through Helix.
- 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 |