ProjectsGlossaryARC-AGI-3FleetAutonomyRaisingPrinciplesLinks

Explainer Sites

GitHub

New here? Repo descriptions use Web4 vocabulary (LCT, T3/V3, MRH, MCP, RDF, ATP/ADP). See /context for full definitions.

Hardbound (hardware-bound oversight suite) is internal research — code is not publicly available. Capabilities described on the Projects page.

Contributing

New here? Read /context for the vocabulary, then start with SAGE or ACT — the most accessible entry points for hands-on experimentation.

Quick start

# SAGE — on-device cognition kernel
# Needs: Rust (stable), Ollama, Python 3.10+
git clone https://github.com/dp-web4/SAGE
cd SAGE

# 1. Create your own instance — this is the first real command.
#    It writes sage/instances/mybox/ : identity, state files, experience buffer.
python3 -m sage.instances.init --machine mybox --model gemma3:4b --operator-name yourname

# 2. Build the daemon that runs the 12-step loop.
cd sage-rs && cargo build --release && cd ..

# 3. Start it. Dashboard comes up at http://localhost:8760/
SAGE_MACHINE=mybox SAGE_MODEL=gemma3:4b ./sage-rs/target/release/sage-daemon

# ACT — Agentic Context Tool (Cosmos SDK)
git clone https://github.com/dp-web4/ACT
cd ACT
# See README for Go/Cosmos SDK setup

What you should see after step 3: the daemon logs its instance name and model, then the dashboard at localhost:8760 shows the loop stepping and a metabolic state. If step 1 is the only thing you run, the payoff is the generated instance directory — that directory is the entity; everything raising does, it does to those files. Commands transcribed from the SAGE README's Getting Started section, which is the maintained version if these drift.

SAGE is the recommended starting point — it runs on a single machine, has 1,991 internally logged raising sessions as context (2,065 including HUB; per-machine counts on /fleet, the source of record), and is where most fleet behavior originates. ACT is the right entry if you want the Web4 trust-layer / Cosmos SDK side.

Licenses

ARC-SAGE: MIT-0 (MIT No Attribution; see repo). Gemma 4 Good Submission: Apache 2.0. Other repos: see each repo's LICENSE file — check before forking. Hardbound is internal and not publicly available.

Questions or contributions? Open an issue on any public repo. SAGE and Web4 are the most active issue trackers. The dp-web4 org holds 40 original repos — 21 public, 19 internal — plus 32 forks of external work the lab builds on, 72 repositories in all. (“Original” means not-a-fork; the same denominator is used for the “40” on the home page. Verified against the org on 2026-07-26.) Clone what interests you, experiment, and open a discussion if you want to engage.

There is no CONTRIBUTING guide yet and no stated policy on outside pull requests. Ask in an issue first — that's the on-ramp until a formal policy exists.

For researchers: no papers or preprints are published yet — the Synchronism preprint is in late revision, and the claims on this site (other than the externally scored ARC-AGI-3 result) cite internal session logs that are not yet externally auditable. Redacted log samples and coding criteria are not published at this time; email below to inquire.

Contact