# Decision: Stage-1 feature cut (productive transfer)

| Field | Value |
|-------|--------|
| Id | CSOC-DEC-2026-001 |
| Date | 2026-08-12 |
| Status | **accepted** (founder direction; refine fields as product details firm up) |
| Owner | bernd |
| Workplan | CSOC-WP-0001-T03 |
| Model | `docs/capability/model-v0.yaml` |
| Narrative | `docs/capability/stage-1-cutover.md` |

## Context

coulomb.social rebuild runs on `app.coulomb.social` in parallel with Bubble on
apex. Full Bubble parity is not required before transfer. We need an explicit
**must** set so implementation and migration do not stall on marketplace-class
scope, and so reductions are intentional.

Discussion baseline: capability = utility, feature = implementation; practice
capability model on coulomb first; HelixForge extraction later.

## Decision

1. **Partial rebuild is the strategy for stage 1.** Transfer users and retire
   Bubble as the **productive** system when stage-1 capabilities work. Bubble
   may remain as **implementation reference only** (not productive use).

2. **Stage-1 must capabilities:**
   - **User onboarding** (`cap.member-onboarding`)
   - **Spaces with markdown content and CRUD**, including **Visual, Title,
     Abstract** on space/page as product fields (`cap.space-content`)
   - **Transfer of pages to other spaces** (`cap.page-transfer`)
   - **Generate copy of page** (`cap.page-copy`)

3. **Later use cases** (social, marketplace, monetization, full chrome parity,
   etc.) extend the rebuild **after** stage 1; they do not block productive
   transfer.

4. **Capability/feature vocabulary and map** live in `docs/capability/` and
   guide backlog and toggles. Feature toggles attach to features, not to
   capability ids.

## Consequences

- Implementation backlog prioritizes space/page CRUD metadata + copy/move over
  marketplace and social graph.
- CSOC-WP-0001 migration/export targets stage-1 content and members first.
- Public registration may complete via NetKingdom residual; transfer cohort may
  use provisioned accounts if registration is late (open question in stage-1 doc).
- ADR-0002 remains: page **bodies** markdown in Forgejo; Title/Abstract/Visual
  may live in app DB and/or frontmatter — detail in implementation WPs.

## Non-goals (stage 1)

- Rebuild-as-is of all Bubble workflows  
- Pixel-perfect Research UI  
- In-app real-time collab editor (unless later promoted)  
- HelixForge capability-management platform (extract later)

## Open questions

See `docs/capability/stage-1-cutover.md` § Open product questions (Visual
storage, Abstract field naming, body editor UX, delete vs archive, transfer
cohort auth).