You start from the business problem
Objectives and requirements first, screens later. The objective is held as the thing everything else answers to, and you are told when an implementation stopped serving it.
See what governs nowHowever you started
The product adapts to how you work. It does not impose a method.
Some people start from the business problem. Some start from the screen. Some inherited a codebase nobody remembers. Some are looking at something their agent wrote and cannot explain. All four are real starting points, and none of them is the wrong one.
- Problem first or solution first
- Inherited code
- Agent-written code
ONE PLATFORM FOUNDATION
PUBLICDiscover
ACCOUNTCommercial control
WORKSPACEGoverned work
OWNEROperate
IdentityEvidenceAI policyAudit
Four ways in
Find the one that describes your week.
These are working styles, not company sizes. The system holds the same records underneath each of them and changes what it asks of you first.
You start from the solution
Screens and stories first, structure later. Records are derived from what you already built rather than demanded before you are allowed to build it.
You inherited a codebase
Nobody remembers why, and the agent is now guessing. The system reconstructs what appears to be governing the code and asks you to confirm or retire each one.
Your agent wrote most of it
It works, and no one can explain it. This is the most common situation in 2026 and the least well served. Start by finding out what is currently steering the agent.
See the governed contextWhichever one you are
The first run answers the same question for all four.
What is currently in force in this repository, and which of it did you not know was still there?