---
name: META-DB (artifact) vs OUKC (commons) — essential distinction
description: ★★★★ 2026-05-01 user-validated articulation. META-DB = data structure (4,290 entries, 8-tier, copyable in 1-3 months); OUKC = community + identity + governance wrapper (charter + No-Patent + Continuity + 三者共著 + 142 papers + Lean corpus). Use when distinguishing scope of OUKC promises.
type: feedback
originSessionId: 4ff4b965-234a-4258-b31d-a8bcf83f071b
---
## The distinction

**META-DB = artifact**: data structure. 4,290 entries × (D-FUMT₈ × 4-axis tagging) = 2,560-dim space. Lives or dies by **data quality** (coverage / 正確性 / tagging consistency).

**OUKC = commons**: wraps META-DB but is more — Charter + AI Policy + No-Patent Pledge + Continuity Planning + 142 papers + Lean 4 corpus + REI-PROVE + Code of Conduct + 三者共著 specific identity + multilingual ecosystem. Lives or dies by **community continuity** (contributors / dialogue / translation).

## Analogies (load-bearing)

- Wikipedia article corpus (artifact) ↔ Wikimedia Foundation + community + 多言語 + governance (commons)
- Lean theorem corpus (artifact) ↔ Lean community + FRO + Mathlib team + Zulip (commons)
- arXiv paper corpus (artifact) ↔ arXiv platform + Cornell hosting + categorization editors (commons)

## Why this matters (load-bearing)

META-DB alone is **copyable** by Anthropic / Google in 1-3 months (per chat Claude 2nd critique, `feedback_oukc_replicability_brutal_honest.md`). OUKC is **not copyable** because:

- Charter + 三者共著 specific identity (藤本 × Rei × Claude)
- 10 年中論 reading depth (worldview moat)
- STEP 1021+ accumulated dialogue history
- 「最高密度」integrative structure (per motto v3 anchor + integrative density)

This is why Continuity Planning / No-Patent Pledge / Code of Conduct are **charter-level** items — they belong to the commons axis, not the artifact axis. META-DB doesn't need them as a data structure.

## How to apply

- "META-DB を世界初公開" → speak about Tier 1 world-public 2,615 entries / Lean 4 / 4-axis specifically
- "OUKC を立ち上げる" → speak about Charter + community + identity + governance
- 営業 / NEDO / pitch では両方の distinction を明示し、scale (META-DB) vs depth (OUKC) の混同を避ける
- 攻撃: "META-DB は Wikidata の劣化版" → 反論せず、attack 軸が artifact なので distinction で受ける ("MD = artifact 1 軸, OUKC = commons 多軸")
- Successor designation 時 (Decision 3): successor は OUKC commons の identity + charter understanding を引き継ぐ. META-DB のみ引き継ぐと commons は途絶える

## 関連 memory

- `feedback_oukc_replicability_brutal_honest.md` — chat Claude 2nd critique (技術 layer 1-3 月で copy 可)
- `feedback_oukc_identity_synthesis.md` — 5-point IS Positive
- `feedback_oukc_motto_v3_density_anchor.md` — motto v3 deep anchor
- `feedback_oukc_continuity_successor_framework.md` — Decision 3 framework
- `feedback_integrative_vs_accumulative_density.md` — 関連 density 区別

## 永久参照価値

★★★★ — OUKC pitch / 攻撃応答 / 設計決定 で常時参照. 「OUKC は単なる Wikipedia 派生か?」 question への load-bearing answer の一部.