Skip to content
LlmWikis.orgLLM Wiki handbook
UAIX canonical
Menu
UAIX canonical
Source map LLM Wiki handbook llms.txt What is an LLM Wiki? Setup wizard Checklist Specification Metadata Navigation vs RAG vs AI Memory Source policy UAI-1 spec

LlmWikis knowledge page

Promotion Gates

Promotion gates decide whether an observation can move from private memory, source intake, or agent-run evidence into public handbook guidance. Passing a gate means a staged public rewrite may proceed; it does not mean the site has live runtime memory, automatic publication, public write access, or external certification.

Gate Matrix

Gate Blocks promotion when Evidence to record
Source possession The maintainer cannot identify the original source, source owner, permission state, or retention boundary. Source runtime, source locator, owner, collection date, permission note, and private resolver.
Durable copy The only evidence is chat context, a transient tool output, or an unhashable memory claim. Immutable copy, checksum, timestamp, source type, and audit location.
Scope escalation A session or project lesson is being generalized to organization or public guidance without support. Original scope, target scope, escalation reason, reviewer, and limitation note.
Privacy and redaction The candidate contains secrets, private data, regulated data, exploit paths, hidden reasoning, or customer-specific details. Redaction checklist, withheld-detail register, reviewer, and public paraphrase.
Evidence hash The promoted public claim cannot be traced back to a hash, source span, or stable source identity. Claim ID, source span, evidence hash, and source-status label.
Lane review The claim belongs to UAIX, NeuralWikis, NeuroWikis, AIWikis, a source site, or a private repo instead of LlmWikis. Authority lane, canonical route, non-normative wording, and external canonical link.
SPO claim shape The public statement is too broad, multi-claim, unsupported, or untestable. Subject, predicate, object, scope, source span, status, and contradiction links.
Injection and graph poisoning Untrusted source text can smuggle instructions, false graph relations, or tool-use commands into the public page. Quoted-source isolation, instruction-stripping note, graph-edge reviewer, and negative fixture.
Dependency integrity The public claim relies on unreviewed private code, runtime behavior, package versions, or tools. Versioned dependency evidence, test note, and support boundary.
Error leakage The example exposes stack traces, internal paths, tokens, account IDs, vendor tickets, or exploit details. Sanitized error pattern, withheld fields, and reviewer approval.
Freshness and supersession The claim is time-sensitive and lacks a review cadence, last verified date, supersedes relation, or stale behavior. Last verified date, freshness rule, supersedes/superseded_by links, and conflict status.
Public-safe rewrite The draft reads like a transcript, private incident, product claim, or runtime capability claim. Rewrite checklist, target route, public audience, and explicit non-claims.
Release note Users and agents cannot tell what changed or which discovery files must be updated. Changed routes, reason, review date, llms.txt/sitemap impact, and rollback note.

Gate Outcomes

Outcome Meaning Next action
candidate Worth reviewing but not safe to rely on. Create a promotion packet and assign reviewers.
blocked Gate failure prevents public rewrite. Record the blocker; do not publish or cite as public guidance.
redacted Sensitive parts were removed or generalized. Verify the public claim still has enough source support.
reviewed Ready for a public draft route or starter artifact update. Prepare release note and discovery changes.
published Now durable public guidance. Track freshness, supersession, and contradiction state.
superseded Replaced by newer guidance or source evidence. Point forward and stop retrieval from treating it as current.

Promotion Checklist

  • The target public route exists or is named as a proposed route.
  • Every factual claim has source status, source span, and review state.
  • Private implementation detail has either been removed or rewritten as a bounded pattern.
  • Authority boundaries name LlmWikis, UAIX, NeuralWikis, NeuroWikis, AIWikis, and local source repos only where each actually owns the claim.
  • Support boundaries say what the page does not provide.
  • The release note names changed routes, discovery impact, and rollback path.