# ResolveChain — Investor Pitch Deck Build Plan
*IKIGAI board-approved dark-green/gold design system · self-contained animated HTML deck*

---

## 0. Key finding (read first)

The `ikigai-board-deck` skill expects several reference files that **do not exist in this repo**:

- `IKIGAI-DS.md` (repo root) — the design-token/component catalog — **missing**
- `00.Extract/new/` sample decks — **missing**
- `04.Template/charter-data.json` — **missing**

The only shipped asset is:

- `.claude/skills/ikigai-board-deck/assets/deck-boilerplate.html` (55 KB: full CSS framework + routing engine + 11 example slides)

**Therefore the boilerplate IS our source of truth** for the design system, and
`context/smart-logistic-os-app.html` ("Smart Logistic OS") is the target-style reference.

**Palette (confirmed from boilerplate):** dark greens `#082b1d` / `#14503a`, sage greens
`#3f5a4b` `#4a6355` `#87a191` `#9db4a6` `#c3d2c6`, gold accents `#c9a35b` / `#f1e2c2`.

**Two hard rules (from the skill):**
1. **No content drift** — strip every `REPLACE:` marker and all sample copy
   (AVP, SMBC, Iwatani, biomass trading, "Human Transformation Journey"). Every slide must
   carry ResolveChain's real data.
2. **No design drift** — reuse existing components by shape; never rename classes, invent
   colors, or hand-roll new visual patterns. If content doesn't fit, pick another existing
   component or ask.

---

## 1. Phase 0 — Setup & guardrails

1. Copy `assets/deck-boilerplate.html` → **`deck/resolvechain-pitch.html`** (never edit the boilerplate in place).
2. Every slide keeps the same chrome:
   - `.subbar` (back-link + empty `.progress`)
   - `.eyebrow` + `h2.title` (+ optional `.lede`)
   - `.content` block built from existing components
   - empty `.pager`
3. **Never** hand-write `.progress` dot buttons or `.pager` buttons — the boot script generates them.

---

## 2. Phase 1 — Narrative & slide map

Pattern **A** (grouped index → home grid), ~12 slides. Each ResolveChain fact from `business.md`
maps to an existing boilerplate component:

| #  | Slide                     | Component (boilerplate source)                 | ResolveChain content |
|----|---------------------------|------------------------------------------------|----------------------|
| 0  | **Home / Contents**       | index grid (`home`)                            | 3 groups: Problem & Market · Product · Business & Moat |
| 1  | **Positioning**           | `.compare` (s1)                                | Old: per-FTE billing, opaque, SLA disputes → New: pay-per-resolution, on-chain proof |
| 2  | **The Problem**           | `.stat` grid `.c4` (s5)                         | $380B industry · per-FTE model · manual reconciliation · SLA disputes |
| 3  | **Solution — 4 pillars**  | `.cols` / `.card` (s4)                          | AI orchestration · on-chain audit trail · smart-contract pay-per-resolution · portable AI credit score |
| 4  | **Platform / hub map**    | `.stackzone` / `.node` / `.hub` / `.conn` (s2)  | AI agent + blockchain layer + SLA engine converge on the ResolveChain core |
| 5  | **Ticket lifecycle**      | `.vc` value-chain chips (s3)                    | receive → classify → resolve → escalate → hash on-chain → auto-pay / compensate |
| 6  | **Market opportunity**    | `.stat` `.c4` + `.count` (s5)                   | $15.12B AI CX (25.8% CAGR) · $4.89B AI call centers · $80B Gartner savings 2026 · $7-12 → $0.40 cost/call |
| 7  | **Business model**        | `.wf` waterfall (s7)                            | fee / resolved ticket + platform fee / smart-contract tx + enterprise compliance & audit packages |
| 8  | **Competitive moat**      | `.risk-wrap` / `.rq` (s9)                       | network-effect data · on-chain reputation asset · industry-specific SLA engines |
| 9  | **Why now / vs alts**     | `.compare` (s1)                                 | vs AegisRail & TitanGrid: established budget need, lower market risk |
| 10 | **Roadmap**               | `.tl` timeline + `.gate` (s8) *or* `.bars` (s6) | phased rollout with go/no-go gates **(needs input)** |
| 11 | **The Ask / Conclusion**  | closing card (s10)                             | stage, raise amount, use of funds **(needs input)** |

