coulomb/coulomb-social
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
coulomb-social/SCOPE.md
tegwick bc78cd27fc Adopt stage-1 capability cut and product capability model 
Persist capability/feature vocabulary, v0 model, and founder stage-1 must set
(onboarding, spaces/pages with Title/Abstract/Visual, page copy and transfer).
Mark CSOC-WP-0001-T03 done; add CSOC-WP-0006 for implementation.
2026-08-12 13:09:09 +02:00

5 KiB
Raw Permalink Blame History

SCOPE

This file helps you quickly understand what this repository is about, when it is relevant, and when it is not. It is intentionally lightweight and may be incomplete.

One-liner

Reimplementation of the coulomb.social co-creation platform as a standalone Railiance / NetKingdom / HelixForge application, exiting the stalled bubble.io stack.

Core Idea

coulomb.social connects people around shared projects and complementary capabilities. Development on bubble.io has stalled. This repo owns the full product rebuild — UI, content, data model, and migration — so the platform can evolve with the rest of the Coulomb agentic fleet under the business-app service contract.

In Scope

  • Product intent, scope, workplans, and ADRs for the coulomb.social rebuild
  • Inventory of the existing bubble.io app (pages, workflows, data types, integrations, content)
  • Data export, relational schema mapping, and migration rehearsal
  • Feature-cut decisions (rebuild-as-is vs reduced v1) and acceptance criteria
  • Application implementation: UI parity, domain model, app-local accounts, APIs
  • Packaging for the business delivery lane (commit-SHA images, railiance-apps release values)
  • Tenant-keyed data model from the first migration; member account export/delete
  • Ops/runbook stubs required by the business-app service contract (§§3–6)
  • State Hub workplans, progress events, and classification for this repo

Out of Scope

  • Remaining on bubble.io as the primary development platform
  • Owning Railiance cluster, platform, or app-chart infrastructure code (railiance-*)
  • Owning NetKingdom identity platform implementation (Keycloak/OpenBao) — only the app-local auth boundary and future OIDC switch point live here
  • Owning HelixForge standards or capability registry implementation
  • Core Hub embedding or treating coulomb.social as a hub extension
  • Fleet self-improvement loops (owner: coulomb-loop)
  • Serving paying external multi-tenant SaaS before the service-contract preconditions are met

Relevant When

  • Planning or implementing the bubble.io exit and product rebuild
  • Mapping coulomb.social features, content, or data into code-owned artifacts
  • Packaging or deploying the coulomb.social app via the business delivery lane
  • Checking tenancy, identity, backup, or cost-attribution obligations for this app

Not Relevant When

  • You need cluster or mesh infrastructure changes → use the relevant railiance-* repo
  • You need platform SSO/secret custody work → use net-kingdom / OpenBao workplans
  • You need fleet kaizen loop operation → use coulomb-loop
  • You need a reference business-app implementation pattern → start with vergabe-teilnahme
  • You only need the historical seed note → the-custodian/docs/coulomb-social-rebuild-seed.md (pointer; work originates here)

Current State

  • Status: parallel hosts — identity + app shell + Forgejo spaces live on app.*
  • https://app.coulomb.social: Railiance rebuild (OIDC, app home, spaces markdown)
  • https://coulomb.social: Bubble.io full product until cutover decision
  • Finished product path: CSOC-WP-0004 (spaces + Forgejo markdown + runbook)
  • Finished identity path: CSOC-WP-0002, CSOC-WP-0003 (Case A; Case B residual intakes)
  • Content ADR: docs/adr/ADR-0002-space-content-forgejo-markdown.md
  • Operator: docs/deploy.md runbook; residuals docs/intakes/csoc-residuals.md
  • Finished resource evidence: CSOC-WP-0005 → docs/resource-evidence/
  • Bubble exit: CSOC-WP-0001 — inventory done; stage-1 feature cut accepted (partial rebuild); export still needs Bubble editor
  • Capability model: docs/capability/ — stage 1 must = onboarding + spaces/pages (Title/Abstract/Visual) + page copy/transfer
  • Open residuals: public registration (CSOC-IN-0001/0002, NK-WP-0025)

How It Fits

  • Upstream decisions: business-app service contract; DR-1 C / DR-2 B / DR-3 A
  • Delivery lane: vergabe-teilnahme (pattern) → this repo (product) → railiance-apps (release values) → railiance01
  • Platform peers: railiance-*, net-kingdom, helix-forge, ops-hub, fin-hub
  • Coordination: State Hub topic coulomb-social (domain communication); related engagement repo coulomb-loop

Getting Oriented

  • Start with: INTENT.md, GOAL.md, .custodian-brief.md
  • Key paths: workplans/, docs/ (as they appear), application source (once scaffolded)
  • First workplan: workplans/CSOC-WP-0001-bubble-io-exit-assessment.md
  • Contract: the-custodian/canon/standards/business-app-service-contract_v0.1.md

Related Repositories

Repo Relationship
vergabe-teilnahme Reference business-app delivery lane
railiance-apps Helm/release values for deploy
railiance-forge / helix-forge Forge and capability patterns
net-kingdom Future OIDC / platform identity
coulomb-loop Fleet improvement loops (same State Hub topic)
the-custodian / state-hub Coordination, standards, seed history