# Status

A thin index of where member-console development stands. Detail lives in the linked files — this page stays short on purpose.

## Where we are

Pre-production. A working Go/HTMX app with OIDC auth, FedWiki site management (create / delete / archive / restore with entitlement-gated quotas and downgrade read-only parking), a core domains registry (verify-once DNS claims, generic placements, entitlement-gated custom domains served through FedWiki), a Discourse forum integration (org-held entitlement, per-person delivery via group membership, live SSO + commerce loop proven), an operator MPA admin panel (curated landing overview, catalog, plan ladders, auto-provisioning, per-org enrollment, unified integrations section with runtime-managed settings), first-class plan management (ladders + the `Transition` supersession primitive + transition audit), Stripe billing (Checkout upgrade, cancel downgrade, subscription/invoice/payment sync), and Temporal workflows for site/group sync, domain verification, and Stripe fulfillment. Integrations live in registered trees behind an explicit contract; the database spans a single `core` domain schema plus a `domains` stream and the `stripe`, `fedwiki`, and `discourse` provider integration schemas with per-stream migration ledgers.

**Milestones 1 to 9 complete; Public launch is the active milestone.** Milestones and issues live on the [forge tracker](https://git.coopcloud.tech/wiki-cafe/member-console/milestones); the completed ones are recorded in [archive/milestones-completed.md](archive/milestones-completed.md).

## Current focus

**Public launch**, the milestone that makes the console presentable to a stranger: what it still needs is on the [forge](https://git.coopcloud.tech/wiki-cafe/member-console/milestones). The next milestones, in order, are Audit log and observability, Operator API, and Usage metering.

## Key files

| File | Purpose |
|------|---------|
| the [forge tracker](https://git.coopcloud.tech/wiki-cafe/member-console/issues) | **The home for issues and milestones** |
| [design-feedback.md](design-feedback.md) | Asks of the upstream design repository |
| [strategy.md](strategy.md) | Design-alignment philosophy, the four-roadmaps lens, migration strategy, repo structure |
| [fedwiki-service.md](fedwiki-service.md) | FedWiki Service tier → implementation mapping |
| [archive/](archive/) | Resolved issues and completed-milestone detail |
| `explorations/` | Local lab notebooks, one directory per decision; ignored by git and harvested into `docs/` or the change's `design.md` when the decision lands |
| [MAINTAINING.md](MAINTAINING.md) | Conventions for keeping status/ healthy | and **the rule for where every kind of file lives** |
| `log/` | Per-session development logs |
| `../design/` | Normative data model and design documents (read-only, synced from membcons-db) |
| `../docs/` | Conventions and as-built model cards; the durable home for anything a reader needs without the history |

## Keeping it organized

`status/` tracks where things stand. It is not where decisions, conventions,
or research live once they are settled: conventions go to `docs/`, normative
model rules to `design/` via upstream, changes to `openspec/`, and the
records of an investigation to `explorations/<topic>-<yyyy-mm>/`, a local
notebook git ignores that no tracked file cites. Decide a
file's home by what it is before writing it; the table in
[MAINTAINING.md](MAINTAINING.md#where-things-live) is the rule.