Stale state blocks with VERDICT-STATE-STALE (naming what changed);
a fresh bundle + verdict restores eligibility. The full flow runs as a
test (tests/e2e/trust-flow-demo.test.ts) and is walked through in
docs/guides/demo-trust-flow.md —
offline, no API key.
This repository dogfoods itself: it was built by following the same docs/tasks task system it ships.
What ACKit is not: an autonomous coding agent, a model runtime, a browser
automation framework, an agent router, or a cloud orchestration service. ACKit
is the deterministic, offline-first engineering layer those agents share —
repository context, explicit intent, structured tasks, plan discipline,
evidence-backed completion, resumability, independent verification, policy
enforcement, drift detection, and provider interoperability. Model execution
and autonomous coding stay with your chosen agent (Codex, Claude Code,
OpenCode, Copilot, Gemini, Cursor, Cline, any MCP-capable agent).
flowchart LR
A[Repository] --> B[Filesystem Engine<br/>realpath containment]
B --> C[Instruction Graph v2<br/>scope → precedence]
B --> D[Scanner<br/>redacted findings]
B --> E[Context Pack<br/>budgeted ranking]
C --> F[Readiness 0–100<br/>6 categories]
D --> F
E --> F
C --> G[Optimize v2<br/>8-class + waste]
D --> G
F --> H{CLI / SDK / MCP / Action / Dashboard / VS Code}
G --> H
Single door to filesystem — one containment engine
Redaction before reporters — findings constructed already-safe
Determinism — same repo+config → byte-identical JSON/fingerprints
Offline-by-construction — no network in product code
Trust chain (v0.5)
flowchart LR
T[Task / Intent / Workflow] --> E[Evidence]
E --> V[Bound Verification<br/>bundle v2 + verdict v2]
V --> I[Verdict Independence + Freshness<br/>reviewed bundle + replay/stale refusal]
I --> S[Canonical Status<br/>ackit.status.v1, read-only]
S --> H[Portable Handoff v2<br/>export / import / resume]
H --> P[CLI / SDK / MCP / Action / VS Code]
Context7 / Docs7: Maintained indexing settings live in context7.json; Docs7 navigation uses docs/docs.json. See the Context7, Docs7 and verification guide for owner claiming, badge requests and optional Docs7 Free hosting. Existing documentation hosting remains unchanged.
🔗 Ecosystem
Community integration for ACKit and GitHub Spec Kit: Spec Kit bridge
(@cynrath/ackit-spec-kit-bridge) connects
Spec Kit's intent-driven development artifacts to ACKit's deterministic repository context, task
lifecycle, evidence, verification, and completion gates. Offline-first, no telemetry.
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich Agent Context Kit?
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt Agent Context Kit einen API-Schlüssel?
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Welchen Transport verwendet Agent Context Kit?
Agent Context Kit läuft lokal über stdio.
Wann wurde Agent Context Kit zuletzt geprüft?
Zuletzt geprüft: 2026-10-28. Offline-first toolkit for agent-ready repositories: readiness scoring, instruction graphs, context packs, policy/rule packs, MCP, GitHub Actions, diagnostics, and VS Code.