The cognitive kernel for Claude Code.
Quick Start · Architecture · Skills · Agents · Synapses · Pipelines · Docs
Production-Ready Release — Everything is hardened for real-world agent discipline.
- Synapse Engine v2 — Production-hardened async trigger firing with formal decision types (halt/warn/allow)
- All 12 synapses fully operational — metacognition, anti-rationalization, sequential thinking, pattern recognition, security awareness, code quality, completeness, consistency, trust verification, and MCPs
- Wired into pipeline execution — Synapses fire on
pre-executiontriggers; blocking decisions halt pipelines with explicit error messages - CI/pytest now enforced — All 362 tests run on every commit (previously unguarded)
- 3 MCP servers — File-ops (Python), Forge (Python), and skill-router (Rust) for external service integration
- Trust verification enhanced — Contradiction detection now analyzes negations + shared term heuristics
- Metacognition synapse — Full 4-check validator: plan requirement, reasoning depth, reflection markers, confidence calibration
✅ 362 pytest test cases
✅ Test suite protected by CI
✅ All synapses have dedicated tests
✅ .gitignore enforces clean build artifacts
✅ Production checklist complete
All core systems hardened and tested:
- Synapse Engine v2 with async trigger firing
- 362 test suite protected by CI
- All 12 cognitive synapses fully wired and tested
- 3 MCP servers (file-ops, forge, skill-router)
- Trust verification with contradiction detection
- Metacognition synapse: 4-check validator (plan, reasoning, reflection, confidence)
- File-ops Rust daemon with rate limiting + metrics
Status: Production grade. Launch ready.
All core systems hardened and tested:
- Synapse Engine v2 with async trigger firing
- 362 test suite protected by CI
- All 12 cognitive synapses fully wired and tested
- 3 MCP servers (file-ops, forge, skill-router)
- Trust verification with contradiction detection
- Metacognition synapse: 4-check validator (plan, reasoning, reflection, confidence)
- File-ops Rust daemon with rate limiting + metrics
Status: Production grade. Launch ready.
Most AI agent frameworks give you plumbing — tool calling, memory, chains. None of them address the real failure mode: agents that guess, rationalize, and skip steps.
Archon is the first framework that treats agent discipline as a first-class concern. It ships 98 skills as a native Claude Code plugin, but the real value is what happens between skills: cognitive synapses that force structured reasoning, guardrails with Iron Laws agents cannot talk their way out of, and resumable pipelines that recover from failure instead of crashing.
Important
Archon is not another LangChain. It does not manage LLM calls, memory, or tool routing. It manages what agents know (skills), how agents think (synapses), and what agents must never do (guardrails).
git clone https://github.com/SufficientDaikon/archon.git
cd archon
pip install -e .archon init # Initialize Archon for Claude Code
archon doctor # Verify everything works
archon install --all # Deploy all 98 skills
archon install --bundle godot-kit # Just one domain
archon install --skill backend-development # Just one skillRun a full pipeline:
archon pipeline run sdd-pipeline --project ./myappTip
archon doctor validates your environment, checks skill integrity, and reports any manifest issues — run it after every install.
Archon uses a strict 6-layer architecture. Each layer builds on the one below. No shortcuts, no bypasses.
graph TD
RT["🔒 Runtime Contracts<br><sub>Session state · Policy engine · Telemetry · MCP trust</sub>"]
GH["⚙️ Guardrails & Hooks<br><sub>5 lifecycle hooks · Iron Laws · Deviation protocol</sub>"]
PO["🔄 Pipelines & Orchestration<br><sub>8 resumable workflows · Failure recovery · Context curation</sub>"]
SC["🧠 Synapses & Cognition<br><sub>12 cognitive synapses · Structured reasoning · Confidence tagging</sub>"]
AP["🤖 Agents & Personas<br><sub>17 agents · Skill bindings · Handoff contracts · Quality gates</sub>"]
SK["📚 Skills & Knowledge<br><sub>99 skills · 16 bundles · Prompt library · Knowledge sources</sub>"]
RT --> GH --> PO --> SC --> AP --> SK
style RT fill:#1a1a2e,stroke:#00F0FF,color:#e0e0e0
style GH fill:#1a1a2e,stroke:#00F0FF,color:#e0e0e0
style PO fill:#1a1a2e,stroke:#00F0FF,color:#e0e0e0
style SC fill:#1a1a2e,stroke:#00F0FF,color:#e0e0e0
style AP fill:#1a1a2e,stroke:#00F0FF,color:#e0e0e0
style SK fill:#1a1a2e,stroke:#00F0FF,color:#e0e0e0
Directory structure
archon/
├── skills/ 98 skills (SKILL.md + manifest.yaml + resources/)
├── bundles/ 16 domain bundles (bundle.yaml + conflict resolution)
├── agents/ 17 agent definitions (AGENT.md + agent-manifest.yaml)
├── pipelines/ 8 multi-agent workflows (resumable YAML)
├── synapses/ 12 cognitive synapses (SYNAPSE.md + manifest.yaml)
├── hooks/ 5 lifecycle hooks
├── src/ Core engine (session, policy, telemetry, replay)
├── sdk/ Python SDK
├── mcp-servers/ MCP server integrations
├── vscode/ VS Code extension
├── webapp/ Web application
├── schemas/ 15 validation schemas
└── tests/ 513 automated tests
Skills are installed directly into ~/.claude/skills/ and are immediately available to Claude Code sessions. The built-in VS Code extension provides skill browsing, pipeline visualization, and agent card inspection without leaving your editor.
This is what makes Archon different. Synapses don't add knowledge — they shape how agents reason. Core synapses fire automatically. Agents cannot opt out.
flowchart LR
IN([Agent receives task]) --> MC{Metacognition}
MC -->|PLAN ➜ MONITOR ➜ REFLECT| ST{Sequential Thinking}
ST -->|DECOMPOSE ➜ REASON ➜ VALIDATE| AR{Anti-Rationalization}
AR -->|DETECT ➜ CHALLENGE ➜ ENFORCE| SA{Security Awareness}
SA -->|SCAN ➜ FLAG| PR{Pattern Recognition}
PR -->|DETECT ➜ SUGGEST| OUT([Execute with discipline])
style MC fill:#2d1b69,stroke:#c084fc,color:#fff
style ST fill:#2d1b69,stroke:#c084fc,color:#fff
style AR fill:#2d1b69,stroke:#c084fc,color:#fff
style SA fill:#2d1b69,stroke:#c084fc,color:#fff
style PR fill:#2d1b69,stroke:#c084fc,color:#fff
| Synapse | Type | Phases | Purpose |
|---|---|---|---|
| Metacognition | Core | PLAN → MONITOR → REFLECT | Agents plan before acting, tag confidence levels, reflect on outcomes |
| Anti-Rationalization | Core | DETECT → CHALLENGE → ENFORCE | 10 Iron Laws prevent agents from making excuses to skip steps |
| Sequential Thinking | Core | DECOMPOSE → REASON → VALIDATE → SYNTHESIZE | Forces step-by-step decomposition instead of "just do it" |
| Pattern Recognition | Core | DETECT → SUGGEST → APPLY | Surfaces matching skills for detected code/design patterns |
| Security Awareness | Core | SCAN → FLAG | Injects OWASP security checks during every code task |
The 10 Iron Laws of Anti-Rationalization
An agent under Archon's guardrails cannot:
- Skip a required step by claiming "it's obvious"
- Omit tests by saying "the code is simple enough"
- Ignore a failing check by promising to "fix it later"
- Substitute a quick fix for a proper investigation
- Claim something is "out of scope" without citing the spec
- Override a guardrail by asserting expertise
- Merge work that violates a quality gate
- Produce output without tagging its confidence level
- Skip context curation between pipeline phases
- Self-assess as "done" without running the reviewer
Violations trigger the Deviation Protocol: halt → explain → get explicit override or fix.
98 skills organized into 16 domain bundles. Each skill follows a standardized format: SKILL.md (instructions) + manifest.yaml (metadata) + optional resources/ and references/.
All 16 Bundles
Skill anatomy
Every skill follows this structure:
skills/backend-development/
├── SKILL.md # Full instructions the agent follows
├── manifest.yaml # Metadata: name, version, tags, triggers
└── resources/ # Templates, schemas, reference docs
├── api-template.md
└── db-patterns.md
The manifest.yaml declares everything the framework needs:
name: backend-development
version: 1.0.0
description: "Backend API design, database architecture, microservices"
author: tahaa
license: MIT
tags: [backend, api, database, architecture]
triggers:
- pattern: "design.*api"
- pattern: "database.*schema"
priority: P117 agents with formal personas, strict guardrail enforcement, skill bindings, and handoff contracts. Every agent operates under all 12 cognitive synapses.
| Agent | Role | Skills | Specialty |
|---|---|---|---|
spec-writer-agent |
Specification Architect | spec-writer, prompt-architect | Transforms ideas into implementable specs |
implementer-agent |
Implementation Engineer | implementer | Builds from specs with test-driven discipline |
reviewer-agent |
Compliance Reviewer | reviewer | Verifies implementation against spec |
debugger-agent |
Debug Investigator | systematic-debugging | Root-cause analysis, never guess-and-check |
context-curator-agent |
Context Architect | context-curator | Manages context windows between pipeline phases |
dissector-agent |
Codebase Analyst | knowledge-sources | Reverse-engineers codebases into skills |
ux-research-agent |
UX Researcher | ux-research | Personas, journey maps, competitive analysis |
ui-design-agent |
Visual Designer | ui-visual-design, frontend-design | Design systems, component libraries, hero sections |
qa-master-agent |
QA Engineer | e2e-testing, qa-test-planner | Test plans, regression suites, bug reports |
security-reviewer-agent |
Security Auditor | guard-chain, error-handling | OWASP review, threat modeling, secure patterns |
university-professor-agent |
Adaptive Professor | adaptive-teacher, codebase-to-course, research-paper-to-course, pr-to-course | Harvard/MIT-caliber teaching with ADHD-friendly pedagogy and anti-hallucination logic gates |
Note
The university-professor-agent includes 5 anti-hallucination logic gates (Source Verification, Confidence Rating, Numerical Accuracy, Claim Strength, Feynman Gate) that block the agent from ever guessing or fabricating information during teaching.
Agent handoff protocol
Agents don't "call" each other — they hand off through a structured contract:
sequenceDiagram
participant S as Spec Writer
participant CC as Context Curator
participant I as Implementer
participant R as Reviewer
S->>CC: Handoff: spec artifact
Note over CC: Compress context<br>Strip irrelevant files<br>Keep decisions + spec
CC->>I: Handoff: curated context + spec
I->>CC: Handoff: implementation artifact
CC->>R: Handoff: curated context + impl + spec
R-->>I: Fail: compliance issues found
R->>S: Pass: verified implementation
Every handoff includes: artifact type, confidence level, and a manifest of what was included/excluded.
8 resumable multi-agent pipelines. If interrupted mid-execution, they save state and continue from the last completed step. No lost work, no manual restarts.
flowchart LR
subgraph sdd ["SDD Pipeline"]
direction LR
SP[Spec Writer] --> CC1[Context Curator] --> IM[Implementer] --> CC2[Context Curator] --> RV[Reviewer]
end
subgraph ux ["UX Pipeline"]
direction LR
UR[UX Research] --> WF[Wireframe] --> VD[Visual Design] --> DR[Design Review] --> HO[Handoff]
end
style sdd fill:#0e1525,stroke:#6366f1,color:#e0e0e0
style ux fill:#0e1525,stroke:#ff69b4,color:#e0e0e0
| Pipeline | Trigger | Agent Flow |
|---|---|---|
| sdd-pipeline | "build feature X from scratch" | spec → curate → implement → curate → review |
| ux-pipeline | "design feature X" | research → wireframe → visual → review → handoff |
| debug-pipeline | "fix bug X" | debug → curate → implement → test → review |
| skill-factory | "create a new skill for X" | prompt → spec → implement → validate → review |
| full-product | "build product X end-to-end" | ux-pipeline → sdd-pipeline → testing |
| dissect-to-skill | "dissect codebase X into skills" | dissect → diff → specify → implement → validate |
| skill-upgrade | "upgrade skill X" | assess → specify → rewrite → verify |
| batch-sdd-pipeline | "batch process multiple specs" | queue → sdd-pipeline × N → aggregate |
Failure recovery
When a pipeline step fails:
- State is saved — which step, what artifacts were produced, what context was active
- Failure is classified — transient (retry), permanent (escalate), or quality (fix + retry)
- Recovery runs — the failed step re-executes with the failure context injected
- Max 3 retries — after which the pipeline halts and surfaces the exact failure to the operator
archon pipeline resume sdd-pipeline --session abc123Guardrails are not suggestions. They are enforcement mechanisms that agents cannot bypass, disable, or rationalize away.
- Iron Laws
- 10 inviolable rules enforced by the Anti-Rationalization synapse. Violations trigger automatic halt + deviation protocol.
- Lifecycle Hooks
- 5 hooks that fire at key moments: pre-execution, post-execution, pre-handoff, post-handoff, on-failure. Each can block, warn, or transform.
- Confidence Tagging
- Every agent output is tagged with a confidence level. Agents cannot self-assess as HIGH without meeting specific evidence thresholds.
- Deviation Protocol
- When an agent wants to skip a step or override a guardrail: halt → explain deviation → receive explicit override from operator or fix the issue. No silent skips.
- Quality Gates
- Pipeline phases cannot hand off to the next agent until the quality gate passes. Spec must be complete. Implementation must match spec. Review must confirm compliance.
| Guide | Description |
|---|---|
| Getting Started | Installation, setup, first skill |
| Creating Skills | Skill anatomy, SKILL.md authoring, manifest reference |
| Creating Bundles | Domain kits with conflict resolution routing |
| Creating Agents | Personas, skill bindings, guardrails, handoff protocols |
| Creating Pipelines | Multi-agent workflows with branching + failure recovery |
| Creating Synapses | Custom cognitive capabilities |
| Architecture | 6-layer design, data flow, validation schemas |
| Guardrails | Iron Laws, deviation protocol, confidence tagging |
| CLI Guide | Full command reference |
| VS Code Extension | Extension setup, skill browser, pipeline visualization |
| FAQ | Common questions |
All commands
| Command | Description |
|---|---|
archon init |
Initialize Archon for Claude Code |
archon doctor |
Validate environment and skill integrity |
archon install --all |
Install all 98 skills |
archon install --bundle <name> |
Install a domain bundle |
archon install --skill <name> |
Install a single skill |
archon search <query> |
Search skills by name, tag, or domain |
archon info <skill> |
Show skill details and manifest |
archon validate |
Validate all manifests and skill structures |
archon pipeline run <name> |
Execute a multi-agent pipeline |
archon pipeline resume <name> |
Resume an interrupted pipeline |
archon pipeline list |
List available pipelines |
archon admin stats |
Show framework statistics |
archon cards <agent> |
Display an agent's card (capabilities, skills, guardrails) |
| Capability | LangChain | CrewAI | AutoGen | Archon |
|---|---|---|---|---|
| Native Claude Code plugin | — | — | — | ✅ Built for Claude Code |
| VS Code extension | — | — | — | ✅ Skill browser + pipeline |
| Cognitive synapses | — | — | — | ✅ 5 synapses |
| Anti-rationalization | — | — | — | ✅ 10 Iron Laws |
| Resumable pipelines | — | Partial | Partial | ✅ Full state recovery |
| Guardrail enforcement | Partial | Partial | — | ✅ Cannot be bypassed |
| Agent handoff contracts | — | Basic | Basic | ✅ Formal protocol |
| Confidence tagging | — | — | — | ✅ Every output |
| Skill validation schemas | — | — | — | ✅ 15 schemas |
| Domain bundles | — | — | — | ✅ 16 bundles |
| Built-in teaching agent | — | — | — | ✅ ADHD-friendly, 5 logic gates |
Caution
Archon is not a replacement for LangChain/CrewAI/AutoGen. Those frameworks manage LLM orchestration (tool calling, memory, chains). Archon manages agent discipline (skills, reasoning, guardrails). They are complementary — you can use Archon skills inside agents built with any orchestration framework.
See CONTRIBUTING.md for guidelines on adding skills, bundles, agents, pipelines, synapses, and hooks.
archon validate # Run before submitting — all manifests must passMIT License · Built by Ahmed Taha
98 skills · 17 agents · 5 synapses · 8 pipelines · 16 bundles · 513 tests · Claude Code native