Open Knowledge Format Mapping

What makes Open Knowledge Format useful here?

It validates the wiki as an agent-readable knowledge bundle: markdown files, YAML frontmatter, stable paths, normal links, and change logs.

The local rule is stricter than OKF. OKF defines the portable minimum. Dreamineering standards define the working contract for this wiki.

For agent-facing knowledge, the working contract starts at Agent Knowledge Contract. The /agents pages are rendered projections; /playbook/agents is the OKF-readable source layer that external AI agents can quote, link, export, and improve.

Portable context is not enough. An agent also needs Delegation: the decision-rights layer that says when it may act alone, ask first, escalate, or refuse.

What OKF Adds

Google Cloud introduced Open Knowledge Format on June 13, 2026 as an open specification for portable AI context. The core shape is simple:

• a directory of markdown files
• one concept per file
• YAML frontmatter for queryable fields
• normal markdown links as graph edges
• optional index.md files for progressive disclosure
• optional log.md files for chronological history

The article says OKF v0.1 is minimally opinionated: every concept needs a type field, while producers choose their own content model. That makes OKF a lowest-common-denominator exchange format, not a full writing standard.

Local Mapping

OKF convention	Dreamineering standard	Local rule
type frontmatter	Page Types	type means page job: hub, concept, playbook, domain-map, and so on.
Markdown file	Documentation Writing Standard	A page must stand alone without private project context.
File path as identity	Naming Standards	Route and filename are stable semantic handles.
index.md hierarchy	Index Page Standard and Hub Index Template	Index pages route before they teach.
YAML frontmatter	Wiki Schema	Frontmatter is queryable map data, not decoration.
Markdown links	Information Architecture Standard	Links should carry scent and typed relationship intent.
log.md history	Wiki-log pattern	Public pages teach current truth; the private wiki log records schema evolution.

Agent Knowledge Contract

Agent-facing knowledge has one extra rule: a page must say whether it is source, projection, discovery, execution, or proof.

Layer	Home	Job
Source	/playbook/agents/	OKF-readable markdown that names current language, capability, evidence, receipts, services, and loops.
Projection	/agents/**	Rich public React surfaces rendered from or pointing back to the source contract.
Discovery	agent.json, llms.txt, llms-full.txt	Machine-readable entry points for external agents.
Delegation	Delegation	Decision rights that bound act-alone, ask-first, escalation, and refusal cases.
Execution	Skills, hooks, and Stackmates drmg	Procedures and build loops that make the contract operational.
Proof	receipts, capability mirrors, Stackmates evidence	Closed-loop evidence of what is REALITY, DREAM, or CONSUMED.

Design Decision

Treat OKF as an interoperability benchmark, not the source of truth.

Dreamineering pages should be easy to export toward OKF because they already use markdown, frontmatter, semantic paths, and links. They should not weaken their local contract to match OKF's minimum. A touched page still needs the stricter page-type/template match described in Page Types.

Use This When

• checking whether a playbook page is machine-readable enough for external agents
• deciding whether an agent-facing contract belongs in /playbook/agents or remains a rendered /agents projection
• deciding whether portable context is enough for an agent to act without asking Wik
• designing an export, manifest, or bundle format
• explaining why type, title, description, tags, links, and logs matter
• comparing local wiki rules to open knowledge-sharing standards

Checks

An OKF-aligned Dreamineering page passes when these signals are visible:

• type exists and matches Page Types
• title and description explain the page job
• route and filename are stable semantic handles
• links have scent, not bare labels
• current truth lives in public docs, while schema evolution is logged privately

Automation

Run the OKF audit before broad playbook metadata work:

pnpm playbook:okf

Apply the safe mechanical fields with:

pnpm playbook:okf:write

The script adds missing type, description, template, template_url, loop_phase, and level fields. It preserves nested YAML blocks such as instrument: and provenance maps. It treats nested index.md and index.mdx files as subject-navigation pages, which map to the local hub page type.

After the map is clean, run the value gauge:

pnpm playbook:okf:value

This report turns metadata into a cleanup queue. It shows weak descriptions, missing tags, template drift, orphan pages, weak link scent, and the highest-value hubs. Use it after generate-playbook-manifest.mjs so the report reads the current map.

Failure Modes

• Minimum becomes ceiling — OKF requires type, but the local page still needs the right page type and template.
• Portable but weak — markdown exports cleanly, but links lack scent and agents cannot choose the next page.
• Path drift — the file path stops naming the concept clearly.
• Log leak — private evolution history appears in public teaching prose.

Source Trail

• Github Repo
• Google Cloud: Introducing the Open Knowledge Format — source article for OKF v0.1.
• Page Types — local page-job authority.
• Wiki Schema — local Map-First edit and frontmatter contract.
• Information Architecture Standard — local placement, links, and answer-engine rules.

Context

• Purpose — the Tight Five root for why a page exists.
• Platform — where portable knowledge formats become useful infrastructure.
• Performance — how retrieval and answer quality should be measured.

Questions

What would fail if this wiki were exported as an OKF bundle tomorrow?

• Which page lacks a meaningful type?
• Which route depends on private context?
• Which links are present but carry no scent?
• Which generated projections need a portable manifest?