# v0.2.1 — Business Track Handover

> Companion to `v0.2.0-platform-track.md`.
> v0.2.0 covers ENGINEERING. This file covers the BUSINESS frame
> that engineering must NOT couple to, but should be aware of.
>
> Status: living document. Last updated: v0.2.1 entry.

---

## 0. Why this file exists separately

If a Claude Code session conflates engineering decisions with
business hypotheses, the platform fails:

- A code change is made to "make customer X happy" → mother hardens
  around one domain's assumptions → other domains can no longer fit
  cleanly.
- A roadmap milestone is renamed to match a sales pitch → technical
  priorities follow sales rather than platform health.

This document records the business hypothesis so it is **legible to
engineering sessions but not mixed into engineering decisions**.
Code sessions read it for context, not for instructions.

---

## 1. Strategic frame (one paragraph)

JAMES is a mother platform. We will build the mother + ONE reference
domain pack (cafe / 음료 매장) with zero starting capital over
18–24 months. After the first reference pack runs in production with
one customer for 6+ months, we will pursue capital and add the
remaining domains (travel, then government) sequentially. We will
NOT pursue any of the three domains in parallel before the first one
is operationally proven.

---

## 2. Target market (long horizon)

JAMES targets the intersection of three constraints:

- **Local / on-prem only** (cloud-rejecting customers)
- **Multi-domain accumulation potential** (not single-domain SaaS)
- **Korean-language-first**, English second

This intersection is small but real. Three domains are on the long
horizon, ranked by capital-zero entry feasibility:

| Domain | Barrier | Zero-capital entry | Earliest realistic gate |
|---|---|---|---|
| Cafe / franchise HQ (음료) | low | ~10% | v0.4 First Pilot (free PoC) |
| Travel / OTA (여행) | medium | ~3% | After seed funding, post-v0.4 |
| Government (정부) | high | ~1% | After Series A + GS/CC certs (~3 yrs) |

The operator's earlier sketch of "자메스0 / 자메스00 / 자메스000"
domain forks is recorded here as a long-horizon option. It does
NOT happen before mother v1.0.

---

## 3. The "no parallel domains" rule

This rule overrides any feature request, customer ask, or roadmap
PR during v0.2 ~ v0.4.

> Until the first domain pack (cafe) has run in production for
> 6 months without a mother-level regression, no second domain is
> introduced — in code, marketing, or roadmap text.

Concrete prohibitions during v0.2 ~ v0.4:

- No `packs/travel/`, `packs/government/`, or related stub directories
- No README mention of travel or government use cases beyond the
  "domain candidates" table in `docs/PLATFORM_READINESS.md`
- No grant application that promises three-vertical delivery in the
  v1.0 timeline
- No capital pitch that names all three domains as near-term revenue
- No customer-specific feature added to mother during this window

This rule is recorded because the operator has already correctly
identified the temptation as the project's biggest risk.

---

## 4. Capital path (high level only)

Specific tactical details — target company lists, financial
projections, contact strategies, cold-email templates — live in
**private operator notes outside this repository**.

Public summary only:

| Phase | Source | Indicative size | Indicative timing |
|---|---|---|---|
| Non-dilutive seed | Korean government programs (창진원 예비창업패키지, NIPA, K-Global) | 1~3억 | months 6~12 |
| Bootstrap revenue (optional) | Custom RAG / GraphRAG consulting (1~2 customers) | 1~3억/year | months 6~24 |
| Dilutive seed | Korean VC seed round | 3~10억 | months 16~22, after first PoC reference |
| Series A | follow-on after first pilot success | 30억+ | months 30+ |

The first grant application target is **예비창업패키지 (창업진흥원)**,
opening Feb–Mar each year. The actual application draft lives as a
separate artifact (private notes), not in this handover.

---

## 5. Engineering ↔ business interaction rules

| Decision type | Where it is made |
|---|---|
| Module split, refactor, eval threshold | **Engineering** (code session) |
| Roadmap calendar slip | Engineering, with rationale in PR body |
| Domain pack to build first | **Business** (this doc); engineering executes |
| Roadmap milestone rename | Engineering only — never to match a sales pitch |
| Customer-specific feature | **Forbidden during v0.2 ~ v0.4** |
| Marketing claim added to README | Business, but requires concrete evidence in code |

If a code session encounters an ambiguous request that smells like
"add this for customer X" — pause and confirm with the operator
before shipping.

---

## 6. The 18–24 month skeleton (calendar)

