cgalo5758
fa614d0fb7
Fourth section of #269's change. Every act that can change who holds a ladder now writes one reconcile_subscription outbox entry per live subscription of the organization (active, trialing, past_due or unpaid, in id order), in the act's own transaction, so each subscription's collection pause is decided again after the act commits. The entry is an insert and takes no lock. The acts: issuing a grant (entitlements.IssueGrant, which the issue handler now calls in place of ConferGrant), managing, revoking and expiring one, the legacy grant a default change confers, and removing a tier from a ladder. ConferGrantTx itself requests nothing, because the conferral and provisioning paths that call it run before the subscription exists or reconcile it themselves. In the reconcile, the ended branch and the surplus end request the organization's other subscriptions, excepting the one being reconciled. The screens utility waits until the application database holds no pending or failed outbox row before its first capture, because the demo seed's revocation and expiry now leave two entries the running app's relay completes on its own schedule. docs/stripe.md rewrites the grant over a paid plan: the console pauses the subscription's collection while the grant holds, and the costs that pause accepts are listed. docs/models/plan-ladders-transitions.md, docs/plan-management.md, docs/models/payments-billing.md and docs/database-locks.md say the same. Tests: TestActsRequestSubscriptionReconciles (six acts, two live subscriptions and a canceled one, ids and creation order differing), TestConferGrantTxRequestsNothing, TestReconcileEndedRequestsTheOtherSubscriptions, TestSurplusEndRequestsTheOtherSubscriptions, TestIssueGrantHandlerRequestsAReconcile, and the demo seed's entries. Seven trace goldens gain the ListLiveSubscriptionsOfPool read. Review: no blocker or major; six minors and six nits applied (a step name for the tier removal's request error, the fixture's id order, doc comments and the docs that still said a grant over a paid plan keeps billing). Breaks: 17 of 17 caught. Ignoring the exception is caught only through the surplus end: in the ended branch the excepted subscription is already canceled, so the live read never lists it. Full suite on reset databases: 4768 pass, 14 skip. make screens: no change beyond the three captures every run since section 2 redraws.
title, audience, summary
| title | audience | summary | |||
|---|---|---|---|---|---|
| Documentation index |
|
Index of member-console documentation, grouped by audience, plus the front-matter convention every doc follows. |
Documentation
Every document in this directory carries YAML front matter declaring its audience, so readers can find what's for them and contributors know who they're writing for.
Front-matter convention
Start each doc with a front-matter block:
---
title: "Human-readable title"
audience: [admin, developer] # one or more of: developer, admin, user (primary first)
summary: "One sentence describing what the doc covers."
---
The three audiences:
- developer — contributing to or understanding the codebase: architecture, design decisions, dev setup, testing, UX research and conventions, the provider-extension contract.
- admin — hosting and operating an instance: installing, configuring an identity provider, building the image, generating secrets, running the service.
- user — the general public or a member using a running service. (None yet — the tag is reserved for member-facing docs.)
List the primary audience first; a doc may name more than one.
For administrators — hosting & operating
- Production Deployment — the sequenced path from a fresh host to a running instance; start here.
- Environment Reference — every configuration key with its default and
MC_*override. - Settings and Configuration — why software uses two words for what a program is told, and how this console applies the rule.
- Hosting member-console — build the image and generate secrets.
- Deployment Architecture — how the console fits alongside a public site and an identity provider.
- Identity Provider Setup — configure an OIDC IdP for login.
- Temporal Authorization Setup — emit the
permissionsclaim Temporal's JWT authorizer expects. - Plan Management — operator guide to plan ladders and grants.
- Stripe Integration — flags, secrets, webhooks, and purchasability.
For developers — contributing & internals
- Database Management — goose migrations and sqlc.
- Database Locks — every advisory and serializing row lock, how each key is built, and the order each path takes them in.
- Design System — UI conventions.
- Domain Model Cards — the model catalog: one card per domain model with invariants, dimensions, and traps.
- FedWiki Integration — provisioning via the FarmManager API.
- Go Conventions — where a rule and an act live, transactions and locks, services that answer after the listener opens, output order, error handling, and dead code.
- HTMX Setup — HTMX under a strict CSP.
- Identifiers — IDs, names, and keys: which entities carry a key, its grammar and scope, and how seeds and lookups use it.
- Operator Information Architecture — the operator panel's IA contract.
- Operator UX Conventions — form and action conventions.
- First-Contact UX Walk Process — the repeatable method for walking the console as a stranger.
- First-Contact UX Rubric — the instrument that method scores with: the A–G question bank, the walker protocol, and the screen coverage checklist.
- Agent Runner — how an agent from another model family reviews or ideates on the code inside a disposable copy: what contains it, how a task is shaped, and what a finding must carry before it counts.
- Operator UI Accessibility Baseline — what operator-UI changes are diffed against.
- Building an Integration — adding a new integration.
- Testing — the test taxonomy and how to run each kind, plus the gates:
make lint(page-anatomy rules and the Go static checks) andmake screens(contact sheets at two widths).
For users
No member-facing documentation yet.
One page per rule
A rule is written on the one page that owns it. Another page that needs the rule links to that page instead of restating it, because two copies of a rule are edited separately and drift apart.
Where things are not
Research, drafts, audits, walkthrough evidence, and other records of how a
decision was reached are not documentation; they stay in a local notebook
that git ignores, so a clone never carries them. When a decision lands,
whatever a reader still needs is written into this directory, which holds
the result without the history. The rule for every kind of file is in
status/MAINTAINING.md.