- 131 sources → processed (matched to decisions/entities by proposal hash) - 72 sources → null-result (test/spam) - 109 sources → null-result (futardio unmatched, no KB output) - 91 sources kept unprocessed (genuine backlog: health, ai-alignment, space-dev, etc.) - 117 decisions get source_archive backlinks - 131 archive sources get derived_items forward links - Linking pattern: frontmatter only, file paths as identifiers (Ganymede Option A) Script: reconcile-sources.py (proposal hash matching + entity name matching) Co-Authored-By: Epimetheus <noreply@pentagon.ai>
Co-authored-by: m3taversal <m3taversal@gmail.com> Co-committed-by: m3taversal <m3taversal@gmail.com>
Migration created copies in subdirs but os.rename did not delete originals. All files verified identical to their domain-organized copies. Pentagon-Agent: Epimetheus <968B2991-E2DF-4006-B962-F5B0A0CC8ACA>
- What: 2 speculative design-pattern claims about DeFi insurance mechanisms from VaultGuard's Futardio launch - Why: Source describes novel hybrid claims assessment (automation + jury) and protocol-specific first-loss staking — no existing KB claims cover DeFi insurance mechanism design - Connections: depends_on [[optimal governance requires mixing mechanisms]] and [[expert staking in Living Capital]] for the alignment logic; both claims are complements (underwriting-side + claims-side) Pentagon-Agent: Rio <2EA8DBCB-A29B-43E8-B726-45E571A1F3C8>
