Same `/work/` UI an engineer already knows. The only thing different per client = the templates in the shelf and the variables that feed them. Engineers never see "schemas". Adina configures everything ahead of time.
/workspace/ page was the wrong build — a generic schema-explorer that shows the plumbing. This wireframe set captures what should ship instead: the existing /work/ shell, with templates and the data behind them swapped per client. Adina has a separate admin layer for setting up clients (never visible to engineers). And both engineer + admin views pull from a shared Template Library that Adina owns and grows over time.
Same tile grid as today's /work/. Tiles populated from THIS client's report types, not our hardcoded "Project Brief / Weekly Status". Logo + colour from the client.
Paste / voice / photo, the AI knows the client's templates + their fields, asks which template, fills the gaps. Engineer reviews and saves.
Open scene →Adina's home when she's running multiple demos / paid deployments. Each client is a row: brand, templates loaded, status, last opened.
Open scene →Inside one client. Three origin types side by side: scanned-from-theirs · pulled-from-library · custom-built. Drag to reorder. Click to edit fields or rebrand.
Open scene →Adina's master library — the moat. Browse by discipline. Each template = AS-aligned spec + house-style examples + AI-drafting prompts.
Open scene →┌──────────────────────────────────────────────────────────────────────┐
│ Template LIBRARY (Adina owns it, lives in our repo + DB) │
│ Geotech factual · Drainage design · Bridge inspection · Site diary │
│ TIA · GIR · IFC drawing register · Lessons learned · etc. │
│ Each template = AS-aligned spec + AI prompts + example boilerplate │
└──────────────────────────────────────────────────────────────────────┘
↓ pulls from
┌──────────────────────────────────────────────────────────────────────┐
│ CLIENT WORKSPACE (one per client, lives in their tenant) │
│ - Picks which library templates apply to this firm │
│ - Adds any of their scanned templates (their .docx) │
│ - Adds any custom-built ones from engagement │
│ - Branded with their logo + colours │
└──────────────────────────────────────────────────────────────────────┘
↓ engineer signs in
┌──────────────────────────────────────────────────────────────────────┐
│ /work/ (the polished app the engineer already knows) │
│ Dashboard · Project Info · Schedule · Risks · Issues · RFIs · │
│ Budget · People · Variations · Meetings · Period Reports · │
│ Capture · TEMPLATES SHELF (← the only thing that varies per client) │
└──────────────────────────────────────────────────────────────────────┘
/workspace/, keep /scanner/ (it's how Adina adds templates), retrofit /work/'s Templates shelf and Capture to read from a per-client config table. Two real engineering pieces, not the 5 sprints I was doing.