Perpetum CGOS Admin Guides¶
Operating manuals for the Perpetum team administering the CGOS Portal. Each guide documents how an admin performs a task on the live system: who can do it, where it lives, the exact steps, and how it appears to the family.
Use the search box (top of the page) to jump to any term, or pick a guide below.
Map of the guides¶
graph LR
A([Perpetum Admin])
A --> Build
subgraph Build["1. Build a family"]
direction TB
H["House and Estate:<br/>Annex, Room Cards, Keys, Seats"]
P["Permissions and roles"]
end
A --> MoveIn["2. Move-In and Onboarding"]
A --> Operate
subgraph Operate["3. Operate the system"]
direction TB
B["Bricks and Trust Indicators"]
C["Care Protocol"]
end
A --> Content
subgraph Content["Content the family reads"]
direction TB
Ar["Family Intelligence Archive"]
L["Library and Glossary"]
end
A --> Nav["Getting around:<br/>Dashboard and Living Structure"]
Getting around¶
- Dashboard and Living Structure — the 14 Dashboard modules, per-role visibility, and the Living Structure pieces admins author.
- Move-In and Onboarding — the three move-in primitives: architecture approval, Terms of Use, and the two universal review dates.
House and Estate¶
- Annex — populating the Annex (structure, room content, and the family-facing Restricted Access list).
- Room Cards — authoring room-card content and how the four card variants render.
- Room Keys — creating keys, granting and revoking holdings, and how keys gate access.
- Seats and Seat Chart — the three seat types, assigning holders, Successor seats, and the Legal Seat Risk dashboard.
Operating the system¶
- Bricks and Trust Indicators — quarterly Bricks (request, status, outcome, strikes) and authoring Trust Pulse readings.
- Care Protocol — the three-state capacity model, Care Review triage, and the rule that Care never changes keys.
Content¶
- Family Intelligence Archive — adding PDFs to the family's governance library.
- Library and Glossary — curating Library resources and authoring Glossary terms.
These guides are sourced from the live CGOS Portal code and the product requirements. When a feature changes, the matching guide is updated in the same repository, so the documentation tracks the product.