metaqualitycitationsskillsverificationUpdated 2026-07-01

Quality Gates

A wiki or skill change is not done because text exists. It is done when the graph, provenance, routing, and verification all still work.

Quality gates make agent output durable. They prevent the common failure mode where a page looks polished but cannot be trusted, found, or reused. Source: AGENTS.md Writing Standards; conventions-quality

Wiki Write Gates

Gate Required behavior Failure mode caught
Source Every factual claim has inline [Source: ...] or is clearly synthesized from linked pages confident but untraceable claims
Shape Page/section/ledger/generated/redirect choice follows Wiki Brain Operating Model weak stubs and duplicate article-shaped fragments
Filing Page location follows Filing Decision Tree invisible or miscategorized knowledge
Identity Entity duplicates and aliases searched duplicate people/tools/projects
Graph Related pages and inline wikilinks added orphan pages
Backlink Entity pages get meaningful timeline references one-way graph drift
Format Compiled truth and timeline separated where required append-only sludge in current synthesis
Generated Generated packs/source views are regenerated from their owning source per Generated Surface Contract derived files drifting from source
Redirect Retired slugs resolve when pages are folded or renamed broken old retrieval paths
Index build-index run after substantive edits stale _index.md and backlinks
Search qmd update && qmd embed run wiki search misses new knowledge
Log wiki/log.md appended next agent cannot reconstruct the operation

Skill and Config Gates

When changing executable skills, rules, hooks, or routing:

  1. Read the existing skill/rule before editing.
  2. Update the executable source under skills/ or config/.
  3. Update the wiki reference page when the behavior is durable.
  4. Update SKILL-RESOLVER, Active Stack (What to Actually Use), or Capability Routing Map if routing changes.
  5. Run bash scripts/sync-skills.sh --check for skill changes.
  6. Run npm run routing-doctor and npm run trigger-eval when routes/triggers change.

Skill Install Gates

Before installing external skills:

  1. Prefer already installed skills.
  2. Use find-skills when no installed skill matches.
  3. Audit new skills with skill-auditor.
  4. Check source reputation and install count when available.
  5. Add a wiki skill page and resolver route after install.

Review Questions

Before closing, ask:

  • Would a future agent know why this page exists?
  • Can every important claim be traced?
  • Did I update the action surface, not only the storage surface?
  • Did I verify the machine-generated indexes?
  • Did I preserve old retrieval paths if anything moved or merged?
  • Did I leave stale instructions elsewhere?
  • Did I update the source of truth rather than patching a generated projection?

Timeline

Related Pages

Filing Decision TreeWiki Brain Operating ModelWiki Page FormatBacklink Index ProtocolEntity Identity ProtocolGenerated Surface ContractIndex Logging ProtocolSecurity and Review Skills

17 pages link here

Backlink Index ProtocolMetaCapture Ingest ProtocolMetaCitation StandardSOULCompiled Truth TimelineFiling Decision TreeConfig Sync ProtocolMetaEnrichment TiersMetaEntity Identity ProtocolMetaFiling Decision TreeFiling Decision TreeGenerated Surface ContractMetaHow to Update the WikiMetaInbox FilingFiling Decision TreeIndex Logging ProtocolMetaProof-Carrying WorkConceptsTest Before Bulk ProtocolMetaWiki Doctor ContractAgent DocsWiki Lint WorkflowWorkflowsWiki Page FormatMeta