```
M  0–4    v0.2 Foundation Hardening (engineering only)
M  1      ★ Submit 예비창업패키지 application (annual cycle)
M  4–10   v0.3 Platform Skeleton + general reference pack
M  6–9    ★ Government grant decision (if approved: ~1억 non-dilutive)
M 10–16   packs/cafe/ — first non-general reference pack
M 14–18   Free PoC with one cafe franchise HQ
M 16–22   ★ Seed fundraising (dilutive) — using cafe PoC as evidence
M 22+     Travel domain begins (only after seed closes)
M 36+     Government domain begins (only after Series A or equivalent)
```

This calendar is aspirational. Slips of 30–50% are normal for solo
+ AI-paired open-source projects. **The discipline above survives
the slip; the calendar does not.**

---

## 7. What stays in this repo vs what stays private

**Public (this repo, OK to commit)**:
- Strategic frame (one paragraph)
- Domain horizon table (no specific company names)
- Discipline rules
- High-level capital path (order-of-magnitude figures only)
- Calendar skeleton

**Private (operator's local notes, NEVER committed)**:
- Specific franchise / OTA / agency target lists
- Cold-email templates and individual contact information
- Detailed financial projections
- Investor target lists
- Personal runway, salary, equity intentions
- Co-founder candidate names and conversations

If a code session sees information that looks private leaking into
a PR or commit, flag it before merge.

---

## 8. Decision log (append-only)

| Date | Decision | Rationale |
|---|---|---|
| v0.2.1 entry | Cafe selected as first domain | Lowest legal liability + accessible PoC partner space + modest hardware/infra demand |
| v0.2.1 entry | Government deferred to ~3 years | CC/GS certification cost (~5억+) and procurement registration require corporate maturity that solo OSS does not have |
| v0.2.1 entry | Travel deferred to post-seed | GDS/CRS integration complexity + competitive density (large OTAs run in-house AI teams) |
| v0.2.1 entry | "No parallel domains" rule adopted | Operator-confirmed risk that simultaneous pursuit destroys mother contract |
| v0.2.1 entry | Long-horizon naming "자메스0/00/000" recorded but not adopted | Marketing-friendly named packs (e.g. JAMES Brew / Compass / Atlas) preferred; final naming deferred until pre-seed |

Future decisions append below. Do not delete history.

---

## 9. Companion documents

| Document | Purpose |
|---|---|
| `CLAUDE.md` | Session-start primer (read first) |
| `docs/PLATFORM_READINESS.md` | 6-dimension readiness + v0.3/v0.4/v1.0 gates |
| `docs/ARCHITECTURE.md` | Design principles + non-goals |
| `ROADMAP.md` | Engineering milestones |
| `docs/handovers/v0.2.0-platform-track.md` | Engineering track handover |
| **`docs/handovers/v0.2.1-business-track.md`** | **This file — business track** |
| (private) operator notes | Tactical details outside repo |

The two v0.2 handovers (.0 engineering + .1 business) together
define the v0.2 cycle's full context. Subsequent cycles add a
new matched pair (e.g. v0.3.0-platform-track + v0.3.1-business-track).

---

## 10. How to update this document

- **Strategic frame change** (e.g. add a fourth domain horizon):
  PR with the `business-track` label and rationale; require operator
  approval. Engineering does not approve business frame changes.
- **Decision log append**: any operator-level decision that changes
  the calendar, capital path, or domain order. Append-only.
- **Tactical detail leak**: if a contributor adds private-flavor
  content (specific names, real financial figures), revert the PR
  and move the content to private notes.

---

## 11. 한국어 요약

이 문서는 **사업 가설을 기록**하되 **엔지니어링 결정에 직접 영향을 주지 않도록 분리**합니다. 핵심 규칙 5가지:

1. **음료(cafe) 1개 도메인 우선**, 여행·정부는 음료 PoC 6개월 운영 후에만 진입
2. v0.2 ~ v0.4 동안 **3개 도메인 병행 금지** (마케팅·코드·로드맵 모두)
3. 자본 경로: 예비창업패키지 → 음료 PoC → 시드. 정부 시장은 약 3년 후
4. 구체적 영업 대상·재무 수치·투자자 명단은 **이 저장소가 아닌 비공개 노트**에 보관
5. "고객 X를 위한 기능 추가" 류 요청은 v0.2 ~ v0.4 동안 **금지**

엔지니어링 세션은 이 문서를 컨텍스트로 읽되, 코드 결정 자체는
`ROADMAP.md`와 `docs/PLATFORM_READINESS.md`를 따릅니다.

장기 horizon으로 메모된 "자메스0 / 자메스00 / 자메스000" 분화 구상은
v1.0 이후의 옵션이며 그 전엔 어떠한 형태로도 코드·마케팅에 반영하지 않습니다.
