Skip to content

docs: generalize world definition to be data-model agnostic - #98

Open
EthanThatOneKid wants to merge 1 commit into
mainfrom
generalize-world-definition
Open

docs: generalize world definition to be data-model agnostic#98
EthanThatOneKid wants to merge 1 commit into
mainfrom
generalize-world-definition

Conversation

@EthanThatOneKid

@EthanThatOneKid EthanThatOneKid commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Summary

The world data structure was defined as an RDF knowledge graph engine
(glossary.mdx ### world, opening of worlds/index.mdx), which made the
concept too specific: a world should be able to be any stateful,
synchronizable, AI-native dataset — including a relational database — not only
an RDF graph.

This PR generalizes the world contract while keeping the RDF knowledge graph
(+ hybrid search) as Worlds' default data model:

  • glossary.mdx — the world entry is now a stateful, versioned,
    synchronizable, AI-native dataset; the RDF graph + hybrid search index is
    described as Worlds' default model, and the entry states the contract is
    data-model agnostic (relational database or another syncable store).
  • worlds/index.mdx — opening paragraph reframed: a world can also be
    backed by a relational database or another syncable store, without naming
    specific products.
  • contribute/style.mdx — terminology rule for lowercase world/worlds
    updated to match (knowledge graphs under the default engine; contract is
    data-model agnostic).

Validation

  • prettier --check passes on all changed files.
  • No links broken: #world / /glossary#world cross-links and the
    #reciprocal-rank-fusion-rrf anchor are unchanged.

Note

mintlify validate is network-dependent (fetches OpenAPI specs) and timed out
locally; it runs in CI.

The 'world' glossary entry and the opening of worlds/index defined a world
as an RDF knowledge graph engine. Reframe the world contract as a stateful,
synchronizable, AI-native dataset, with the RDF knowledge graph and hybrid
search as Worlds' default data model — so relational stores such as Polygres
qualify as worlds too. Update the style-guide terminology entry to match.

Generated with Codebuff 🤖
Co-Authored-By: Codebuff <noreply@codebuff.com>
@EthanThatOneKid
EthanThatOneKid force-pushed the generalize-world-definition branch from 511591b to 8bd066c Compare August 4, 2026 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant