Reference

Look things up here. Each page covers one surface of the app at full depth: every button, every field, every drag handle, every keyboard shortcut.

If you're learning a workflow, use Guides instead. Reference is the index, not the tutorial.

What's in here

• Interactions: every drag handle, resize boundary, right-click menu, double-click, hover behavior, and gesture in the app. Start here if you're hunting for "how do I make X bigger?" or "what does right-clicking Y do?"
• Keyboard shortcuts: the full table. Includes context (when each shortcut fires vs. is suppressed), modifier conflicts, and the Escape stack hierarchy.
• Popups & modals: every popup in the app, what opens it, what's inside.
• Settings: every tab in the Settings popup, every field. One page per tab.
• Agent roles: the 16 built-in roles, what each one defaults to, when to use which.
• File formats: .cerevisor, .cerevisor-world, .opaal. What's inside each file, how they're loaded, when each is used.
• Glossary: every domain term defined once. If you see a word you don't recognize in another doc, it's defined here.

How to read these pages

Reference pages are dense by design. They use these conventions:

• Bold field names on their own line, with the field's purpose immediately after.
• Tables for any catalog (shortcuts, popups, fields) so you can scan.
• Constraints (min/max bounds, when something is disabled, which modes a feature is available in) are always noted explicitly.
• File:line references point into the codebase for anyone who wants to confirm a behavior themselves. End users can ignore these.