Elev8 Matrix · Labyrinth OS
Labyrinth OS
Day-in-the-Life Workflow Guide
What each person actually does in Labyrinth day to day: where they log in, the order they work, and how each feature is used. Then one client followed end-to-end — from the CRM hand-off through execution, approvals and accountability. Ends with the exact permission matrix.
Daily routines are the recommended way to work each role — they reflect each role's purpose (its "operating question") and the shipped features, not a system-enforced sequence.
Start here
Everyone runs the same execution funnel
Labyrinth is the execution engine: a signed client becomes a contract, which holds milestones, which generate requests (the unit of delegated work). Leadership owns work, specialists are assigned it, and Accountability governs the flow.
| Role | Their job in one line | Lands on |
|---|---|---|
| Coordinator | Own execution direction; delegate & unblock. | Execution Command |
| Manager | Ensure the team has resources, docs & readiness. | Resource & Readiness |
| Advisor | Review, approve, improve templates/systems. | Systems & Review |
| Accountability | Govern overdue/blocked/ownerless work; create users & tasks. | Accountability |
| Admin / Executive | Org-wide oversight. | Command Center |
| Specialist | Do the work assigned to them. | My Work |
| Client | See progress, approve, respond. | Client Portal |
Core role
Coordinator — Execution Command
🧭 Coordinator
"What does my team need to move and unblock today?"
Lands on Execution Command; works Contracts, Requests, Boards, Rainfall.
The daily loop
- Open Execution Command — today's actions, blocked cards, urgent commands.
- Triage blockers — clear red-tagged / blocked work first.
- Delegate — assign requests to specialists; set owners and due dates.
- Drive contracts forward — move milestones along; keep the tree healthy.
- Communicate via Rainfall — issue commands / updates on the record.
Contracts — the trunk of the work
How it's used: open a contract to see its Tree of Execution (milestones → requests), move stages, and delegate the work underneath.
Requests — the unit of delegated work
How it's used: assign and re-prioritise requests; overdue ones are what the accountability engine escalates.
Rainfall — communication & commands
Hands off to: Specialists (assigned requests appear in their My Work) and up to Accountability when something stays blocked.
Core role
Manager — Resource & Readiness
🧰 Manager
"Does my team have the resources, docs and readiness to execute?"
Lands on Resource & Readiness; works Documents, Tools, Performance.
The daily loop
- Check readiness — missing docs, unsigned contracts, training/resource gaps.
- Supply what's missing — attach documents/resources to the work that needs them.
- Watch KPIs — team load and readiness signals on Performance.
- Close communication gaps — make sure owners have what they asked for.
Documents — the resource vault
How it's used: ensure every active contract has the documents/resources its team needs, so execution isn't waiting on missing material.
Performance — readiness & KPIs
Core role
Advisor — Systems & Review
🔎 Advisor
"What needs my review, approval, or a system improvement?"
Lands on Systems & Review; works Approvals, Tools (templates), board reviews.
The daily loop
- Clear reviews — board cards / deliverables awaiting expert review.
- Approve — act on milestone approvals that need the Advisor's step.
- Improve systems — refine templates & SOPs; address recurring failure patterns.
Approvals — the Advisor's queue
How it's used: the Advisor is one step in the milestone approval chain — Coordinator → Advisor → Accountability → CEO — all four needed to fully approve.
Tools — templates & the battleplan
Core role
Accountability — the governor
🛡️ Accountability
"What is overdue, blocked, ownerless, or ungoverned?"
Lands on Accountability; owns user creation and official task creation.
The daily loop
- Run the check — refresh accountability events before reviewing.
- Work the exception queue — overdue, blocked, unowned, missing-evidence work, top-down.
- Escalate / reassign — push stuck work up the ladder or to a new owner.
- Govern access & users — create users, assign role + function; keep Rainfall clean.
Authority (by design): only Accountability creates official tasks and users; templates are Advisor + Accountability; overriding ownership needs Accountability + Executive. A 15-minute cron walks the escalation ladder automatically — Accountability steps in at ESCALATED.
Other roles
Admin, Executive & Project Director
👑 Admin / Executive — oversight
"Where are we winning, blocked, or drifting?"
Command Center + the Strategy view.
- Scan the Command Center (priorities, risk, deadlines) and metric tiles.
- Use Strategy to see the chosen strategy's A→Z milestone timeline and which roles/contracts sit at each stage.
- Admin additionally has System Factory + Admin Log; Executive sits atop approvals/override.
📋 Project Director — Team Command
"What does my team need to move today?"
Cross-client execution health and the contract lifecycle at a team level — sits above Coordinators, leans on the Vision timeline and Command surfaces.
Other roles
Specialist & Client
🔧 Specialist — My Work
"What do I need to complete today?"
Lands on My Work — a focused list of assigned items, no command grid.
- Work assigned requests in order; mark progress; flag blockers.
- Specialists are assignees, not owners — they do the work; leadership owns the outcome.
🧑💼 Client — Client Portal
"What can I see, approve, or respond to?"
- Sees milestones & campaign progress, reviews deliverables, gives approvals — scoped to client-safe data only.
- Not a Command Center persona; the team drives execution, the client reviews it.
Putting it together
One client, from hand-off to delivery
1
Hand-off arrives. A deal is won in ElevateCRM → a contract is created in Labyrinth (stage SIGNED, journey ONBOARDING) with starter milestones, requests and a Rainfall message. It surfaces in System Factory.
2
Accountability registers it. The handoff creates owned operational requests; Accountability confirms ownership and governance from the start.
3
Coordinator takes execution. Picks the blueprint, seeds milestones, and delegates requests with owners & due dates.
4
Manager readies the team. Attaches the documents/resources each milestone needs; clears readiness gaps before work starts.
5
Specialists execute. Assigned requests show in their My Work; they progress them and flag blockers.
6
Advisor reviews & approves. Deliverables/milestones move through the chain (Coordinator → Advisor → Accountability → CEO).
7
Accountability keeps it honest. The 15-min cron escalates overdue work; red tags gate progression (WARNING→request, CRITICAL→milestone, BLOCKER→contract). Leadership watches via Command Center & Strategy.
The seam works live: the contract that starts this story is the one ElevateCRM created on Closed-Won (verified 2026-06-01) — see the ElevateCRM Workflow Guide for the front half.
Reference
Exact permissions by role
The complete grant table from the live permission model — 38 permissions across 9 role columns (MEMBER mirrors SPECIALIST, folded in). ADMIN holds all 38. Legend: ✓ granted · · not granted.
| Permission | ADM | EXEC | PD | ACC | MGR | CRD | ADV | SPC | CLI |
|---|---|---|---|---|---|---|---|---|---|
| contracts.create | ✓ | ✓ | · | · | · | · | · | · | · |
| contracts.edit | ✓ | ✓ | ✓ | · | · | · | · | · | · |
| contracts.transition | ✓ | ✓ | · | ✓ | · | · | · | · | · |
| milestones.create | ✓ | · | ✓ | · | · | ✓ | · | · | · |
| milestones.edit | ✓ | · | ✓ | · | · | ✓ | · | · | · |
| milestones.transition | ✓ | ✓ | ✓ | ✓ | · | ✓ | · | · | · |
| milestones.approve | ✓ | ✓ | ✓ | ✓ | · | ✓ | ✓ | · | · |
| requests.create | ✓ | · | ✓ | ✓ | ✓ | ✓ | · | ✓ | · |
| requests.edit | ✓ | · | ✓ | ✓ | ✓ | ✓ | · | ✓ | · |
| requests.assign | ✓ | · | ✓ | ✓ | ✓ | ✓ | · | · | · |
| red_tags.create | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | · | · |
| red_tags.resolve | ✓ | ✓ | ✓ | ✓ | · | · | · | · | · |
| decisions.create | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | · | · |
| decisions.edit | ✓ | ✓ | ✓ | ✓ | · | · | ✓ | · | · |
| workflows.deploy | ✓ | ✓ | ✓ | · | · | · | · | · | · |
| workflows.edit_templates | ✓ | · | · | · | · | · | · | · | · |
| playbooks.view | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | · | · |
| playbooks.manage | ✓ | ✓ | · | · | · | · | · | · | · |
| team.manage | ✓ | · | · | ✓ | · | · | · | · | · |
| team.view_all | ✓ | ✓ | ✓ | ✓ | ✓ | · | · | · | · |
| admin.system_config | ✓ | · | · | · | · | · | · | · | · |
| admin.view_logs | ✓ | ✓ | · | ✓ | · | · | · | · | · |
| command.view | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | · |
| command.override | ✓ | ✓ | · | ✓ | · | · | · | · | · |
| command.factory | ✓ | ✓ | ✓ | ✓ | · | · | · | · | · |
| command.admin_log | ✓ | ✓ | · | ✓ | · | · | · | · | · |
| communications.send | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | · |
| communications.view_all | ✓ | ✓ | ✓ | ✓ | ✓ | · | · | · | · |
| client.communicate | ✓ | ✓ | ✓ | · | · | · | · | · | · |
| portal.view | ✓ | · | ✓ | · | · | · | · | · | ✓ |
| portal.manage | ✓ | · | ✓ | · | · | · | · | · | · |
| payroll.view | ✓ | ✓ | · | ✓ | · | · | · | · | · |
| integrations.manage_external | ✓ | · | · | · | · | · | · | · | · |
| boards.create | ✓ | ✓ | ✓ | ✓ | · | · | · | · | · |
| boards.edit | ✓ | ✓ | ✓ | ✓ | · | · | · | · | · |
| boards.view_all | ✓ | ✓ | ✓ | ✓ | ✓ | · | · | · | · |
| boards.review | ✓ | ✓ | ✓ | ✓ | ✓ | · | ✓ | · | · |
| boards.upload | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | · |
ADM Admin · EXEC Executive · PD Project Director · ACC Accountability · MGR Manager · CRD Coordinator · ADV Advisor · SPC Specialist · CLI Client. MEMBER mirrors SPECIALIST. Source: labyrinth-os/src/lib/permissions.ts.