Google shipped an open knowledge-interchange format the day before this was written. It lands next to Loomworks and stops, by design, exactly where Loomworks begins.
What this document does. It examines Google's Open Knowledge Format — published 12 June 2026 — and sets it against what Loomworks is building, so the relationship is understood rather than guessed at.
What it concludes. The Open Knowledge Format is a knowledge interchange format that maps onto the wire layer near Loom, not onto the Memory room. It deliberately carries thin provenance and no governance. That is the layer Loomworks occupies. The arrival reads as validation of the direction, and it sharpens the line Loomworks draws around itself.
What decision is needed. None now. Two interoperability directions are recorded at the end — consuming an Open Knowledge Format bundle as a contribution pathway, and emitting one as a render-type. Both touch seed-governed territory (shape-types and render-types) and are recorded as candidates, not decided.
Scope. Conceptual and strategic comparison. No code, no specification change, no seed amendment proposed.
A format, deliberately not a service.
The Open Knowledge Format is a directory of plain Markdown files. Each file is a single concept — a table, a dataset, a metric, a runbook, an interface description. The file path is the concept's identity. Each file carries a small block of structured front matter for the fields that need to be queryable — a type, a title, a description, a source link, tags, and a timestamp — and a Markdown body for everything else. Of those, only the type is required. Concepts reference each other with ordinary Markdown links, and those links turn the directory into a graph.
That is the whole of it. No runtime, no software development kit, no compression scheme. A bundle is just files: readable in any editor, shippable as an archive, hostable in any version-control repository. It formalises the “knowledge as a living wiki” pattern — the same pattern that has appeared as Obsidian vaults wired to coding agents, as the convention files coding agents read before they work, as metadata-as-code repositories — into a small set of shared conventions so that a wiki written by one producer can be read by a different consumer without translation.
Its purpose is to give artificial-intelligence systems the internal context they otherwise have to reassemble from scattered, incompatible surfaces every time. It is published as an open specification, vendor-neutral, with contributions invited.
It is not the Memory room. It is nearer the wire.
The first framing of this comparison placed the Open Knowledge Format against Loomworks Memory directly. That framing is too loose, and correcting it is what makes the rest sharp. The Open Knowledge Format is an interchange format — a way to serialise knowledge so it survives moving between systems. In Loomworks terms that is the neighbourhood of the Loom wire layer, the layer that rests on the W3C PROV provenance standard. It is not Memory.
Memory is a room inside a running engine, with provenance accumulating against every contribution and a governance gate above it. The Open Knowledge Format has no engine, no room, no gate. So the honest pairing is the Open Knowledge Format against Loom-as-wire-format, with Memory sitting one full layer above what the Open Knowledge Format describes. Holding that distinction is what keeps the rest of this document from comparing two things of different kinds.
Two real overlaps, both worth naming plainly.
Producer and consumer are separated. The Open Knowledge Format draws a clean line between who writes knowledge and who reads it: a bundle authored by a person can be read by an agent, a bundle generated by a pipeline can be browsed by a viewer, and the format is the contract between them. That is close in spirit to the Loomworks principle that the source supplies and the Operator governs — both refuse to bind the writer and the reader into one fixed shape.
The underlying bet is the same. The Open Knowledge Format rests on the belief that systems in the agentic era need a portable, durable knowledge substrate rather than another catalogue locked behind one vendor's interface. That is the bet Loomworks made. The largest player in the space has now endorsed the direction in public. That is useful, not threatening.
The format ships the commodity floor and leaves the governance-and-recall layer open. That layer is the product.
| Axis | Open Knowledge Format | Loomworks |
|---|---|---|
| Provenance | A timestamp, a source link, an optional change log. Thin by design. | Provenance is the trust mechanism. Every contribution carries origin threads; artificial-intelligence origin is marked and cannot be suppressed; the trust axis is tie-to-source. |
| Unit of knowledge | One concept per file — a document-sized unit. | The assertion — a far finer unit, each one threaded to where it came from. |
| Recall | Markdown cross-links and an index file for navigation. Finding by traversal. | Recall as the product: surfacing the relevant thing, knowing what links, noticing when a premise changed. |
| Corrections | A change log; version-control history. A superseded fact is overwritten, recoverable only by diff. | Corrections preserved, not smoothed. A superseded assertion stays in Memory as a correction; the trajectory is walkable. |
| Governance | None. Anyone produces, anyone consumes, no approval before knowledge settles. | The Operator approves before anything settles. The machine surfaces and signals; the Operator decides. |
| Identity and authorisation | None. Access is whatever the filesystem or repository provides. | System-assigned identity and OVA authorisation built into the substrate; read access and write access as separate axes. |
| Layers above | Stops at representation. It is input substrate for something else. | Manifestation, Shaping, and Rendering all sit above Memory and have no counterpart in the format. |
The pattern across the whole table is one thing said seven ways: the Open Knowledge Format is minimally opinionated on purpose, requiring exactly one field of any concept and leaving everything else to the producer. Its openness is its virtue and its ceiling. The work it declines — provenance as trust, recall over a moving body of knowledge, an approval gate, an identity model, and the three rooms that turn knowledge into a reader-specific artifact — is precisely the work Loomworks exists to do.
The same arrival can be read as endorsement, as contrast, or as a connector.
The market direction Loomworks bet on is now affirmed by the largest player in it. The “knowledge as a living substrate” pattern is real and named. That strengthens the narrative without changing the build.
The Open Knowledge Format draws the commodity line on Loomworks' behalf: it is the portable shape of knowledge; Loomworks is the governed, provenance-bearing, recall-capable layer that knowledge in that shape can feed into and be produced from. The risk to manage is being mistaken for a richer version of the format. The pitch that avoids that: name the format as the floor and Loomworks as the layer above it.
The format is a natural ingestion shape and a natural emission shape. Treating it as both would make Loomworks fluent in an emerging common language without ceding the layer that sits above that language. The two concrete moves are recorded in the next section.
Two candidate moves. Both touch seed-governed territory. Neither is proposed for adoption here.
An operational engagement that ingests an Open Knowledge Format bundle, reading each concept file as external data and attaching provenance threads on the way in — so that knowledge arriving in the common shape gains the tie-to-source it lacked at origin. The format's thin provenance becomes the input; Loomworks supplies the layer it was missing.
Flag: this defines a new shape-type for incoming material. Shape-types are seed-governed. Recorded as a candidate for a later seed or specification decision.
A render-type that emits a Manifestation or a Render as a conformant Open Knowledge Format bundle — Loomworks knowledge leaving in the common shape, consumable by any agent or viewer that already speaks the format, while the provenance and governance stay recorded on the Loomworks side.
Flag: this defines a new render-type. Render-types are seed-governed. Recorded as a candidate for a later seed or specification decision.
Both directions share one shape: the Open Knowledge Format is the boundary format, and Loomworks is the system on the inside of that boundary that does the work the format does not attempt. Adopting either is an Operator decision against the seed, not a conclusion of this investigation.
Google Cloud Blog — “Introducing the Open Knowledge Format” (Sam McVeety, Amir Hormati), 12 June 2026.
GoogleCloudPlatform/knowledge-catalog — Open Knowledge Format v0.1 specification and reference implementations, GitHub.
Loomworks commitments referenced: candidate seed (four rooms, authentication framework, source-supplies/Operator-governs), provenance-threads and Memory-equals-recall framings, and the Loom protocol resting on the W3C PROV standard.