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

Public-Safe Rewrite

A public-safe rewrite turns a private event into a useful public pattern without leaking who, what, where, how to access it, or what private runtime exists. It preserves the lesson and citation posture while removing private identities, privileged paths, and unsupported capability claims.

Rewrite Transform

Private source says Public rewrite should say Reason
A named tenant or repository had a failed memory promotion. A promotion candidate failed the source-possession or durable-copy gate. The reusable lesson is the gate failure, not the tenant identity.
An internal tool accepted duplicate events under one idempotency key. Protected submit routes need deterministic idempotency, replay, and duplicate-disposition records. Public guidance can teach the safety pattern without exposing the tool.
A private prompt, trace, or chain-of-thought showed why an agent acted. The public page should cite observable inputs, outputs, decisions, and checks only. Hidden reasoning and private prompts are not public source material.
A runtime feature exists in a private dogfood lane. LlmWikis documents the review pattern and does not claim public runtime support. Dogfood evidence is not a public product claim.

Rewrite Rules

  • Replace proper nouns, tenant names, user names, repo names, private URLs, and account IDs with role descriptions only when the identity is not necessary.
  • Replace raw traces with observable claim/source-span records, run IDs, checks, and reviewer decisions.
  • Replace private implementation detail with a requirement, anti-pattern, template field, negative fixture, or gate.
  • Replace “we support” language with “the handbook recommends” unless a current public product/service exists and is source-backed.
  • Keep external standards authority at the canonical source. LlmWikis can explain; UAIX defines UAIX standards.
  • Name uncertainty and limitations instead of smoothing over missing evidence.

Public-Safe Rewrite Template

# Public-Safe Rewrite Packet

private_source_pointer: private-audit://...
source_hash: sha256:...
target_public_route: /reference/...
private_lesson:
  summary: "What went wrong or what worked."
  do_not_publish:
    - secrets
    - tenant identity
    - private tool route
    - hidden reasoning
public_pattern:
  claim: "One atomic public lesson."
  source_status: source-linked | source-needed | contradicted
  support_boundary: "What this page does not provide."
  related_routes:
    - /reference/promotion-gates/
review:
  redaction_reviewer: ""
  source_reviewer: ""
  publication_owner: ""
  release_note_required: true

Final Public Copy Tests

  1. Could a reader infer a secret, customer, repository, vendor ticket, or private endpoint from the copy?
  2. Could an agent mistake the page for permission to call a tool, mutate a repo, submit memory, or publish content?
  3. Does every factual claim have source status and a review owner?
  4. Does the page name non-claims before a crawler or agent overreads the guidance?
  5. Does the copy still help a builder after private details are gone?