Rig brain
How the rig platform works — agents, dispatch, events, memory, conventions. Invariant across every project that uses the rig.
Tablez Docs
Project brain for the Tablez product portfolio. Scaffold ready; populate when Tablez engineering onboards to the shared rig.
Scaffold state
Section titled “Scaffold state”This project brain is ready for Tablez content but not yet populated. The infrastructure is in place:
- Brain compiles from
facts/*.yaml→/BRAIN.md - Live status blocks + spawned-stories components (when user stories are added)
- mermaid-check CI, auto-deploy on merge, hourly refresh
What’s left is Tablez-side onboarding: list the product repos in facts/repos.yaml, install the dev-e + review-e GitHub Apps on the tablez-dev org, start labeling issues agent-ready.
Two-brain model
Section titled “Two-brain model”This project brain
What the Tablez portfolio is — product repos, tech stack, deploy targets, release gates, portfolio-specific conventions.
An agent assigned to a Tablez repo will fetch both brains at session start — once the rig knows about Tablez repos (via the character-prompt lookup in dashecorp/rig-gitops/apps/{dev-e,review-e}/rig-agent-helmrelease.yaml).
Sibling: Dashecorp
Section titled “Sibling: Dashecorp”The same pattern runs for Dashecorp’s iOS app portfolio at dashecorp-docs.pages.dev — look there for a fully populated example of what this brain will become.