[EthanThatOneKid]

What

Several docs pages say Worlds enforces or provides SHACL validation. It doesn't: no code in worlds-api, worlds-sdk-ts, worlds-cloudflare or worlds-libsql mentions SHACL. Both hosted write paths, import and SPARQL UPDATE, apply quads without validating them. In this family, SHACL validation runs before import, in the Wiki CLI or in CI.

• Comparisons: cocoindex, gbrain, google-okf, llm-wiki (prose, table and the "When Worlds fits" list) and relational-databases no longer say Worlds enforces SHACL. Where validation is part of the story, they say it runs before import.
• Guides: the entity-resolution intro and its "what Worlds provides" table no longer list SHACL (or provenance) as something Worlds provides. They say to validate before import, and the neurosymbolic table matches.
• worlds/update.mdx: "Insert the new, verified triple" becomes "Insert the new triple". A note says Worlds doesn't validate patches yet, to validate before import with the Wiki CLI, and that validation on write is planned in feat: validate every write against a world's SHACL shapes, on by default with a per-world opt-out worlds-sdk-ts#151. That plan is on by default with a per-world opt-out, as the owner decided.
• Left alone: pages that credit the Wiki CLI with SHACL validation (vault-ld, llm-wiki coexistence, company-brain, projects/wiki), since those are accurate. "Verified" in the core Worlds pages also stays, because worlds/index.mdx defines it as a SPARQL ASK check.

Also fixes three per-quad provenance claims that #193 missed because they were worded differently (document-databases, graphiti, llm-wiki table).

Restore the write-time claims when #151 ships.

Checks

pnpm run precommit (format check plus Mintlify build validation) passes, and mintlify broken-links finds none. I didn't preview the pages locally.

🤖 Generated with Claude Code