Open Knowledge Format

Keep OKF in git. Cite it from UniFact.

OKF is Google's portable Markdown + YAML knowledge format. Enterprises maintain bundles in version control (or any URL-addressable host). UniFact is where you publish the governed claim agents must not invent.

One Fact. One Truth.

OKF mapping on GitHubWork agents & MCP →

How they fit

OKF lives in git (or a URL)

Enterprise knowledge bundles are Markdown + YAML — reviewed in PRs, hosted on GitHub/GitLab, or served from any HTTPS path agents can open.

UniFact holds the claim

Propose → review → publish. Agents Fact Check the registry for the short, citeable value — not a whole wiki folder.

Link them with evidence.url

Point each published fact at the OKF concept URL (raw git or CDN). Depth stays in OKF; authority stays in UniFact.

Git-first workflow

No website zip import/export. Generate a tree with the CLI when you need a bootstrap, commit it, then link facts to raw URLs.

# Optional: bootstrap an OKF tree from published facts
uni export --okf ./knowledge-okf
git add knowledge-okf && git commit -m "OKF bundle"

# In UniFact (CLI or /facts propose): store the claim + URL
# evidence.url = https://raw.githubusercontent.com/org/repo/main/…
#   unifact/company.policy/return_window.md

# One-time ingest from a checkout (propose only — never auto-publish)
uni import-okf ./knowledge-okf --dry-run

On /facts, propose with an optional OKF / evidence URL field.

Concept mapping

  • Fact namespace/keyOKF path unifact/<namespace>/<key>.md
  • value (published)Short claim agents cite
  • evidence.urlHTTPS URL to the OKF concept (or supporting doc)
  • Maintain OKFGit PRs / CI — not a zip upload on the website
  • Bootstrap from registryCLI: uni export --okf → commit to the knowledge repo

For agents

Fact Check UniFact first

Work agents and @Uni treat published UniFacts as production truth. Open the linked OKF URL only for elaboration — never treat a repo folder as a silent override of publish gates.

EnterpriseOKF spec (Google) →