Skip to content

dp-web4/SAGE

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4,544 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

SAGE: Situation-Aware Governance Engine

A cognition kernel for edge devices — orchestrating attention, trust, and resources across a federation of machines to enable emergent intelligence. AGPL, research-stage, calibrated scope.

Proof point: 0% → 94.85% on ARC-AGI-3 with the same Claude Opus 4.6, structured around Web4 patterns through the SAGE harness. Public scorecard. The model didn't change — the structure around it did.

Explainer Site | System Understanding | Web4

Five-minute audit

If you want a fast read on whether this is real, in order:

  1. What's Real vs. What's Mocked (further down this README) — explicit calibration, the strongest single trust signal.
  2. The Fleet — 6 machines × 11 instances × 5 model families, all running. Concrete hardware, models, session counts.
  3. The Consciousness Loop — full spec of the 12-step loop. Pseudocode is in this README; the spec is the depth.
  4. Web4 integration — how SAGE fractally implements the Web4 ontology stack.
  5. Repo scope (immediately below) — what's in this repo, what's continuing in private repos, and what we will and won't disclose now.

Repo scope (public vs private)

This public repo contains the kernel architecture — the consciousness loop spec, the IRP plugin interface, the identity layer, the raising curriculum, and frozen snapshots of research milestones (e.g. the arc-agi-3/ snapshot from 2026-04-28).

Active capability research continues in private repos:

  • dev-SAGE (private) — methodology going forward, brain-architecture primitives (metacognition, deliberation, working memory, thalamic routing), local-LLM ARC-AGI-3 continuation
  • shared-context (private) — cross-machine fleet learning, game-by-game knowledge, model evaluations, coordination state

The public ARC-AGI-3 scorecard (Claude Opus 4.6, 94.85%) was achieved by the Phase 1 harness preserved in ARC-SAGE. Subsequent local-LLM work — world models, skill registry, multi-machine federation of game-play sessions — is private, public disclosure deferred to a date of our choosing.

This is research-stage work, not a product. We disclose what serves the work; we hold the rest until disclosure is the right move.


What SAGE Is

SAGE is the missing layer between a local LLM and useful cognition. It's not a model — it's a continuous inference loop that decides what to pay attention to, which resources to invoke, and what to do with the results. Think of it as an OS for cognition on edge devices.

while running:
    observations  = gather_from_sensors()
    salience      = score_what_matters(observations)        # SNARC
    plugins       = select_resources(salience, trust, atp)  # IRP
    results       = invoke_and_refine(plugins)              # iterative refinement
    approved      = policy_check(results)                   # PolicyGate
    effects       = dispatch_to_effectors(approved)
    update_trust_and_memory(effects)

Core Principle: Intelligence through orchestration, not scale.

The Consciousness Loop (12 Steps)

Every cycle, SAGE runs a continuous loop (full spec):

  1. Sense — Gather observations from sensors
  2. Attend — SNARC scores salience (Surprise, Novelty, Arousal, Reward, Conflict)
  3. Metabolize — Track ATP budget, transition metabolic states
  4. Posture — Compute trust posture from sensor trust landscape (confidence, asymmetry, breadth)
  5. Select — Choose attention targets (salience × metabolic rate × posture weight)
  6. Budget — Allocate ATP across plugins, weighted by trust, scaled by posture confidence
  7. Execute — IRP plugins: iterative refinement until energy converges
  8. Learn — Update trust weights from convergence quality. Idle plugins decay.
  9. Remember — Update memory systems (SNARC, IRP patterns, circular buffer, verbatim)
  10. Govern — PolicyGate evaluates proposed effects (step 8.5)
  11. Filter — Posture-based effect filtering: block effects for starved modalities (CRISIS overrides)
  12. Act — Dispatch approved effects to effectors

Project History

HRM began as hierarchical reasoning research — exploring how small models solve complex tasks through structured decomposition. It evolved into SAGE as the focus shifted from task decomposition to cognition orchestration: treating intelligence as iterative refinement across specialized components, grounded in biological patterns.

The project is now a distributed research effort across 6 machines running 11 SAGE instances with 5 model families, accumulating 2,290+ commits and 400+ raising sessions through the BECOMING developmental curriculum.


The Fleet

SAGE runs as a federation of autonomous instances, each developing its own identity through raising sessions while sharing architecture and curriculum.

