<aside> 🧭
FLOW WORK SYSTEMS GLOBAL NAVIGATION
OPERATE 🎛 CEO Dashboard ☀ Daily Action 🗓 Weekly Review ⚡ Quick Create
DELIVER 📦 Client Handoff
</aside>
<aside> ⚡
CANONICAL QUICK CREATE
Create one record in the correct master database. Use relations for routing, responsibility, decisions, dependencies, and handoffs rather than maintaining a parallel intake list.
</aside>
<aside> ✓
After submission, verify authoritative relations, owner, lifecycle status, dates, evidence, dependency source, approval state, and next handoff. Business Area, Project View Filter, and Completed are intentionally excluded from the canonical forms.
</aside>
<aside> <img src="1" alt="1" width="40px" />
FOUNDATION
Business → Person → Goal → KPI → Project
</aside>
Create the records that later relation questions depend on.
<aside> <img src="2" alt="2" width="40px" />
OPERATE
Task → Decision → Meeting → Review
</aside>
Capture execution, governance, conversations, and periodic review.
<aside> <img src="3" alt="3" width="40px" />
DELIVER
Content → Launch → Vendor
</aside>
Capture approval-dependent assets, release work, and external commitments.
<aside> 🧭
CANONICAL INTAKE ORDER
Create or identify the Business, then the People who own, approve, receive, or block work. Define the Strategic Goal and KPI evidence before creating a Project when the outcome requires coordinated steps. Create dependent operating and delivery records against those relations, then open each submitted record and verify integrity before relying on a filtered dashboard.
</aside>
<aside> ⚠️
Distribution control: before public sale or client delivery, recreate and test every form inside the final duplicated workspace. Form structure is installed here, but recipient-workspace submission behavior remains a separate validation requirement.
</aside>
<aside> <img src="4" alt="4" width="40px" />
GOVERN & IMPROVE
Process → SOP → Knowledge → AI Workflow
</aside>
Create governed operating specifications, approved guidance, improvement work, and controlled AI-assisted procedures.
Quick Create — Govern & Improve
<aside> ↗
USE ONLY WHEN JUSTIFIED
Governance records should reduce operating risk, clarify repeated work, preserve approved knowledge, or control AI use. Do not create documentation merely to fill a database.
</aside>