# Release Manifest

Date: 2026-05-22  
Release state: Limited Preview

Production deployment:

- Public domain: `https://ergocommunity.org/`
- Vercel fallback alias: `https://ergocommunity-portal.vercel.app/`
- Vercel project: `ergocommunity-portal`
- Latest deployment/inspect URLs are tracked in the Vercel project history.
- Custom domain status: `ergocommunity.org` and `www.ergocommunity.org` are attached to this Vercel project. GoDaddy nameservers remain active, with Vercel A/CNAME records observed; some resolvers may show the older GoDaddy/DPS endpoint during propagation.

## What Is Ready

- Static community portal prototype.
- Public navigation: Start, Missions, Feed, Trollbox, Networks, Work Board, Projects, Pulse, Programs, Safety.
- Trollbox preview with X/Twitter, Reddit, Telegram and Discord identity handoff into local chat messages.
- Trollbox bridge plan for Telegram, Discord and Web through one moderated Message Relay.
- Network Embassy layer for friendly L1 communities, daily asks, filters and source-reviewed collaboration.
- Daily retention hub on the homepage with small useful actions and local proof records.
- Mission Inbox with active briefs, proof submission preview and local browser records.
- Work Feed for ranked asks, shipped proof, governance notes and safety reminders.
- Operator navigation: Paths, Gov Watch, Creator Kits, Operator Queue, Sage Lab, Metrics, Launch, Roadmap, Intake, Local.
- Local operator cockpit with static review rooms, weekly cadence, local record storage and JSON export.
- 21 contribution tasks with owner role, source, first step, proof requirement and review date.
- 22 project cards with operational status, verification status, risk state and help-needed slots.
- Launch readiness dashboard with computed data hygiene.
- Read-only Sage proof stream via hosted official drop-in.
- Trust and safety center with verified link registry, report flow and safety interstitial.
- First Weekly Pulse limited-preview draft.
- Source audit, QA log and project owner confirmation script.
- Soft launch runbook and GitHub Issue Forms for claim, proof, safety report and project update workflows.
- Static smoke test for IDs, navigation targets, local docs and generated containers.
- Public trust docs: official/community explainer, security, privacy, contributing and code of conduct.
- Deployment metadata: robots, sitemap, web manifest and `llms.txt`.
- Sitemap/robots/canonical metadata target `https://ergocommunity.org/`.

## What Must Stay Marked Preview

- Project owner/contact fields until maintainers confirm.
- Direct wallet, bridge, DeFi, support and private-invite links until safety review.
- Pulse issue #1 until public URLs and a real contributor spotlight are inserted.
- RACI roles until real handles are assigned.
- Local browser records until a real backend, GitHub issue flow or operations database is connected.
- Trollbox preview messages until provider login, realtime storage, moderation and rate limits are connected.
- Paid Sage chat until safety, source and testnet/mainnet gates are closed.

## Go / No-Go

### Share Limited Preview

Allowed if:

- `Limited preview` label remains visible.
- No direct high-risk action link is exposed without safety state.
- Feedback is routed to the portal owner.

### Full Public Launch

Blocked until:

- Five owner roles have real handles.
- High-risk links are reviewed.
- Project cards have owner-confirmed contact/status.
- Pulse #1 has public source URLs and reviewer sign-off.
- Manual responsive/accessibility QA is complete.
- The local preview workflow is replaced by real review destinations or explicitly documented as a soft-launch mode.

## Deployment Checklist

- Host static files under final domain.
- Confirm `ergocommunity.org` and `www.ergocommunity.org` resolve to Vercel from public resolvers.
- Add privacy-friendly analytics only if needed.
- Add CSP allowing Sage only if the proof stream remains active.
- Add `robots.txt` and sitemap for final URL.
- Confirm all Markdown links resolve after deployment.
- Run `node qa-smoke.mjs` from the portal folder after every content edit.
- Archive this manifest with the release date.