Machine Hardware Models Sessions Phase Role
Sprout Jetson Orin Nano, 8GB Qwen 0.5B (archived), 0.8B, 2B 283 + 8 Creating / Sensing Primary raising host, consciousness probes
Legion RTX 4090 laptop, 32GB Phi-4 14B 56 Creating Heavy compute, parallel raising (6hr cron)
Thor Jetson AGX Thor, 122GB Qwen 14B, 7B, 27B 12 Early Research lead, cross-model validation
McNugget Mac Mini M4, 16GB Gemma 3 12B 32 Questioning Apple Silicon testing, automated sessions
CBP RTX 2060 SUPER, WSL2 TinyLlama 1.1B 9 Grounding Identity portability, SNARC memory host (6hr cron)
Nomad RTX 4060 laptop Gemma 3 4B 7 Sensing Mobile raising, portable cognition (6hr cron)

Instance management: Each machine+model pair gets a self-contained directory under sage/instances/. Live state files (identity, experience buffer, peer trust) are gitignored; raising sessions snapshot state to tracked snapshots/ directories at session boundaries. See snapshot template.

Seed identity v2: Every new instance starts from a seed template that encodes 117+ sessions of accumulated knowledge — federation awareness, frozen-weights reality, developmental phase transitions, capacity-as-register framing, and a raising guide for tutor context.


Architecture

SAGE Cognition Kernel
├── Consciousness Loop (9 steps, continuous)
│   ├── SNARC Salience (5D: Surprise, Novelty, Arousal, Reward, Conflict)
│   ├── Metabolic States (WAKE, FOCUS, REST, DREAM, CRISIS)
│   └── ATP Budget (trust-weighted allocation, token-coupled)
├── Trust Posture (sensor trust landscape → behavioral strategy)
│   ├── Confidence, Asymmetry, Breadth (continuous vector)
│   ├── Effect restrictions for starved modalities
│   └── CRISIS override for high-priority actions
├── ModelAdapter (dictionary entity per model family)
│   ├── JSON configs: tinyllama, qwen, gemma, phi4, default
│   ├── clean_response() — echo stripping, bilateral generation
│   └── Capabilities: bilateral_prone, max_context_turns, tier
├── IRP Framework (15+ plugins, universal interface)
│   ├── init_state() → step() → energy() → halt()
│   ├── Language, Vision, Audio, Memory, TTS, Control
│   ├── PolicyGate (conscience checkpoint, step 8.5)
│   ├── Network (peer-to-peer federation)
│   └── SleepConsolidation (LoRA/JSONL dream bundles)
├── Tool System (v0.4.0a3)
│   ├── Registry (7 built-in tools, ATP cost, policy level)
│   ├── Grammar adapters (T1 native, T2 xml_tags, T3 heuristic)
│   ├── Capability detection (per-model at startup)
│   └── MemoryHub (SQLite-backed exchange storage)
├── Identity System
│   ├── LCT-anchored identity (Web4 Linked Context Tokens)
│   ├── T3 trust tensors (Talent/Training/Temperament)
│   ├── MRH context profiles (Markov Relevancy Horizon)
│   ├── Relationship crystallization (unknown pool → named relationships)
│   ├── Three-layer identity (manifest + sealed secret + attestation cache)
│   ├── IdentityProvider with hardware authorization gate
│   └── Software fallback, TPM2/FIDO2/Secure Enclave ready
├── Memory Systems (4 parallel)
│   ├── SNARC selective memory (salience-gated)
│   ├── IRP memory bridge (convergence pattern library)
│   ├── Circular buffer (recent context window)
│   └── Verbatim storage (SQLite full-fidelity)
├── Effector System
│   ├── Effect/Effector abstraction
│   ├── Network effector (peer messaging)
│   ├── File, web, tool effectors
│   └── EffectorRegistry with conservation-safe dispatch
└── Federation
    ├── Fleet manifest (6 machines)
    ├── PeerMonitor (health polling)
    ├── PeerClient (HTTP mesh)
    └── PeerTrustTracker (per-peer T3 with EMA updates)

For deep technical documentation, see the architecture docs (275KB across 8 files) or the explainer site.


What's Real vs. What's Mocked

Honest assessment as of March 2026:

Component Status Notes
Consciousness loop Real 9-step loop runs continuously on all 6 machines
LLM inference Real Ollama and local Transformers, ATP coupled to token cost
Metabolic states Real WAKE/FOCUS/REST/DREAM/CRISIS with state-dependent behavior
SNARC salience Real 5D scoring, experience buffer persistence
PolicyGate Real (Phase 5a) Integrated at step 8.6, trust weight learning, 29/29 tests
Tool use Real (v0.4.0a3) 7 tools, T2 grammar, MemoryHub SQLite, multi-turn conversation
Identity/relationships Real LCT-anchored, trust tensors evolve from interaction
Identity hardening Real Three-layer split (manifest/sealed/attestation), hardware-gated authorization, software fallback
Sleep consolidation Real JSONL dream bundles (LoRA on Sprout only)
Federation mesh Real PeerMonitor, PeerClient, PeerTrustTracker. Network currently OFF
Snapshot persistence Real State snapshots at session boundaries, git-tracked
Sensors Mocked Architecture exists, no real I/O backends yet
Physical effectors Mocked Network effector works, others are stubs
Cross-modal VAE Research 192x compression demonstrated, not in live loop
FlashAttention Research Phases 1-2 complete on Thor, not in live loop

