Project status

Where the platform stands — what's real and shipped, what's deliberately absent, and what's in flight. This page is a snapshot; the repository is the authority.

The platform today

Core architecture — consolidated. One Next.js + Payload + PostgreSQL application; the member interface as App Router routes (src/member/ mounted under (site)/(member)); independent mcp-content service; the retired Vite/Express stack and the interim wouter SPA both removed.

Authority model — consolidated into authority_records. The legacy assignments/appointments dual store, its supersession machinery, and the accounts.team_roles mirror are gone; ~1,900 records backfilled with provenance. One derivation engine, one write service, one lock contract.

Governance — decision pipeline (draft → consultation → decision → vote → outcome) with flags, vetoes, event trail and Council electorate; elections via credential ballots; selections with committee evaluation.

Content — the draft → review → publish pipeline is live for members and agents alike; opportunities and resources carry review queues.

Domains — membership lifecycle (verify, appeals, renewals, handovers, COI, safeguarding, privacy), partnerships, recognition, working-group workspaces, negotiations (tracks, versions, extraction review, contribution projects), GYS and COY programmes, intelligence query adapters.

Delivery — outbox-based email + web push with per-category opt-out; VAPID provisioning scripted.

Operations — Vercel deployment with per-PR Neon preview branches; CI covers lint, build, both Node versions, the full migration chain, payload-types drift, and an MCP handshake smoke test.

Deliberately absent

• An admin UI — by design, not omission.
• Member data in the repository — structure only; provisioning is out-of-band.
• Cryptographically verifiable elections — the credential ballot preserves secrecy within the system but trusts the server; the docs say so rather than implying more.

Known debt

• Lint warnings — zero errors, several hundred warnings (mostly no-explicit-any in older code and specs). Paydown is welcome; it's tracked rather than urgent.
• Semantic retrieval — the Intelligence shadow retrieval path stays opt-in until the governed benchmark passes human review.

In flight

Watch open PRs for what's moving. Recent landed work: the authority-store consolidation, the member interface's absorption into the App Router, the dead-code sweep, review tooling (.coderabbit.yaml), the MCP CI smoke job, and the agent-infrastructure pass (shared .agents/skills, the project-scoped memory bank, sync:mcp, and the autofix-token CI fix).