dexio

Review what agents recently wrote to an LLM wiki: read each change as a diff, accept, fix or revert it with a note, promote drafts that pass, and send a person a short digest of what changed and what needs their call. Use daily or weekly on a wiki that agents write to, when drafts are waiting for approval, or after a burst of agent writes such as a large ingest.

Rules for an LLM wiki that several agents, machines or people write to: read before writing, detect concurrent edits, prefer small edits to rewrites, attribute every change with a note, derive the index and log instead of hand-editing shared files, and keep scoped content where only the right readers see it. Use when more than one agent or person maintains the same wiki, or when setting up a wiki for a team or an agent fleet.

Fact-check an LLM wiki against its own sources: pick the pages where an error would do the most harm, pull out the checkable claims, open each cited source and mark every claim supported, outdated, unsupported, unsourced or unreachable, then correct the page and every page that copied the claim. Use on a schedule, before a decision relies on a page, after a large ingest, or when a page's claims are in doubt.

Read an LLM wiki before working in it or answering from it: the schema page, the catalog of page descriptions, recent changes, then a targeted search and the canonical page for the topic. Use at the start of any task that will read or change a shared markdown wiki, and before asking a person to repeat context the wiki may already hold.

Start a new LLM wiki or bring an existing folder of notes or Obsidian vault under maintenance: write the SCHEMA page that tells every agent the wiki's domain, folder layout, page types, frontmatter, tags and thresholds, and point each agent's instructions file at it. Use when creating a knowledge base that agents will maintain, when a wiki has no schema page, or when agents keep writing pages in inconsistent shapes.

Restructure an LLM wiki without breaking it: split oversized pages into focused linked pages, merge duplicate pages, rename or move pages, and archive superseded ones, rewriting every inbound link and confirming zero broken links afterwards. Use when a page passes about 200 lines, when two pages cover the same topic, when the folder layout changes, or when a page is superseded.

Answer a question from an LLM wiki: find and read the relevant pages, answer with the page paths you relied on, check anything mutable at its original source, say plainly what the wiki does not cover, and file substantial answers back as query pages so the research compounds. Use when a person asks something the wiki may cover, or after an answer took real research.

File a decision, finding or fact into an LLM wiki the right way: find the page that already covers it, make the smallest edit that records it, keep frontmatter and dates current, link it to its neighbors, cite where it came from, and leave a change note. Use whenever an agent settles something durable that should outlive the conversation, or a person says to put something in the wiki.

Compile a source (article, paper, transcript, meeting notes, doc, dataset) into an LLM wiki with provenance: keep an immutable raw copy with a hash, update every existing page the source touches instead of writing one summary page, cite the source at each claim, and label how far each claim can be trusted. Use when adding a new source to a wiki or when asked to read something and add it to the wiki.

Handle contradictions and outdated claims in an LLM wiki without silently overwriting: compare dates, provenance and the current system of record, replace only when one side is clearly authoritative, otherwise keep both claims side by side, mark the page contested or lower its confidence, and escalate material conflicts to a person. Use when a new source disagrees with a page, when two pages disagree, or when a fact on a page may no longer be true.