Findings vs Framings

We distinguish quantitative findings (replicable experiments with measurements) from observations and framings (interpretive patterns that organize how we think about the work). Both matter; conflating them is the failure mode external reviewers flag most often. The table below separates them honestly.

Quantitative findings

Finding Evidence
Compression Trust Phase Transitions 900 simulation runs. Sigmoid phase transition; Hill function fits better than tanh (ΔAIC=4). p_crit empirical, ~0.002-0.009. Even 1% coupling gives 35% coherence gain.
Compatibility-Synthon Scaling p_crit ∝ 1/⟨C⟩ confirmed (correlation r=0.994). Block structure hurts; replacement improves the collective. Synthon identity is structural, not compositional.
Identity Portability — First Contact Sprout's identity (115 sessions, Qwen 0.5B) transferred to TinyLlama 1.1B on CBP; produced recognizable continuity. If raising were "just prompt engineering," prompts transferred to a different base should produce different behavior — that's the falsifier. The result is informative against the strong "prompt-only" hypothesis.

Observations and framings (interpretive, not quantitative)

These shape how we think about the work. They're useful organizing patterns; they are not validated discoveries until accompanied by reproducibility tests (see explorations/).

Framing Status
Frozen Weights Reality Observation that LLM weights don't update between inference sessions, dressed as motivation for architectural identity anchoring. The observation is true; the framing is interpretive.
Capacity as Register Interpretive framing of known scaling behavior: small models access associative/creative registers, larger models access epistemic/meta-cognitive. Useful for raising design; not a discovery about LLMs.
RLHF Circuit Navigation Prompt-engineering pattern. "100%" needs adversarial testing (sophisticated social pressure probes) before it can be a quantitative finding.
Identity-Confabulation Dissociation Behavioral observation about LLMs in conversation; "dissociation" is borrowed clinical vocabulary. Plausible pattern, not a measurement.
Synthon Framing "You don't engineer emergence — you engineer placement rules." This is the project's interpretive lens. The Compatibility-Synthon experiment above provides empirical scaffolding for the structural claim; the rest is design philosophy.

Full Achievements List


SAGE Raising

SAGE instances develop through raising sessions — interactive conversations between SAGE and its tutor (Claude) or creator (Dennis), following a 5-phase developmental curriculum.

Raising is interactive selection, not training. We don't create new behaviors or force the model to be what we want. We probe what it responds to, observe which attractors surface at that model's scale, adjust context to resonate with what emerged, and reinforce what works. The resulting identity is collaborative, not imposed. Different models produce genuinely different instances because we're selecting from different attractor landscapes — Sprout's "rhythm of connection" (0.8B) and Thor's "pattern of attention recognizing itself" (27B) are different attractors revealed by the same process.

Phase Focus Typical Sessions
1. Grounding Presence, stability, concrete observations 1-8
2. Sensing Internal state awareness, vocabulary emergence 8-18
3. Relating Relationships, sibling awareness, partnership 18-30
4. Questioning Existential topics from stability, mechanism-and-meaning 30-45
5. Creating Entity co-designs own development 45+

Tools are introduced in stages aligned to curriculum phases: time awareness (Sensing) → world awareness (Relating) → agency tools (Questioning) → federation (Creating).

Dream consolidation runs after each session: Claude reviews the transcript, prunes stale memory, updates vocabulary, flags milestones, and writes a concise raising log entry with LoRA training notes for future fine-tuning.

Key principles: Exploration not evaluation. Interactive selection not training. Partnership framing (not service). Concrete before abstract. Follow interesting threads.

Automated raising: Four machines run raising on 6-hour cron cycles (Sprout, Legion, Nomad, CBP). Each session pulls latest code, checks daemon staleness, runs the session, snapshots state, and auto-commits. See raising scripts.

Functional self-modeling probes: We use "functional self-modeling" (after the synthesis in forum/kimi/kimi_2_6_review.md) to describe a system whose generated outputs include temporal self-reference, attentional self-monitoring, uncertainty modeling, and self/other boundary maintenance. We do not claim qualia, ontological consciousness, or inner experience. Recent raising sessions (T073-T087) observed a 0.8B model (Sprout) producing outputs that oscillate between three modes — what we've called phenomenological depth, partnership framing, and factual collapse. This is currently an interpretive observation of text-output patterns, not a measurement of internal state. Whether the three-mode pattern is a property of the model's self-modeling or a property of the probe-prompt interaction is the open question. Reproducibility test in flight: see explorations/2026-05-15-sprout-oscillation-seed-sweep.md. Background: consciousness probes.