**Boilerplate component reference (what each example slide demonstrates):**
- s1 → `.compare` (old way vs new way)
- s2 → `.stackzone` / `.node` / `.hub` / `.conn` (everything converges on one core)
- s3 → `.vc` value-chain chips (long sequential process)
- s4 → `.cols` / `.card` (layer cards)
- s5 → `.stat` grid `.c4` (+ `.count` animated numbers)
- s6 → `.bars` (phased plan with capped metric)
- s7 → `.wf` waterfall (payment / allocation order)
- s8 → `.tl` timeline with `.gate` badges (roadmap w/ exit criteria)
- s9 → `.risk-wrap` / `.risk-core` / `.rq` (N categories under one control tower)
- s10 → rules / conclusion closing card

---

## 3. Phase 2 — Wiring (bottom `<script>`)

1. `ORDER = ['home','s1','s2',…]` must list every `<section id>` in slide order (home first).
2. `TITLES` must have a short nav label for every id in `ORDER`.
3. Update the home index grid: group headers + `data-nav` entries (must match section ids) → the 3 groups above.
4. Fix doc `<title>` (line ~6) and the title suffix (line ~900) → "— ResolveChain".
5. Everything else in the script is engine code — do not edit.

---

## 4. Phase 3 — Verify before "done"

- Extract the inline `<script>` and run `node --check` for syntax errors.
- Confirm every `ORDER` id has a matching `<section id>` and every `ORDER` id has a `TITLES` entry.
- Serve locally (`python3 -m http.server`) and open it:
  - click every nav entry, test ←/→ arrows and Esc
  - resize below ~860px to confirm mobile fallbacks (rails hide, `.cyclecard` fallback shows, grids collapse to 1 column)
- Grep the finished file for leftover `REPLACE:` markers and sample terms
  (`AVP`, `SMBC`, `Iwatani`, `Ikigai Green Energy`, `Human Transformation Journey`).

---

## 5. Content source — ResolveChain facts (from business.md)

- **Name:** ResolveChain (Resolve = ticket processing, Chain = blockchain). AI-agent call-center platform, pay-per-result on-chain.
- **Domain:** BPO / Customer Service Automation — AI Agent + Blockchain.
- **Problem:** $380B call-center outsourcing bills per FTE — opaque performance, frequent SLA disputes from manual reconciliation and two-sided data manipulation.
- **Solution — 4 pillars:**
  1. AI agent orchestration — end-to-end ticket lifecycle, learns per-client to raise auto-resolution.
  2. On-chain audit trail — every action, response time, CSAT hashed & immutable.
  3. Smart-contract pay-per-resolution — fee per resolved ticket; auto-compensates on SLA breach.
  4. Portable AI credibility — agents build a cross-client "credit score."
- **Market:** AI CX market ~$15.12B in 2026 (CAGR 25.8%); AI call centers ~$4.89B; Gartner: AI cuts contact-center labor cost by $80B in 2026 and replaces 20–30% of human agents; cost/call $7–12 (human) → ~$0.40 (AI voice); $380B outsourcing shifting to "AI agent as a service" with no transparency/measurement/payment standard — the gap ResolveChain fills.
- **Business model:** fee per resolved ticket + platform fee per smart-contract transaction + enterprise compliance/audit packages (finance, insurance, healthcare).
- **Moat:** cross-client operational data (data network effect) · on-chain agent reputation (hard-to-replicate asset) · industry-specific SLA engines (technical barrier).
- **Vs alternatives:** vs AegisRail (agency commerce) & TitanGrid (AI compute) — established budget need (BPO cost-cutting is happening now), lower market risk, easier early paying customers.

---

## 6. Open inputs needed before an investor-ready build

`business.md` is strong on problem/market/model but a pitch deck needs items it doesn't contain.
To avoid content drift, these must be supplied (or approved as drafted placeholders):

1. **Fundraise stage & ask** — pre-seed / seed / Series A? amount + use of funds? (Slide 11)
2. **Roadmap** — real phases/milestones/dates, or draft a generic 3-phase go-to-market for review? (Slide 10)
3. **Traction / team** — any pilots, LOIs, revenue, founder credentials? (add slides or omit)
4. **Audience** — external VCs vs. internal board (tone of positioning vs. AegisRail/TitanGrid).

**Decision to confirm:** proceed now with clearly-marked placeholders for #1–3, or answer these first
for a one-pass investor-ready deck.