# v0.5 Entry Handover — Enterprise Ontology Mount Track (2026-06-12)

> **Cycle**: v0.4.4 closed → **v0.5 entry**.
> **Date**: 2026-06-12 (post-v0.4.4 GitHub Release, post-Zenodo DOI
> 10.5281/zenodo.20652679 mint, post-21-PR enterprise polish + audit
> session).
> **Operator decision**: "이제는 진짜 엔터프라이즈 온톨로지 장착으로
> 간다" (2026-06-12).
> **Previous CLAUDE.md theme**: Direction α (hybrid cloud reasoning
> tier) — closed 2026-06-04 with premise 미입증.

---

## 1. v0.5 entry 선언

After 21 PRs (#819-#839) closing v0.4.4 (LRB v0.2.3 S3 publication-
scale + cycle γ 4-bench infrastructure closure + arXiv preprint pre-
flight + enterprise polish across every customer-facing surface), the
operator has decided to enter **v0.5 cycle**.

v0.5 = **first-domain pilot path**. The cycle is defined by
[`docs/strategy/v0.5-pilot-scope-spec-2026-06-11.md`](../strategy/v0.5-pilot-scope-spec-2026-06-11.md)
(Dim F production proof gate: ≥6 months external customer pilot, 0
core regressions, success metrics evidence) and target domain by
[`docs/strategy/v0.5-domain-candidate-evaluation-2026-06-11.md`](../strategy/v0.5-domain-candidate-evaluation-2026-06-11.md)
(Legal contract review = 86% Primary).

## 2. CLAUDE.md rule #1 정합

> **Critical rule** (CLAUDE.md): *Do not add new domain features
> (legal-specific, food-specific, retail-specific, etc.) until v1.0.
> Mother-hardening mode. Any domain-coupled work pollutes the
> platform contract and will be reverted in review.*

v0.5 entry **does NOT change this rule**. v0.5 = **pilot prep** +
**enterprise-fitness mother features**. Domain-specific code (legal
contract clauses, force-majeure ontology, governing-law type
hierarchy, etc.) **still waits until v1.0** or until a signed
external pilot LOI defines the customer-specific pack (per `v0.5-
pilot-scope-spec` §"Scope discipline").

### 2.1 What "enterprise ontology mount" means in v0.5

| Layer | Allowed in v0.5 | Blocked until v1.0 (or LOI) |
|---|---|---|
| **Mother-platform enterprise-fitness** (multi-tenant ontology namespaces, finer ABAC, customer-deployment hardening) | ✓ Allowed — these are mother-level, not vertical | — |
| **Generic enterprise ontology primitives** (Department / Role / Document_Class / Policy / Audit_Event extensions if not vertical-coupled) | ✓ Allowed if domain-neutral | — |
| **Legal-vertical ontology pack** (force_majeure, indemnification, governing_law, etc.) | ✗ Blocked | ✗ Blocked (LOI gates the pack scope) |
| **Customer-specific data ingestion pipelines** | ✗ Blocked | ✓ After LOI — customer-specific addenda |
| **Customer-specific UI / workflows** | ✗ Blocked | ✓ After LOI |

### 2.2 The "enterprise ontology mount" framing

What the operator means by "엔터프라이즈 온톨로지 장착" in v0.5 context:

1. **Mother-platform ontology framework** that makes legal pack (or any
   domain pack) **mountable** when LOI is signed — without changing
   `core/`.
2. **Plugin API freeze** for ontology packs (a v0.5 → v1.0 gate item).
3. **Enterprise deployment surface** (multi-tenant workspace
   isolation, sovereign deployment patterns, customer-facing API
   stability).
4. **Customer-facing evidence** that the mother-platform can carry an
   enterprise ontology — without the operator having a signed customer
   pilot yet.

→ This is **all mother-level work**. The v1.0 plugin API freeze gate
defined in [`docs/PLATFORM_READINESS.md`](../PLATFORM_READINESS.md)
is the actual gate.

## 3. v0.5 cycle work streams

### Stream A — pre-LOI material refresh + Hashevolution dogfooding (started 2026-06-12)

- **A.1** v0.4.4 callout block 추가 across 7 pre-LOI materials ✓ done
- **A.2** Hashevolution own-company pilot scenario doc (시나리오 C 권장
  = internal dogfooding + external outreach 병행) ✓ done
- **A.3** (operator action) Hashevolution 운영 자료 inventory + JAMES
  workspace ingest + 일일 사용 → 1+ 개월 internal iteration
- **A.4** (operator action) Tier S contact list ~30 명 + LinkedIn
  profile + cold outreach 시작

### Stream B — enterprise ontology framework (mother-level, scopable now)

Scope is intentionally narrow to respect CLAUDE.md rule #1. Subject
to refinement based on dogfooding feedback (A.3).

- **B.1** Audit ontology surface review — does the current
  `core/lifecycle/{schema,supersede_chain,contradiction_arbiter,
  causality}.py` 동작 충분히 enterprise-grade인지 평가.
