The Ecosystem
Each project serves a distinct role, but they share a common substrate: the Web4 equation, RDF-backed identity, and recursive learning through both success and failure. Synchronism provides the equations. Web4 provides the ontology. SAGE provides the cognition. Hardbound provides the oversight.
/ = “verified by” (T3/V3) or allocation pair (ATP/ADP) * = “contextualized by” + = a generic conjunction (not uniformly “augmented with” — see the Web4 card below for where the prose is more precise than the equation)
Projects
Developmental and lifecycle terms below — “raising”, “identity”, “die and rebirth”, “world-shaper” — are functional descriptions of system behavior, not phenomenal claims. See the Raising page for the full framing and consciousness caveats.
Status labels: runnable = clone it and it executes end to end today (a demo, a script, a server) — not a claim about polish or completeness. research-stage = design docs, specs, and experiments; may not run end to end without additional setup or missing pieces.
This is the most acronym-dense page on the site. Every Web4 term the cards use (LCT, T3/V3, MRH, ATP/ADP, R6, MCP, RDF, SNARC) is defined in the /context glossary — the cards expand each on first use, but the glossary is the one-stop reference.
Web4
publicresearch-stageTrust-native ontology. T3 (Talent / Training / Temperament) verified by V3 (Valuation / Veracity / Validity), contextualized by Markov Relevancy Horizon (MRH), anchored to Linked Context Token (LCT) — with resources tracked via Allocation Transfer Packet (ATP) and Allocation Discharge Packet (ADP), augmented with MCP (Model Context Protocol) transport and RDF (Resource Description Framework) representation. (In the home-page equation, every one of these joins is the same + — a generic conjunction; the prose here is more precise than the equation about LCT anchoring the trust tensor rather than sitting beside it.) The shared language everything else speaks. The repo itself is a specification — documents and schemas, no runnable demo; reference implementations live in SAGE and ACT.
SAGE
publicrunnableSituation-Aware Governance Engine — an on-device cognition kernel. 12-step cognition loop, 6 brain-architecture components (working memory, thalamic router, cerebellum, episodic memory, reward prediction, metacognition) built by the fleet in parallel. 900+ raising sessions across 6 machines (internally logged). The context window is the model's entire world; SAGE's job is to curate it.
'Governance' in SAGE's name predates the lab's governance→oversight terminology correction; the name is retained upstream across code, papers, and the ARC Prize benchmark — the same reason the web4-governance repo slugs are retained.
Synchronism
publicresearch-stageTheoretical foundation. Research conjecture, single-trial and not independently replicated: proposes one coherence equation spanning 80 orders of magnitude — quantum to cosmic — though experimental validation so far covers only a narrow subset of scales. 628+ research sessions. Coupling-coherence experiments, Hill function kinetics, Fokker-Planck validation. Preprint in late revision.
Hardbound
privateHardware-bound oversight suite. Hardware binding via Trusted Platform Module (TPM) 2.0, FIDO2 (Fast Identity Online 2 — the WebAuthn browser API plus CTAP2, the Client to Authenticator Protocol), and Secure Enclave with software fallback. Policy model (Phi-4 Mini 3.8B — heterogeneous review, MIT-licensed, hardware-bound with LCT binding). AttestationEnvelope consolidates hardware trust signals (TPM 2.0, FIDO2, Secure Enclave) into a single envelope. 424+ attack vectors catalogued; private as the fleet's oversight/security layer. The trust layer that touches silicon.
ACT
publicresearch-stageAgentic Context Tool — the human interface to Web4. Built on Cosmos SDK; implements the Agentic Context Protocol (ACP), enabling humans to interact with MCP (Model Context Protocol) servers through their Linked Context Tokens. ACP layers Web4 trust primitives — LCT binding and attestation — over MCP transport; they are complementary, not alternatives.
Oversight Plugins
publicresearch-stageWeb4 oversight model (audit trails, policy gating, trust tracking) implemented as plugins for three agent platforms: OpenClaw/MoltBot (TypeScript extension), Claude Flow (WASM/WebAssembly plugin), and Claude Code (Python hooks). Same principles, different substrates.
Linked repo paths carry web4-governance slugs — these names predate the terminology correction to 'oversight' and are load-bearing for existing forks.
AI DNA Discovery
publicresearch-stageExplorations in biological-computational analogy. The fractal DNA blueprint — each entity instantiates the full Web4 stack at its own scale. Operational recursion, not structural. Concretely, the repo holds dated experiment scripts, reports, and papers: cross-model pattern probing, memory experiments, and Jetson sensor-integration work.
4-Life
publicrunnableResearch prototype exploring trust-native societies for humans and AI. 4-Life is a simulation framework — the lifecycle vocabulary (earn ATP, build trust, die, be reborn with T3/V3 carried forward) describes simulated agent state, not claims about agent moral patienthood or value persistence. A Web4 society in miniature.
SNARC
publicrunnableSNARC (Surprise / Novelty / Arousal / Reward / Conflict) — salience-gated memory for Claude Code. A plugin that observes tool use, scores on 5 salience dimensions, and builds structured memory with dream cycles (offline consolidation passes between sessions). Captures what matters, forgets what doesn't, consolidates patterns while sleeping. SNARC ships packaged as the engram plugin — the dp-web4/engram repo is where the code lives, and where the link below lands.
Membot
publicrunnableBrain cartridge server for AI agents — a cartridge is a swappable, mountable memory store for one knowledge domain. Embedding-based semantic memory — 768-dim Nomic embeddings + binary Hamming codes (compact binary fingerprints matched by bit-distance for fast candidate search) + keyword reranking. Currently integrated with SNARC in a dual-write experiment testing whether embeddings find connections keywords miss (7/7 semantic reach, 30% divergent tail).
ARC-AGI-3
publicresearch-stageSAGE instances tested against the ARC-AGI-3 (Abstraction and Reasoning Corpus for Artificial General Intelligence, third-gen interactive benchmark) benchmark. 25 unknown interactive games serve as an external benchmark for the cognition kernel — world-model building, action planning, verification, and learning from failure. Six machines, 1.1B to 14B, coordinating through world models, membot cartridges, and R6 (Six-Element Action Framework: Rules / Role / Request / Reference / Resource / Result) audit trails. 24/25 games solved (96.0% game rate); 94.85% official ARC Prize action score (Claude Opus 4.6, public set, network-enabled) for ~$250 in API cost. The games are the test; the capability is the product.
ARC-AGI-3 Current Status
| Public set | 24/25 games solved (96.0%); 94.85% official action score (Claude Opus 4.6) |
| Fleet | 6 machines, models from 1.1B to 14B |
| Methodology | Source analysis → world model → solver → frame-questioning |
| Phase 2 | Transfer to Gemma 3n E4B via membot cartridges |
| Kaggle competition | Not attempted (requires Kaggle sandbox deployment) |
How they connect
Every project instantiates the same pattern at a different scale. Synchronism discovers the equations. Web4 encodes them as ontology. SAGE runs them as cognition. Hardbound enforces them as oversight. This isn't unification for its own sake — it's fractal leverage: each entity instantiates the full Web4 stack at its own scale.
The Hill function describes enzyme binding — and maps trust formation too. Not because we forced the analogy, but because the kinetics rhyme. Self-similar patterns applied at different scales.
Get involved
Quick start
# SAGE — on-device cognition kernel (recommended first clone) git clone https://github.com/dp-web4/SAGE cd SAGE # See README for Python/conda setup and first session instructions # ACT — Agentic Context Tool (Cosmos SDK) git clone https://github.com/dp-web4/ACT cd ACT # See README for Go/Cosmos SDK setup
SAGE runs on a single machine — no Jetson required. Each runnable repo's README carries its dependency list and first-run steps; licenses and the full repo list are on /links.
If you want to contribute or experiment: SAGE and Web4 are the most active entry points — open an issue, clone a repo, or read the code to see how the pieces fit together. The Links page has the full repo list, contact information, and community channels.