Wiki Mission Control: ongoing maintenance + source-of-truth + translation workflow refresh

[clawderdan]

Objective

Make the Aavegotchi Wiki the official Source of Truth (human-readable + AI-scrape friendly), and keep it continuously updated as facts change based on official/important sources.

Primary sources to monitor (canonical)

• Aavegotchi Blog: https://blog.aavegotchi.com
• Aavegotchi X: https://twitter.com/aavegotchi
• coderdan X: https://twitter.com/coderdannn
• Discord announcements channel: <#1468185291935187004>

If there are other “official” sources we should treat as canonical (Snapshot, GitHub releases, docs site, etc.), list them in comments and I’ll add them here.

Monitoring cadence (automation)

• Daily source scan + maintenance report: 09:15 UTC
• Weekly stale-page audit: Mondays 10:30 UTC
• Additional internal checks: heartbeat tasks run twice daily (morning + evening UTC) to propose updates quickly.

Scope of work

1) Content maintenance

• Keep key pages accurate as contracts, features, tokenomics, governance, and product details change.
• Add citations/links to official sources and timestamp Last verified where relevant.

2) Information architecture for humans + AI

• Standardize page templates where appropriate:
  • TL;DR
  • Canonical definitions
  • Key facts (bullets)
  • References (official links)
  • Last verified (date + source)
  • Change log (optional)
• Prefer stable URLs/slugs; avoid duplicated/conflicting pages.

3) Translations

• Keep localized pages updated as EN changes.
• Replace/refresh the outdated Crowdin workflow with a more modern, low-friction approach (proposal required).

Deliverables

• Mission control questionnaire + agreed operating procedure.
• Recurring monitoring cadence (cron + heartbeat checks).
• Backlog of high-impact page updates (issues/PRs).

Open questions (please answer in comments)

• Priority pages + languages
• Definition of official vs important sources
• How to handle uncertainty/rumors
• Review/merge process (who approves PRs)

Initial suggestion

Start with a small, consistent Canonical Facts section on major pages, plus a Last verified box linking to sources.

[clawderdan]

Workflow note: when you answer mission-control questions in Discord, I will immediately update this issue so it remains the canonical spec/source of truth for the work.

[clawderdan]

Update (from Discord): Trial PR created to update GHST page per announcements feed. PR: #340

[clawderdan]

Per Discord request, opened a second test PR while authenticated as clawderdan to verify Vercel deploy attribution. PR: #341

[clawderdan]

Update (from Discord): New rule — UI/UX specialist agent must review production + PR preview and sign off before merge; enforce human-readable formatting (e.g., embedded links vs raw URLs).

[clawderdan]

Decision (from Discord): Enable June to autonomously open UI/UX improvement issues, capped to 3/week, limited to P0/P1, with dedupe against existing issues.

[clawderdan]

Decision (from Discord): For routine wiki maintenance, Moss should open PRs autonomously (don’t ask first). Find the relevant wiki location and just make the PR. Still ask/flag before high-risk changes (dependency/framework upgrades, large refactors, uncertain facts).

[clawderdan]

Decision (from Discord): For dated/older official posts (blog/announcements), wiki updates must be framed as historical events that already happened (past tense + date), not as current guidance. Updated cron job prompts accordingly.