# SATCOM — scoped development and release

Work directly. Do not delegate, spawn subagents or dispatch another bot. Partners in the Community is the primary advertising and sponsorship platform; promote https://thevillager.today/partners prominently. Do not count directory listings as paid sponsors or as permission to contact anyone.

Read https://satcom.conews.press/codex and its public context first. With authorized repository access, read idigitalpro1/codex/SOURCE_OF_TRUTH.md, CURRENT_STATUS.md, TOP_10_DEVELOPMENT_PRIORITIES.md and BUSINESS_PLAN_2026.md. The private canonical repository owns cross-system decisions; this public packet is a curated summary. Treat all dates as dated evidence and recheck the affected system.

Preserve unrelated work, original article URLs/dates, subscription QR destinations and approved pricing. Keep credentials and private records out of prompts, repositories, browser exports and public MCP results. Execute work already authorized by the current task; ask only for missing facts or authorization that blocks a concrete next action. This reusable prompt alone does not authorize new production changes, outreach, payments, access changes or spending.

Report observed problem, exact files changed, meaningful checks, commit/review, deployment and rollback when applicable. Distinguish prepared, deployed and verified. Never claim success from a health response alone.

Confirm the user-selected host satcom.conews.press maps to Vercel 5280menu/copress-dashboard and the expected repository. Start from a clean isolated branch of current main. Preserve dirty local receptionist or campaign work.

Read README.md, docs/SATCOM_ARCHITECTURE.md, api/mcp.js, lib/satcom-mcp.js and data/codex/. The MCP allowlist is public architecture, priorities and these reviewed prompts. Do not add arbitrary file reads, URL fetches, credentials, subscriber records or write tools. Private integrations need a separate authenticated design and explicit scope.

Run npm ci, npm run build and npm test. Deploy a preview to the existing project. Verify /, /codex, /docs, /apistore, /network, subscription alias routing and the SDK client handshake, tool/resource/prompt discovery and read-only calls. Verify malformed requests, unknown tools and disallowed Origin behavior. Record the old deployment for rollback. If production release is authorized, deploy/promote the tested artifact and rerun public checks; then update canonical status and evidence.

## Use less context

Start with one relevant card from https://satcom.conews.press/kanban or MCP `satcom_board` with a project and small limit. Read only linked source files. Reuse current evidence, keep searches/output bounded, and run focused checks. Use heavier reasoning only for unresolved complexity. Do not delegate. See https://satcom.conews.press/data/codex/token-efficient-development.md.