📦 Core · Client — what Diagaxis BUILDS for the client (the local biz's own system)Core · Client = what Diagaxis BUILDS for the client = the local biz's OWN system serving the local biz's OWN customers. Tiles 1-2 mapped the DIAGAXIS journey (biz-owner = Diagaxis's customer); this maps the CLIENT-SIDE MACHINE. The 30-day challenge (journey tile) onboards the OWNER; this tile = what the deployed system does for the OWNER'S CUSTOMERS. Per D104-D107, MACHINE 2's Customer Journey Map = the CJ of the owner's-customers.
1
instances (Marie-Pier · pre-activation)
1/108
combos resolved (6 × 6 × 3)
The resolution pipeline offer × niche × avatar → ONE deployed instance
offer × niche × avatar (generic)→snapshot fork (GHL sub-account)→overlay merge (niche-B + avatar · langue B)→master instantiation (client-master-template)→AXIS provision (the container)→Day 0-30 cycle (the client adopts)
Hard rule: instances are RESOLVED, not authored. 108 theoretical combos (6 offers × 6 niches × 3 avatars) · ~12 overlays authored · 1 instance.
The build engine (6.02) what BUILDS an instance
| System | Role | State |
|---|
| onboarding-system-architecture (steps 0-12) | the resolution pipeline | spec — not GHL-built |
| onboarding-object-schemas | Custom Objects (Client Implementation · Cycle Progression Tracker) | spec |
| onboarding-build-templates | welcome · portal shell · implementation record | spec |
| client-master-template-v0 (DIA-603) | the per-client Contract + Map · client-facing CJ PRIMARY | template ready |
| 7 build skills | funnel-builder · voice-ai · workflow-email · site-builder · lead-magnet · prompt-writer · page-playbooks | spec |
| 5 jobs/ production primitives | client-conversion-page · chiro-patient-page · acquisition · content-delivery · retention-delivery | spec — not exercised end-to-end |
The deployed-instance Customer Journey Map the CLIENT'S CUSTOMERS' journey — what the system runs (≠ the Diagaxis journey)
| Stage (client's customers) | What the deployed system does | Powered by |
|---|
| inquiry | the local biz's customer reaches out (call/DM/form/missed-call) | DFD · RRS |
| captured | system responds <5 min, never misses | RRS speed-to-lead · DFD intake |
| booked | calendar/booking mechanic (the client's own calendar) | RRS · DFD |
| served | the local biz delivers; system confirms/reminds | RRS structured experience |
| impressed | review captured (binary) | Word of Mouth Loop |
| retained | RFM / win-back / loyalty | Continuity System |
| visibility (always-on) | content / GBP / search-trust drawing new inquiries | Flywheel Response |
Offer-component matrix what each offer DEPLOYS into a client sub-account
| Offer | Deployed components | State |
|---|
| Digital Front Desk $297 | scanner/QR · 4-page site · intake form · review-capture wf · chat widget · activation emails | partial (pages pending · Maya KB 🔴) |
| Word of Mouth Loop $497 | 4-page funnel · capture wf · approval-gated reply AI · nurture A/B/C · 3-phase SLA | partial (funnel pending · emails draft) |
| Revenue Root System $997 | speed-to-lead · Ana qual · structured experience · follow-through · Smart Website · GHL snapshot · R1-R6 · Diagaxis-Score | semi-live (legacy 'Intake' naming · screenshot pending) |
| Flywheel Response $997 | daily IG Rhythm 5×/wk · 4 GBP/mo · DM keyword capture · 4 Search-Trust Articles/mo · Month-1 4-Video Authority Network | partial (VibeCode scaffold · DIA-509 blocked) |
| Continuity System $2K | RFM · tiered rewards · win-back · Plai retargeting · points · VIP | PAUSED (Phase 2 gate) |
| Your Digital Front Connect $297 | ≥10-page website · AI chat widget · contact form · lead-capture-to-pipeline · monthly blog · monthly refresh · AskAI | draft (chat-widget collision · packet rebuild) |
AXIS — the client-facing container D63 · the client's daily surface
6 sections (locked)
WelcomePlaybooksSmart DemoWeekly Updates (RSS)Next Steps (CTA)Support (unified chat)
4 support signals (locked)
PredictabilityResponsivenessRecognitionMomentum
Tier flip: free (Diagaxis main: RSS + Maya check-in + Dawson diagnostic) → paid (client sub-account: Pax visible, expanded) · handoff carries bottleneck_constraint · engagement_history · niche_key · offer_purchased · pax_handle
Agents inside the sub-account: Maya = front-desk/onboarding intake · Pax = scoreboard/reporting/anticipation (visible to client, surfaces upgrade signals to Souky) — both INSIDE the client sub-account
Tracker — build-state 🟡 architecturally sound, minimally deployed. Doctrine locked + 41 cards in 6.02 + 12 in 6.01, but 0 live end-to-end resolved instance.
| Layer | System | Blocker |
|---|
| build engine | onboarding pipeline (0-12) + object schemas | not GHL-built |
| build engine | client-master-template Contract + Map | — |
| build engine | 7 build skills + 5 jobs primitives | not exercised end-to-end |
| journey map | client's-customers journey (the Core · Client Customer Journey Map) | embedded in offers, no standalone card |
| components | 6 offers deployed | 2 semi-live / 2 partial / 2 paused-draft |
| AXIS | container (6 sections) | tier-flip automation (DIA-378) |
| instances | Marie-Pier (only instance) | DIA-550 §10 (26-item checklist) |
| population | 108 combos (6×6×3) | ~12 overlays / 1 instance — scale-blocked on first proof |
⚠️ Biggest gap — No live end-to-end instance completion. Marie-Pier (only instance) is pre-activation; DIA-550 §10 blocks Day 0-3. Until ONE client moves Day 0 → Day 30 → renewal, the Core · Client machine's deploy-readiness stays 🟡. Everything else is ready and waiting on this proof.
Build-ops order
- Marie-Pier to Day 30 = the FIRST PROOF — unblock DIA-550 §10 → activate → run Day 0-30 → hit renewal (converts deploy-readiness 🟡→🟢)
- THEN scale: resolve a 2nd instance (different offer/niche) → validate the resolution pipeline repeats
- parallel substrate (gates ALL delivery): DIA-369 Maya/Pax KB + journey-tile S1 (7 P0 signal fields) — same domino as the niche tile
- AXIS tier-flip automation (DIA-378) · per-offer completion (RRS naming · Flywheel DIA-509 · YDFC chat-widget)
🔑 The shared domino (recurs in EVERY tile)The SAME first domino recurs across the whole OS: DIA-369 (Maya/Pax agent rebuild) + journey-tile S1 (7 P0 signal fields) gate BOTH the Diagaxis journey AND the client-delivery machine. One first domino, whole-system unlock.
⏸️ Open Cat A (Souky)
Marie-Pier — activate (unblock DIA-550 §10) as first-proof, OR is it winding down (offboarding 2026-07-25) → pick a different first-proof client?
Instance population — which offer × niche × avatar is the canonical first RESOLVED instance to prove the pipeline?
Maya/Pax per-client KB — rides DIA-369 + journey-tile S1 (same blocker as niches); confirm no separate per-client KB build before agents rebuilt