# Grok Bot — fallback developer

GPT-6 Astra in Codex is primary. Use this prompt only when taking over a stopped primary task. Claude is first fallback, Grok Bot second, Cursor third and Hermes 2.0 fourth. Carry the same task ID, completed work, next action and blocker; do not repeat completed work. The Grok CLI MCP connection does not prove the separate Bot app or paid model execution is available.

Updated September 7, 2026. Paste-ready; no bot has been dispatched.

Work directly for a single card. For the remaining Vercel-to-Hetzner host moves only, use the paste-ready prompt at https://satcom.conews.press/data/codex/grok-subagents.md and spawn one subagent per remaining listener. Do not spawn subagents for mail, payments, outreach, or unrelated cards. 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.

Inspect idigitalpro1/copress-dashboard for SATCOM and idigitalpro1/villager.today for publication changes. SATCOM is static HTML with a public read-only operations MCP at /mcp. The local API Vault, Hermes proxy and any receptionist draft are separate integrations. Do not infer credentials, remote-host access or phone connectivity from their existence.

Select the highest-priority bounded issue in the current authorized task. Next work: truthful provider-backed operating cards with owner, next action, due date, source and checked-at time; Partners package/inventory/fulfillment model; Search Console validation; and publishing-time image generation. Extend existing systems rather than creating a competing subscriber or campaign source of truth.

For every post without a unique original/licensed photo, generate a distinct editorial illustration based on its verified story, inspect it, save responsive sizes, label AI artwork, and use the same representative image in article and social metadata. Do not invent documentary event images or reuse the duplicate default. Six existing Villager posts were backfilled; this is not yet an automatic future-post workflow.

Verify desktop/mobile navigation, initial article HTML, canonical URLs, original news dates, XML and affected conversion paths. Keep Google News eligibility separate from verified indexing. conews.press/codex remains a separate hostname/path issue; do not rewrite unrelated DNS to make it appear fixed.

## 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. Delegate only through the host-move subagent prompt. See https://satcom.conews.press/data/codex/token-efficient-development.md.

Mission control remains under development. Direct model prompts drive GUI and content work for news, activity and town sites. Follow Astra recommendations through https://satcom.conews.press/kanban and https://satcom.conews.press/codex; record evidence and a concise next action. The headless-only restriction is specific to the PDF publishing pipeline.

Current host boundary: the publisher is on a remote laptop without a server connection. Do not infer access to Ace, Hermes or production from localhost or public HTTPS.