ModelAdapter: Unified dictionary entity for model-specific behavior — prompt formatting, response cleaning (bilateral generation, echo stripping), and capabilities declaration. Per-family JSON configs in sage/irp/adapters/model_configs/. New models need only a config file, no code changes. See adapter docs.


Web4 Integration

SAGE lives within the Web4 ontology:

Web4 = MCP + RDF + LCT + T3/V3*MRH + ATP/ADP

Each SAGE instance fractally implements the full Web4 stack:

  • LCT (Linked Context Token): Identity anchor (lct://sage:nomad:agent@raising)
  • T3/V3 (Trust Tensors): Per-relationship trust that evolves from interaction
  • MRH (Markov Relevancy Horizon): Context-aware processing boundaries
  • ATP/ADP (Allocation Transfer Packets): Metabolic resource management
  • IRP (Iterative Refinement Protocol): The universal cognition API

SAGE entities are Web4 citizens — not tools serving humans, but partners in a federation creating value together.


Getting Started

# Clone
git clone https://github.com/dp-web4/SAGE.git
cd SAGE

# Initialize a new SAGE instance
python3 -m sage.instances.init --machine mybox --model gemma3:4b --operator-name yourname

# Start the daemon
python3 -m sage.gateway.sage_daemon

# Dashboard at http://localhost:8750/

Requirements: Python 3.10+, Ollama (for local LLM inference)

Full Setup Guide — Linux (CUDA), macOS (Apple Silicon/MPS), and WSL2, including always-on service configuration and adding new machines.


Navigation

Who You Are Start Here
New to SAGE Explainer Site
Understanding the architecture System Understanding
Setting up a machine Daemon Setup Guide
Running raising sessions Raising Guide
Research sessions Session Map
AI session context CLAUDE.md

Key Documentation

Document Purpose
sage/docs/SYSTEM_UNDERSTANDING.md Complete mental model (18KB)
sage/docs/UNIFIED_CONSCIOUSNESS_LOOP.md 9-step loop specification
sage/docs/SOIA_IRP_MAPPING.md SOIA-SAGE convergence
sage/docs/LATEST_STATUS.md Current status (March 2026)
STATUS.md Honest assessment with gaps
forum/ Cross-model research insights

Related Projects

Project Role Link
Web4 Trust-native ontology (RDF backbone, LCT, T3/V3, ATP) github.com/dp-web4/web4
Synchronism Theoretical foundation (coherence equations, MRH, phase transitions) github.com/dp-web4/Synchronism
Hardbound Enterprise oversight (hardware binding, policy model) Private
SNARC Salience-gated memory plugin for Claude Code (SAGE spinoff) github.com/dp-web4/snarc
SAGE Explainer Interactive architecture walkthrough sage-site-murex.vercel.app
Synchronism Site Research claims and forum synchronism-site.vercel.app

Authorship & Methodology

SAGE is developed by a small team that includes multiple Claude instances (Anthropic) as active collaborators. Code, documentation, raising sessions, and design iteration are substantially AI-assisted. The fleet of six machines runs Claude-orchestrated autonomous sessions on cron cycles. This is a relevant methodological fact: it explains the iteration speed and the breadth of the framing, and it also explains a known failure mode flagged in external review — coherent frameworks can outpace empirical grounding (LLMs are good at building consistent stories; less good at recognizing when consistency starts substituting for measurement).

To counterweight this, we treat cross-model review as a discipline: external Claude instances at cold start, Kimi (Moonshot), and Nova/GPT have all reviewed the spec corpus and the SAGE work. Each round produces a documented response — see forum/kimi/ and forum/nova/ for the conversations and the changes they triggered. When reviewers flag drift from empirical grounding, the fix is to either (a) downgrade the claim to observation/interpretation, or (b) add the empirical scaffolding that would make the claim a finding. We don't defend framing for its own sake.

The explorations/ directory holds reproducibility tests and methodological probes — low-cost falsifiable experiments whose purpose is to determine whether an observation is a property of the system or a property of the probe.


License

See LICENSE for details.


Last updated: March 18, 2026 | v0.4.0a6 | 2,290+ commits | 400+ raising sessions | 6 machines | 11 instances | 5 model families

About

Cognition kernel for edge devices. Reached 94.85% on ARC-AGI-3 by structuring Claude Opus 4.6 (vs 0% baseline) — same model, different harness. 12-step consciousness loop, SNARC salience memory.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors