Why this build exists
Today, Claresia is "skills-as-markdown" — a folder of IP. To stand behind the $60/seat license in a real procurement cycle, Claresia must become a real Agent Operations Platform with: an IT-admin control plane (cc-059), a Hub layer IT can configure (cc-060/cc-062), per-seat role profiles (cc-061), distribution into the customer's chosen LLM (cc-063 Claude / cc-065 Copilot / cc-070 ChatGPT), telemetry observability (cc-064/cc-066), and end-user surfaces (cc-067 Teams / cc-068 Adaptive Cards / cc-069 Browser Extension / cc-071 Slack).
Dainese, our first reference customer, is a Microsoft Copilot M365 + Azure shop. Phase 2 (Route B unlock) is therefore as critical as Phase 1 (Route A) and runs in parallel.
Items
13
cc-059 → cc-071
Build budget
~49 wks
across all phases
Critical-priority
9
of 13 items
In progress
0
parallel agent build
Effort by phase
5-layer platform composition
The 5 layers, materially
L1 — IP Library
56 skills, 83 coworks, agent + workflow templates, role specs (cc-051)
Existing
L2 — Intelligence Hub
Canonical org memory: outputs, decisions, governance events. Option A or B.
cc-050 + cc-060/062
L3 — Distribution Plane
Skill IR → Claude / Copilot / ChatGPT / Gemini. CI publish + per-seat entitlement.
cc-063 / cc-065 / cc-070
L4 — Admin Console
IT admin daily-presence: RBAC, telemetry, billing, audit, connectors.
cc-059 + cc-061 + cc-064
L5 — End-User Surfaces
Teams / Slack / Browser Extension / Adaptive Cards. Ambient, not headless.
cc-067 / cc-068 / cc-069 / cc-071