Combines codex-audit.html (external Codex CLI, hostile-VC stress-test) + gemini-audit.html (Claude-fallback cross-coherence) + design-review-audit.html (Claude design pass). One conclusion across all 3: the decks predate V3 doctrine, and V3 doctrine itself has a load-bearing weakness. Both must change in v5. The codex hostile review is the most important read here — surface it before any deck work begins.
write_file + run_shell_command tools. Process killed. Findings labeled GEMINI are Claude-internal fallback using grep verification on actual source files.
V3 doctrine fixed the 8 violations from May 31 Alchemist debrief, but a real VC will still rate V3's moat 4/10 (Q1), Microsoft trap 2/10 (Q2), success metric 3/10 (Q3), why-not-GPT 3/10 (Q4). The 3 current decks don't visualize V3 anywhere. Both must change in v5.
| Dimension | CODEX hostile VC score | GEMINI deck-V3 coherence | DESIGN visual + slop | Synthesis |
|---|---|---|---|---|
| Problem statement | 8/10 (implicit) | 6/10 EN decks miss 退職代行 hook | 8/10 JA strong, EN OK | 7/10 — strong substance, weak visualization on EN |
| Success definition | 3/10 activity not validated | 2/10 no slide visualizes 3-phase | 3/10 no dedicated success slide | 3/10 — V3's metrics are activity proxies, not VC-credible KPIs |
| Moat | 4/10 properties not barriers | 1/10 3-beat verbatim absent on all 3 decks | 3/10 moat slides describe but don't structure | 3/10 — V3 doctrine sharper than v2, but still a product description not a moat |
| Why not GPT | 3/10 engineering choices reproducible | 1/10 no slide on any deck | 2/10 no slide architecture supports the question | 2/10 — hardest gap, needs the most honest reframe |
The honest reframe. The CURRENT moat is not a moat. The PATH to a moat is:
Codex's rewrite (Q1) is the model: "Our architecture is copyable; the compounding asset is validated, customer-specific longitudinal baselines tied to documented management actions. Defensibility exists only when those baselines drive renewals and trusted reseller distribution that a new entrant cannot recreate quickly."
Pivot decision for v5: Stop pitching the architecture AS the moat. Pitch the architecture as the governance enabler that lets the data + trust + renewal moat be built. This is honest at pre-pilot stage and gives Justine room to show the path, not pretend the moat exists today.
| # | Source | Confidence | Finding | v5 action |
|---|---|---|---|---|
| F01 | CODEX | HIGH | Moat 3-beat reads as "properties not barriers" to a hostile VC. SQL/RLS/contracts are copyable by any competent vendor. | Reframe Moat slide: "Our architecture is the governance enabler — the compounding moat is validated longitudinal baselines + renewal-proven trust." |
| F02 | CODEX | HIGH | Microsoft trap (Q2): V3 ignores Microsoft's telemetry + identity + distribution. The "doctrine in data layer" answer explains positioning, not why Microsoft can't copy. | Add explicit acknowledgment: "Microsoft can copy the analytics — our bet is independent governance wins procurement, reseller endorsement and renewal." (Codex Q2 rewrite verbatim.) |
| F03 | CODEX | HIGH | Success metric (Q3): 5 paid pilots measures founder sales not repeatability. 80% SLA gameable. 50 customers via unproven resellers is projection on unvalidated funnels. | Reframe Phase 1 success: "5 paid pilots → evidence of sustained use + documented action + ≥1 renewal." Phase 2 only after repeatable acquisition. Codex Q3 rewrite. |
| F04 | CODEX | HIGH | Why-not-GPT (Q4): Each "beat" fails. Weekend wrappers can run deterministic feature extraction + state + audit logs. | "A weekend wrapper can copy interface + basic metrics; it cannot reproduce validated longitudinal baselines, governance evidence and embedded workflows. Until customers renew because of those assets, Kashi is disciplined architecture, not a moat." (Codex Q4 rewrite verbatim.) |
| F05 | CODEX | HIGH | Biggest blindspot: "You have not proved that structural meeting signals cause useful management action or measurable customer value." | Add slide or explicit statement: "Our Phase 1 milestone is signal-to-action validation, not pilot count." Honest framing wins; spin loses. |
| F06 | GEMINI | HIGH | All 3 decks: 0 verbatim hits for V3 3-beat moat (auditable + reproducible + content-blind). | v5 adds dedicated Moat slide with V3 verbatim 3-beat — but framed per F01 reframe (architecture as enabler not as barrier). |
| F07 | GEMINI | HIGH | All 3 decks: 0 visualizations of V3 3-phase success (5 pilots / 50 customers / default lane). | v5 adds dedicated Success slide with 3 cards, each anchored to a milestone NOT a count. |
| F08 | GEMINI | HIGH | All 3 decks: 0 "Why not GPT" slide. EN 10-slide S6 vague; JA S07 infers via 監視ツール contrast. | v5 adds dedicated Why-not-GPT slide using codex Q4 rewrite as the headline. |
| F09 | GEMINI | HIGH | All 3 decks: "Article 5" used instead of V3-prescribed "Annex III §4". | Search-and-replace across all 3 v5 decks. |
| F10 | GEMINI | HIGH | All 3 decks: "solo" / "単独" framing on founder slide. V3 forbids. | Replace with "co-founder-level teammate / 共同創業者級のチームメイト" across all 3 v5 decks. |
| F11 | GEMINI | HIGH | Alchemist EN S6: "Machine learning on structural patterns" — V3 forbids in moat context. | Replace with "Structural pattern analysis — auditable, reproducible, content-blind." |
| F12 | GEMINI | MED | EN 10-slide S7 "deterministic analyzer" + JA S14 "決定論的に設計" — borderline (technical detector context, not moat). | Replace with "auditable, reproducible analyzer / 監査可能・再現可能" for vocabulary discipline across the deck. |
| F13 | GEMINI | HIGH | EN 10-slide S9 LinkedIn URL placeholder. MUST NOT SHIP. | Resolve LinkedIn URL before 6/22 submission. Add to BRIEFING checklist. |
| F14 | DESIGN | HIGH | Brand palette inconsistency: EN decks use evergreen #324532 + Inter; JA deck uses emerald-700 #047857 + Fraunces + Zen Kaku. | Unify v5 EN long + v5 EN short + v5 JA on evergreen + Inter (with Zen Kaku for JA body). Drop JA Fraunces wordmark for v5 to match EN brand. Tradeoff: lose Fraunces typographic warmth; gain cross-deck brand coherence. |
| F15 | DESIGN | HIGH | 4-dimension visibility fails across all 3 decks. Partners reading the deck cold cannot answer the 4 questions Justine named in <60s each. | v5 = 14-slide structure with explicit Problem / Moat / Why-not-GPT / Success slides each headlined. |
| F16 | DESIGN | MED | AI-slop patterns: "What we do / What we don't" 2-card grid, generic 3-card grids, "Hard to copy" claims without mechanism. | v5 replaces "What we don't" defensive cards with positive "Why this architecture" framing. |
| F17 | DESIGN | MED | JA deck S06 mock SVG visualizations are the strongest single slide in any of 3 decks. | Port the 3-mock pattern to EN v5 decks. Add a similar Product slide. |
| F18 | DESIGN | LOW | JA deck S08 uses "N=1" — JP-startup jargon US/EU partners don't recognize. | Replace with "Pre-pilot / Phase 1 building". |
Single visual structure across all 3 v5 decks (EN long, EN short, JA). Differences: word count + language + appendix slides. Same slide structure = brand coherence + content discipline.
| # | Slide | Headline (V3-aligned) | V3 anchor | Δ from current |
|---|---|---|---|---|
| 1 | Cover | "Before silence becomes resignation." | — | Keep across decks |
| 2 | Hook | "Japan now has resignation agencies. They are the visible symptom of dialogue breakdown." | V3 L23-25, L46-47 | NEW for EN decks; PROMOTE for JA (退職代行 currently in S08 card) |
| 3 | Problem | "More communication ≠ more visibility. 4 early signs before resignation." | V3 L46-47, L100-101 | Existing in all 3; refine headline |
| 4 | Solution | "Kashi reads the SHAPE of how a team talks — never content." | V3 L50, L106 | Existing; verify "machine learning" not used as moat language |
| 5 | Product | 3 role-specific mock visualizations (Exec / Manager / Member) | JA deck S06 pattern | PORT to EN decks; keep in JA |
| 6 | Boundary | "Built in at the data layer (SQL + RLS + contracts) — not in a setting." | V3 L146 verbatim | Existing; extend to V3 3-element formulation |
| 7 | Moat ⭐ NEW | "Architecture is the enabler. The moat is validated longitudinal baselines + trusted distribution." | V3 L144-146 reframed per F01 | NEW SLIDE on all 3 decks. Uses codex Q1 rewrite as honest framing. |
| 8 | Why not GPT ⭐ NEW | "A weekend wrapper can copy the interface — it cannot reproduce validated longitudinal baselines." | V3 L52-58, L108-114 + codex Q4 rewrite | NEW SLIDE on all 3 decks. |
| 9 | Why now | 3 forces (Loss / Obligation / Regulation). EU AI Act Annex III §4. MHLW. 退職代行. | V3 L60, L116 | Search-and-replace Article 5 → Annex III §4 |
| 10 | Market | Tokyo SMB 50-500 + TAM/SAM/SOM + reseller channel breakdown. | V3 L62-63, L120 | Existing in all 3; add reseller breakdown line |
| 11 | Success ⭐ NEW | "Phase 1 (12mo): 5 paid pilots → 1 renewal + documented actions. Phase 2 (24-36mo): 50 paid (30 via reseller). Phase 3 (5yr): default trusted lane." | V3 L152-154 + codex Q3 rewrite (renewal-anchored) | NEW SLIDE on all 3 decks. |
| 12 | Traction | 908 / 25% / pilot conversations + honest "pre-pilot — no paying customers yet" | V3 L66, L126, L162 | Existing; verify "deterministic" word swap |
| 13 | Founder fit | Justine + co-founder-level teammate. Filipino-Japanese. 6-year board lived-problem credential. | V3 L30, L48, L104, L158 | Search-and-replace "solo" → "co-founder-level teammate" on all 3 decks |
| 14 | Ask / Closer | 3 asks + "Before silence becomes resignation. Thank you." | V3 L32, L128, L166 | Existing; verify 3 asks match V3 §"What support do you need from the program" |
Per-deck variations:
• v5 EN long (Alchemist interview): 14 slides exact. Helvetica font fallback for cross-platform .pptx. Speaker notes from V3 3-min script.
• v5 EN short (J-StarX submission): Collapse to 12 slides — merge Moat + Why-not-GPT into one slide titled "Moat — 3 architectural reasons LLMs cannot match"; merge Boundary + Solution into Solution+Boundary. Resolve LinkedIn URL.
• v5 JA: Same 14-slide structure + 2 appendix slides (market math detail + detector spec) explicitly marked Appendix. Replace "Article 5" → "Annex III §4", 単独 → 共同創業者級のチームメイト, 決定論的 → 監査可能・再現可能.
The plan promised this: "Justine reads the v5 deck cold; can he answer each of the 4 dimensions in <60s each with no warmup? If no → loop one more synthesis pass."
Specific cold-read questions to ask of each v5 deck:
| Q | Pass criterion | Source slide(s) |
|---|---|---|
| "What problem are you solving?" | ≤30s answer using V3 L137-138 wording: "Japanese mid-sized companies losing best people to silent communication breakdown. Resignation agencies are the visible symptom." | S2 + S3 |
| "What is your moat?" | ≤45s answer using F01 reframe: "Our architecture is the governance enabler. The moat is compounding validated longitudinal baselines + trusted reseller distribution + renewal proof — none of which Microsoft has or can build quickly." | S7 |
| "What defines success?" | ≤45s answer using V3 L152-154 + F03 reframe: "3 phases. Phase 1 (12mo): 5 paid pilots converting to ≥1 renewal with documented management actions. Phase 2 (24-36mo): 50 paid customers, 30 via reseller. Phase 3 (5yr): default trusted lane." | S11 |
| "Why couldn't a partner just use ChatGPT / Claude / Gemini for this?" | ≤60s answer using V3 L52-58 + F04 reframe: "A weekend wrapper copies the interface but cannot reproduce validated longitudinal baselines, governance evidence, embedded workflows. Until customers renew because of those assets, Kashi is disciplined architecture — not a moat. We're building toward the moat; we don't pretend to have it pre-pilot." | S8 |
If any v5 deck fails the cold-read test: the synthesis brief needs another pass. Don't ship "almost-passes". The 11-day J-StarX window has buffer for one re-synthesis cycle.