Repository navigation
docs: stop claiming Worlds is an append-only ledger - #193
Merged
Merged
Conversation
Worlds stores current state: updates delete and insert quads, and no history, timestamp or per-quad provenance is kept. Reword every Worlds claim of an append-only or chronological ledger, immutable or per-quad provenance, and queryable past states to what is true, and drop the "When Worlds fits" bullets that only sold history. Claims that describe other products (Graphiti's bi-temporal edges, Kafka's logs) stay. update.mdx also called SPARQL on the data plane read-only; it accepts SPARQL UPDATE, which requires data:write (wazootech/worlds-api#139). Fixes #191 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
History is not retained yet; point to the planned change log, which is the part that will be append-only (wazootech/worlds-sdk-ts#221). The world's current state stays mutable. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
EthanThatOneKid
added a commit
that referenced
this pull request
Oct 19, 2026
* docs: stop saying Worlds validates writes with SHACL No Worlds code runs SHACL: the hosted write paths (import and SPARQL UPDATE) apply quads without validating them. Validation runs before import, in the Wiki CLI or CI. Reword the comparison and guide claims that Worlds enforces or provides SHACL validation, and note in update.mdx that validation on write is planned (wazootech/worlds-sdk-ts#151). Pages crediting the Wiki CLI stay. Also removes three per-quad provenance claims the append-only pass (#193) missed because they were worded differently. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: drop schema-checked claim; SHACL check is the caller's step in resolution tables Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Fixes #191. The docs described Worlds as an append-only, chronological ledger with immutable, per-quad provenance and queryable past states. In fact a world stores current state: updates delete and insert quads, and the
quadstable has no timestamp, version or provenance column (wazootech/worlds-sdk-ts#221).worlds/update.mdx,worlds/index.mdx,glossary.mdx: now say a world holds current state, a deleted fact is not retained, and you record history or provenance as facts (for example, a named graph per source).update.mdxalso called SPARQL on the data plane read-only, but it accepts SPARQL UPDATE, which now requiresdata:write.comparisons/*(35 pages):guides/company-brain,entity-resolution,neurosymbolic: The entity-resolution guide said a retracted resolution "remains in the chronological ledger". It now says retracted facts are removed, and to record decisions as their own timestamped items if you need their history. The neurosymbolic table was a row-shifted copy of the entity-resolution table; it now matches that table.w_<ULID>ID" (IDs are immutable).guides/verifiable-audit.mdxdoesn't exist, so there was nothing to hold.Restore the history claims when the change log in worlds-sdk-ts#221 ships.
Merge order
update.mdxnow says SPARQL UPDATE requiresdata:write. That becomes true only when wazootech/worlds-api#139 is merged and deployed, so merge that first.Checks
pnpm run precommitpasses (format check plus Mintlify build validation), andmintlify broken-linksreports no broken links. I didn't render the pages in a local preview. No code examples changed.Tracker: wazootech/workspace#7.
🤖 Generated with Claude Code