l2_allowlist.json

{
  "_comment": "L2 source allowlist — runtime-editable config (Aaron 2026-07-03, New Brain fact 35, doc 584). NOT hardcoded: the ladder loads this at runtime, so adding a source is a file edit, never a code change. Reason: useful sources keep appearing that can't be identified up front. Entries are URL patterns (scheme-stripped) with a trust tier (design 'Trust tiers': 1 ground-truth, 3 external-authoritative/official, 4 external-community/never-sufficient-alone). A tier-4-only answer writes back as a DOCUMENT, never a fact, unless corroborated. 'exclude' lists sub-globs that fall off the list. Off-list sources are never silently used or dropped — they go to the candidate queue for Aaron's batched approve/veto.",
  "entries": [
    { "pattern": "dev.epicgames.com/documentation/*", "tier": 3, "note": "UE official docs — re-verify cadence" },
    { "pattern": "dev.epicgames.com/community/*", "tier": 4, "note": "user-submitted" },
    { "pattern": "forums.unrealengine.com/*", "tier": 4, "exclude": ["*/off-topic/*"], "note": "community, corroboration required" },
    { "pattern": "docs.python.org/*", "tier": 3, "note": "Python official docs" },
    { "pattern": "stackoverflow.com/*", "tier": 4, "note": "community, corroboration required" },
    { "pattern": "raw.githubusercontent.com/*", "tier": 1, "note": "library source read directly = ground truth" },
    { "pattern": "github.com/*/issues/*", "tier": 4, "note": "issue threads — community" },
    { "pattern": "github.com/*/discussions/*", "tier": 4, "note": "discussions — community" }
  ]
}