HeyRocky
ROCKY GUIDE

Search the wiki

Find related setup, tools, memory, workflow, and security guides without losing the page.

Source-of-Truth Inventory for Rocky Projects

Before Rocky can operate reliably, it needs to know where truth lives. A source-of-truth inventory prevents guessing, stale context, and accidental changes to the wrong system.

What to list

Create a short inventory for each serious project:

  • Repository: local path, default branch, deployment command, test command
  • Public site: canonical URL, staging URL, important routes
  • Private dashboard: login owner, roles, and what Rocky may inspect
  • Docs: internal policies, templates, FAQs, brand rules, SOPs
  • Data: spreadsheets, CMS collections, CRM records, exports
  • Communication: Discord, Slack, Telegram, email, or ticketing channels
  • Approvals: who can approve publishing, spending, deletion, or customer contact

Example inventory

Project: HeyRocky portal
Public URL: https://heyrocky.ai
Repo: /path/to/portal
Primary data: data/*.json
Deploy check: curl -I https://heyrocky.ai/wiki
Approval: owner approval before public social posting

Rules for Rocky

Rocky should inspect the source of truth before making claims about the current state. Past conversation can provide context, but it should not replace a live file, page, dashboard, or API when that source is available.

Maintenance

Review the inventory after major changes: new domain, new repo, new gateway platform, new provider, or new automation.

Related pages