Purpose: Maintain an index of active and past engagements.
Track delivery history, friction patterns, and economic signal without turning the system into a market persona. This ledger can remain mostly dormant until real usage begins.
| Client ID | Client | Project | Mode | Next Deliverable |
|---|---|---|---|---|
| none yet | — | — | — | activate once real client work starts |
Potential engagements under discussion.
- Keep this section empty until real leads exist, or use it as a scratchpad outside the constitutional docs.
Archive of completed work for operational reference.
- Populate only from actual engagements.
- Preloading fictional examples weakens legibility.
Patterns observed across engagements:
- scope creep clients
- unstable token launches
- repeated restricted content attempts
These signals help refine future client selection and boundary setting.
- Activate these fields only once paid/public usage is real enough to measure.
- Until then, absence is more honest than placeholder metrics.