Linking and nesting
A charter becomes more useful when it stops living alone.
Teams depend on other teams. Roles participate in work beyond their home team. A role may become a subteam. Decisions cross boundaries. Particulars turns those references into relationships the model can use.
Mentions
Type @ in a supported field to mention another team or role.
The mention becomes a navigable relationship rather than dead text. Readers can move to the referenced team, and editors can see where their team is mentioned elsewhere.
When a charter mentions another team, the mentioned team's editors may be notified. They can subscribe to future changes.
Use mentions for meaningful interfaces:
- a team whose input is required
- a team receiving the output
- shared ownership of a measure
- consultation on a decision
- a recurring handoff
- a dependency worth seeing in the network
Nested subteams
Sometimes a role has become enough work for a whole team.
From the role details, choose Convert to subteam. Particulars creates a child charter using the role's focus as a starting point and preserves the parent-child relationship.
The parent keeps the role as the interface. The child gains its own purpose, roles, decisions, and measures.
This allows the model to grow without erasing why the new team exists.
The graph
Mentions, nesting, role links, shared people, agents, and decisions create edges in the model.
Over time, Particulars can show:
- the formal hierarchy
- working dependencies
- one team's neighborhood
- every team touching a capability
- one person's work across several organizations
- authority around a decision
- repeated overlap and structural gaps
The graph is not a decorative org chart. It is a set of useful projections over the same underlying record.