- **B.2** Multi-tenant workspace isolation review — current `JAMES_
  WORKSPACE` env pattern 이 multi-tenant 시나리오에서 어떤 boundary
  를 정의하는지 명시 + 한계 식별.
- **B.3** Plugin API stability review — current plugin loader
  (`_load_plugins` in `core/reasoning/backends/__init__.py`) 가
  ontology pack 을 mountable 한 surface 인지 평가; 변경 필요한 점
  명시 (v1.0 freeze gate 의 입력).
- **B.4** Enterprise deployment doc — `docs/security/` + `docs/
  ARCHITECTURE.md §multi-tenant` 신규 / 갱신.

### Stream C — measurement infrastructure (operator-attended, separate cycles)

These are pre-existing v0.4.4 follow-up cycles, not new work:
- v0.2.3b LLM-grounded S3 cross-model measurement (~4-6h wall)
- D-alce + D-2wiki research-tier measurement
- HR full sweep n=100
- arXiv preprint submission (Path A defer — pending v0.5 outreach
  outcome 재평가)

### Stream D — gated on LOI (블록)

- Legal-vertical ontology pack scope + build
- Customer-specific NDA / DPA / MSA / SLA addenda
- Pilot kickoff + 6개월 측정 + Dim F gate clear

## 4. v0.5 success criteria (entry-level definition)

At v0.5 cycle close, the following should be true:

| Surface | Success threshold |
|---|---|
| Internal dogfooding (A.3) | 1+ months of daily operator use; bug catch / UX feedback documented |
| External outreach (A.4) | Tier S contacts sent; response rate measured; channel mix adjusted |
| Enterprise ontology framework (B) | Audit / multi-tenant / plugin API review docs published; v1.0 plugin-API-freeze gate definition updated in PLATFORM_READINESS.md |
| LOI track | ≥1 customer LOI signed OR 'no LOI within 6 months → reassess strategy' decision |

**Dim F gate** (≥6 month external customer pilot + measured success
metrics) is the v0.5 → v0.6 gate, NOT the v0.5 close.

## 5. Critical rules (carry-over from CLAUDE.md, unchanged at v0.5 entry)

1. **No domain features until v1.0** — preserved
2. **Every PR touching `core/retrieval|graph|reasoning` requires
   bench numbers + Quality Delta Card** — preserved
3. **Self-evolution opt-in only** — preserved
4. **Architecture changes require `architecture` label PR** — preserved
5. **`core/` module size cap = 20 KB** — preserved

New v0.5 layer rules (additive):

6. **Dogfooding evidence ≠ Dim F evidence**. Hashevolution own-
   company internal usage is iteration feedback only; Dim F gate
   requires external customer.
7. **Enterprise ontology = mother-level**. Vertical ontology
   (legal-specific, etc.) waits until LOI scopes the pack.
8. **External-facing claims gated on measurement evidence**. Customer-
   facing materials reference committed result.json artefacts +
   Zenodo DOI; no aspirational claims.

## 6. Where to look next (CLAUDE.md update incoming)

After v0.5 entry, the CLAUDE.md "Where to look next" table's top row
should point at this doc. Suggested header row:

```
| 🟢🟢🟢 NEXT SESSION ENTRY (read this first — 2026-06-12 v0.5 entry) |
docs/handovers/v0.5-entry-2026-06-12.md (Stream A: pre-LOI material
refresh + Hashevolution dogfooding 시나리오 C 권장; Stream B:
enterprise ontology framework mother-level scope; v0.5 success criteria
+ 3 new rules carry-over rule #1 보존)
```

## 7. Operator next actions (P0)

```
[ ] Hashevolution 운영 자료 inventory (1-2 day)
[ ] JAMES workspace 본인 자료 ingest (1 day)
[ ] 일일 사용 시작 + weekly internal feedback note
[ ] Tier S contact list 작성 (~30 명, 본인 네트워크)
[ ] LinkedIn 프로필 v0.4.4 갱신 + announcement post
[ ] 첫 cold outreach batch (10 명) → 응답 분석 → batch 2
[ ] Stream B 시작 시점 결정 (dogfooding 1+개월 후 권장)
```

## 8. 관련

- `docs/strategy/v0.5-pre-loi-materials/` (refresh + new 08
  Hashevolution scenario)
- `docs/strategy/v0.5-customer-outreach-playbook-2026-06-12.md`
- `docs/strategy/v0.5-pilot-scope-spec-2026-06-11.md`
- `docs/strategy/v0.5-domain-candidate-evaluation-2026-06-11.md`
- `docs/PLATFORM_READINESS.md` (Dim F gate)
- `docs/handovers/v0.4-next-session-entry-2026-06-12-pm.md` (v0.4.4
  closure entry)
- `docs/research/routing-exercise-verification-2026-06-12.md`
  (routing track design-complete confirmed)
- Memory: `feedback_self_evaluation_trap` (시나리오 B 회피),
  `feedback_build_dont_broadcast` (internal vs external 정합)
