cgalo5758
660485d9b8
The exploration directory held 245 tracked files, and one week's notebook had grown to 28M of captures, per-run CSS copies and model logs, so every change ended with an argument about what to prune. It is now a local lab notebook: git ignores it, its tracked files are untracked, and no tracked file cites a path under it, because another clone does not have it. Every live citation is rewritten so the fact stands in the sentence: the docs pages, AGENTS.md, four main specs, one Go comment, issues.md and milestones.md. The operator IA page gains the landed IA revisions it used to point at, and the UX rubric moves to docs/first-contact-rubric.md because the process requires it. Archived changes, status/archive, status/log and design/ keep their old paths as frozen history; the design/ ones are logged as an upstream issue. MAINTAINING.md and the status README describe the notebook and the harvest that replaces pruning.
39 lines
3.7 KiB
Markdown
39 lines
3.7 KiB
Markdown
# 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–9 complete; M10 (Open-Source Launch Readiness) resumed as the launch gate.**
|
||
|
||
## Current focus
|
||
|
||
**M10 — Open-Source / Public Launch Readiness**, resumed 2026-07-23 after M9 closed (9e/9f/9g all landed; Discourse proved the integration contract end-to-end). Done: 10a (front door), 10b (first-run friction), 10c (purchasability), 10d code (custom domains; production adoption remains as ops), 10e (hardening and polish), 10f (presentable operator dashboard), 10g (first-contact UX pass, closed 2026-08-30 with `unify-shell`), 10h (audit remediation), 10i (model cards), 10j (verification-found hardening). Next: **10k** (page anatomy, quality gate, htmx 4; decided 2026-08-30), then 10d ops (Slice 3 cutover), then the Gitea migration, which is M10-blocking. See [milestones.md](milestones.md) for the boards and [issues.md](issues.md) for open bugs and carried debt.
|
||
|
||
## Key files
|
||
|
||
| File | Purpose |
|
||
|------|---------|
|
||
| [milestones.md](milestones.md) | Milestone definitions and status (active + proposed) |
|
||
| [issues.md](issues.md) | **The home for known issues** — backlog, bugs, design feedback |
|
||
| [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.
|