Amphare ships as a family. atomikd decomposes intent into governed atoms. AmphSE builds them under the kernel. CodeSentinel measures what shipped. RepoGraph maps what depends on what. One substrate underneath; a different door for every way in.
The front door from intent to atoms. atomikd applies atomic decomposition, the methodology behind everything Amphare does: work is broken down until each piece is the smallest reviewable, traceable, estimable thing. Grounded in the published literature: The Physics of Delivery and the Work / Effort / Value atom model from The Fractal Org.
Estimation stops being a negotiation and becomes arithmetic. Requirements go in; typed, sized, dependency-ordered atoms come out, ready for a sprint plan or a kernel dispatch.
read the methodology briefing on requestThe AI code audit instrument. 408 quality atoms across 28 areas, five rubric archetypes, eight compliance overlays. Evidence-tagged findings with a full reliability bundle. The instrument that doesn't average away your catastrophes.
Findings recompute live with zero new model calls: reviewers change a parameter, the math layer replays. Quality becomes a defensible number instead of a vibe.
visit codesentinel →The autonomous software development governance kernel. Backlog to verified, deployable code through governed multi-agent orchestration: append-only ledger, tenant isolation, hash-chained audit trail. Machines do the work. The system stays accountable.
The code intelligence layer, generated as a byproduct of the same single ingestion pass that runs the audit. It owns the two jobs agents cannot grep for: deterministic blast-radius, what breaks if this changes, as an auditable transitive query rather than a probabilistic guess, and the stable semantic map, domain boundaries, ownership, coupling, the skeleton that changes monthly while the code changes hourly. Every edge is epistemically banded.
Change the database module and the graph answers, deterministically, who transitively depends on it. Solid edges are compiler-grade OBSERVED facts; dashed edges are INFERRED dynamic links, labeled as such because the map never claims more certainty than it has.
explore RepoGraph → graph briefing on request