Priority order
Proof surface → Scope → Concrete outcome.
This keeps discovery short and execution targeted.
The route is accepted only after the failing surface is identified. This prevents broad rewrites and makes next steps immediate.
Route map
Pick one failing lane and share the exact signal. We route by proof path and only validate what is actually broken.
Outcome-first intakeOnly validated fields
Production-safe defaultsClear next-step plan
Priority order
This keeps discovery short and execution targeted.
The route is accepted only after the failing surface is identified. This prevents broad rewrites and makes next steps immediate.
01
One focused issue only to avoid broad estimates.
02
We map request against public, CRM, and operator continuity surfaces.
03
We send one precise execution path with acceptance criteria.
Quick route
Use when the issue is directly tied to AI Workspace surface behavior.
Open AI Workspace
Quick route
Use for broader context before scoped repair planning.
Open AI Campus
Direct routes
Choose one path, keep it actionable, then we route the intake.
Before submit
One failing route + impact + expected result is enough to start.
Reference links