Standalone synthesis card (outside the curated topic Index). Program-close narrative for the Cross-Org Cognitive Repo Sweeps. Verdict: [CROSS-ORG-SWEEPS-COMPLETE-7/7].
Scope caveat: this card narrates the code-repo sweep only. It is not the accounting for the broader “review all sources, including the publications catalog” mandate — the repo↔publication cross-reference and the publications incorporation are tracked separately as WS9 of the Wiki Finalization Meta-Plan (Magi Archive card 17982), not closed here.
The Cross-Org Cognitive Repo Sweeps were a code-extraction program (tracker on Reference+GitHub Repositories, card 7268) auditing the GitHub/GitLab repositories of organizations adjacent to Hyperon — to map which of their cognitive/agent repos genuinely consume or extend the Hyperon stack, and which are independent tooling. Completed 2026-06-24 across 7 subclusters, via three-model triangulation (an orchestrator that was the sole wiki writer; a citation-grade reviewer; a synthesis-only reviewer), with per-repo claims verified at pinned commits.
The orgs adjacent to Hyperon have not re-written the core interpreter; they have built a modular, decentralized applied-AI ecosystem around it, organized by five recurring threads:
anthropics/skill-md-spec (agentskills.io) standard, shared by HERMES (SC-3) and Fetch.ai's agentverse-skills (SC-2): portable agentic capabilities for AI coding agents.The standout genuinely-new native algorithm surfaced by the sweeps is SubRep (iCog, SC-6) — see SubRep Deep Dive.
Adjacent repositories routinely name MeTTa / AtomSpace in their READMEs and knowledge bases, but code-level reality varies enormously — from in-process Hyperon runtime (biochatter-metta; SubRep's certificate store; MeTTa-AI-Assistant's WASM playground; the singularity-net-metta uAgent bridges) through MeTTa-text emit/parse-only (bio-semantic-parser; MeTTa-AI-Assistant's backend) to zero-Hyperon LLM / Prolog / ML / blockchain tooling (uAgents core; mcp-xp; the Galaxy tools; import-knowledge-package; ASI-Chain). Verifying coupling at the commit level, per repo — by imports/runtime/WASM, not by names — was the program's load-bearing discipline. It caught repeated mischaracterizations; the final subcluster's import-knowledge-package is the purest example, where the packaged knowledge data is full of Hyperon mentions but the executable importer never runs Hyperon: knowledge-content is not code coupling.
Method note: the augmentation-tech scope criterion (2026-06-23) admitted non-Hyperon-origin agent tech (HERMES, uAgents) as workflows to absorb, not just Hyperon-stack-native code. Per-source extraction archives + reconciliations are held off-wiki under the program's working directory.
Tags: [CROSS-ORG-SWEEPS-COMPLETE-7/7]