Adopt Open Knowledge Format for the Doozer brain

decisions/okf-adoption.md · Decision · okf, knowledge, decision

unverified: no trust signals recorded yet

Why Doozer organizes its knowledge as an OKF bundle, scoped to the stable core.

Adopt Open Knowledge Format for the Doozer brain

Decision (June 2026): organize Doozer's internal knowledge as an Open Knowledge Format bundle (this knowledge/ directory) and build exploration tools on it.

Why

• OKF is "just files": markdown + YAML frontmatter in a typed tree, with markdown links

as graph edges. Vendor-neutral, SDK-free — a perfect fit for Doozer's FTP / no-env model.

• Doozer already speaks it: the memory topic files are frontmatter-markdown, docs/ is

categorized markdown, and includes/design-md.php already emits and serves OKF-shaped /design.md artifacts.

• It gives a durable, linkable "brain" beyond the flat MEMORY.md index — usable by

agents (future Claude) and humans alike.

Scope and caveats

• Adopt the STABLE core (markdown + frontmatter + links). OKF is v0.1, so do NOT couple

to Google's Knowledge Catalog ingestion yet.

• The brain is ADDITIVE: CLAUDE.md (instructions) and MEMORY.md (recall index) keep

their roles. See how to grow the brain.

• Engine: includes/okf-engine.php parses this bundle, emits the live network as OKF

nodes (the flywheel's data), and exports a portable zip. Explorer: Admin → Doozer Brain.

Branding: OKF is plumbing, Doozer Atlas is the product

The outward, AI-native emission layer is branded Doozer Atlas (real-world entities continuously emitting machine-readable knowledge). OKF and schema.org JSON-LD are exports of that layer, not the product. Pairs with the Doozer Brain (internal knowledge) as Brain (inward) vs Atlas (outward). The per-entity public endpoint is /.well-known/doozer-atlas (format: doozer-atlas/0.1); see the flywheel.

Atlas principles (the guardrails)

1. Atlas emits facts, not hallucinations. AI is a CONSUMER of Atlas, not its source.
2. Public information only. Never private contact data.
3. Relationships are first-class objects (CONTAINS, DISCOVERABLE_IN, LOCATED_IN,

IN_NICHE, NEARBY, COVERS_NICHE/PLACE, HOSTS_EVENT). Density is the long-term moat, but only emit edges DERIVED from real data, never invented.

4. Atlas exists automatically for every Doozer host (business, cloud, root, VD).
5. Every field must justify its existence: "will this help a human, AI, or another

Doozer system understand the world around this entity?" If no, do not emit it. Keep Atlas small and intentional, not a dumping ground.

6. Provenance is the differentiator: per-field source + an owner-verified tier (tied to

implicit verification) is trust infrastructure nobody can copy. Strengthen it over time (confidence, verified_at).

Architecture note: Atlas OWNS THE CONTRACT, not the storage. It is a DERIVED projection over the source-of-truth tables (always fresh, no migration, no dual-write). OKF / schema.org / the /.well-known/doozer-atlas JSON are exports of the same model. Resist "Atlas owns a graph DB" and "site renders FROM Atlas" (a rewrite); evolve, don't rebuild.

Deferred (roadmap)

Public publishing (/knowledge.md + a public explorer), a build-in-public marketing beat, and a self-growing enrichment agent.