Scopes
Admin → Scopes creates the units everything else is shaped by. A scope is part organisational unit, part boundary on what the agent reasons over, and part access control. The concept is explained in context scopes; this is the walkthrough.
Creating one
Section titled “Creating one”Only a label is required. Add a description, a colour, and up to three owners — the people accountable for the domain.
Assigning content
Section titled “Assigning content”A scope is populated by assigning entities, metrics, and business rules to it. This is the actual governance work:
- Entities give the agent its tables. Assigning fewer keeps context tighter and cheaper.
- Metrics are the definitions it reasons over — and the paths to answers.
- Business rules are the constraints it is expected to honour. See grounding in practice.
Start with the metrics and the rules, then add the entities those metrics need. A scope with twenty tables and no metrics is a schema dump.
Featured metrics
Section titled “Featured metrics”Featured metrics are what the scope’s board leads with. This is curation, not approval: a scope can feature an uncertified metric while you are still deciding whether to trust it. See scope boards.
Business rules
Section titled “Business rules”A rule is an instruction plus a certification state. Certified rules are part of the context the agent is expected to apply. An uncertified rule is a note that is not yet part of the contract.
Granting access
Section titled “Granting access”Creating a scope does not give anyone access to it. Grant it per user under Admin → Users, and set a primary scope for each — someone with grants but no primary lands on an empty Home.
Deleting one
Section titled “Deleting one”A scope holding entities or metrics cannot be deleted. Reassign the content first. This is deliberate: deleting a scope should not silently orphan the catalogue work attached to it.