metaenrichmenttiersautomationpriorityUpdated 2026-07-01

Enrichment Tiers

tier: 1|2|3 tells agents and automations how aggressively to keep a page current.

Routing

Open this page when creating entity pages, prioritizing source compile work, tuning automations, or deciding whether a stub deserves deeper research. Tiers are priority hints, not quality exemptions: every page still needs enough citations, links, and lead context to be usable.

Enrichment tiers prevent the wiki from spending equal effort on Kevin's core operating context and passing mentions. They are priority hints for source compile, radars, manual research, and entity-page maintenance. Source: AGENTS.md Enrichment Tiers

Tier Definitions

Tier Who / what Effort Examples
1 Kevin, active projects, key collaborators, core tools, core meta protocols Full enrichment on every relevant signal USER, Dedalus, Sigil, Agent Machines, agent-operations-hub
2 Notable people/tools/concepts mentioned repeatedly or strategically useful Update on significant new signals; web/social research when useful collaborators, important tools, philosophy pages
3 Passing mentions or stubs Wiki cross-reference only until they recur minor entities, one-off references

Defaults

  • Existing page without tier: treat as Tier 2.
  • New passing entity: Tier 3.
  • New active project/tool/protocol: Tier 1 or Tier 2 depending on operational importance.
  • Sensitive personal pages: tier can be high for maintenance but should still be used with discretion.

Promotion Rules

Promote when:

  • the entity appears across three or more sources
  • Kevin directly asks about it again
  • it becomes part of an active project or workflow
  • an automation depends on it
  • agents repeatedly search for it

Demote when:

  • the page no longer affects active work
  • the entity was misclassified as important
  • it is retained only for historical reference

Automation Implications

  • source-compile: Tier 1 pages receive proactive updates from new raw sources.
  • radars: Tier 1 gets dedicated monitoring; Tier 2 gets significant-signal updates; Tier 3 is passive.
  • weekly doctor/lint: Tier 3 stubs with repeated mentions should be promoted or merged.
  • generated packs and capsules: Tier 1 pages should appear in relevant pack/capsule sources; use Generated Surface Contract when tier changes affect generated surfaces.

Timeline

Related Pages

Source Compile Automation SetupCapture Ingest ProtocolEntity Identity ProtocolQuality GatesGenerated Surface Contract

1 page links here

Tier Enrichment ModelDecisions