Studio by Aftergraph
demoGeneral-purpose operating environment for governed agent work. Chat, manage missions, approve actions, inspect evidence.
Infrastructure + open research · verifiable intelligent systems
For teams that let AI agents write code, change production or act on real systems. Aftergraph binds agent work to scoped authority, durable execution and evidence that an independent verifier checks, so agent says done becomes verified outcome.
Who it is for
Teams already let agents write code, change systems and run long jobs. The hard part is knowing the work actually happened, within the permission it was given. Three places Aftergraph is built for today.
Coding agents open PRs faster than people can review them. Sentinel evaluates the exact commit and returns a SHIP / DO NOT SHIP verdict with the evidence attached.
See SentinelAn agent that can deploy, pay or email needs scoped, expiring permission, not a shared key. AIE and Trust Gateway grant authority per mission and fail closed.
See Trust GatewayMulti-hour jobs crash, time out and restart. WORKS keeps leases, state and recovery, so the result can be traced back to every step that produced it.
See WORKSTell us what your agents do and where verification breaks today. Concrete failures shape the roadmap more than feature requests.
Start a discussionDevelopers
No signup, no key. The site proves which code it runs. Copy, paste, compare the SHA. Example output shown.
curl -s https://aftergraph.org/healthz
# {"status":"ok","sha":"66b29af",...}
git ls-remote https://github.com/Aftergraph/aftergraph.org HEAD
# SHAs must match — live code equals reviewed codeconst live = await fetch('https://aftergraph.org/healthz')
.then(r => r.json());
console.log(live.status, live.sha); // ok 66b29afWhat do you want to do?
Choose by intent. Each entry path routes to an existing product, governed boundary, or evidence source.
Compose governed intelligent work through the primary experience and developer surfaces.
Follow durable work and runtime orchestration without collapsing their ownership boundaries.
Read reproducible research and canonical architecture without promoting either into runtime authority.
Products
Studio, Wie, Sentinel and Atlas are the current public entry surfaces. The wider canonical portfolio is larger and includes private products, operator projections, capabilities, assurance and operations systems.
General-purpose operating environment for governed agent work. Chat, manage missions, approve actions, inspect evidence.
Work Intelligence Engine. Source-neutral observations become structured, attributable WorkItems ready for review.
Verified code review. PRs evaluated against exact HEAD with evidence-backed SHIP / DO NOT SHIP verdicts.
Production evidence-aware development observatory and system graph. Inspect topology, truth planes, drift, snapshots and cited assertions.
System portfolio · Governance topology/2.0
Governance evidence cut 2026-09-30 records 34 canonical repositories. Visibility and lifecycle are shown separately from product maturity; topology membership does not imply production readiness. See all 32 systems.
Persistent personal intelligent-agent environment and operator cockpit that composes canonical Aftergraph domain systems without taking ownership of their truth.
ad7e841Branded service-operations operator experience over Business Ops and tenant-specific domain truth, with attention and verification projections.
a4a013aOrganization-reality and operational-intelligence projection. It is a secondary diagnostic/backend surface — not the canonical operator/control owner.
Capability-resolution and tool-routing control plane. Agents request capabilities; authority, secrets and execution remain owned by their canonical systems.
86e5fd8Semantic compatibility contract for portable agent skills across models, runtimes and capability environments. Portable does not mean merely parseable.
aeccfe5Read-only scheduled organization sensing with evidence gating, dedupe and escalation. Observation explicitly grants no execution authority.
598fa98Catalog rule: canonical != public != production. Inspect the machine-readable catalog for all repositories, roles, visibility and lifecycle.
Open platform catalogAgent–user boundary · illustrative
Modern agent interfaces need ordered, inspectable events. Aftergraph keeps that interaction stream separate from authority, execution evidence and independent verification.
progress ≠ completion evidence.provenance ≠ ownership.resume ≠ ambient permission.Why Aftergraph
The system is designed around durable principles instead of confidence theatre.
Agent says done≠Verified outcome
Finished work still needs independent checking. Aftergraph separates self-report from proof at every layer.
Live evidence
This surface cross-checks Aftergraph's same-origin health and deploy-provenance contracts at runtime. A verified state requires the exact SHA, route and deployment marker to agree.
The whole company
Every permanent system in the governance catalog, generated from /platform/catalog.json. Public systems link to source. Private systems are listed so you can see the shape of the company, and their code stays private. Being on the map does not mean production ready: lifecycle is shown on each card.
What people use: operator, personal-agent, work-intelligence, review and service-operations surfaces.
Governed operator plane for supervising autonomous work across agents, missions, execution nodes, Runtime projection, and Aftergraph infrastructure.
In AtlasGeneral-purpose human operating environment for Chat, Work, Space, control and evidence surfaces.
SourcePersistent personal intelligent-agent environment: identity/context continuity, agent coordination, user-facing conversational and delegated-work experiences, surfaced through HomeOS and other approved clients.
In AtlasOperational intelligence projection, organization reality queries, missions/agents/compute/attention/evidence aggregation and secondary diagnostic surfaces without inventing canonical state.
SourceWie browser experience and least-privilege BFF consuming canonical Work Intelligence state from wi-backend.
In AtlasRenOS branded service-operations operator experience, workspace composition, chat projection, attention/control presentation and domain/process/verification views.
In AtlasExact-HEAD verified code-review verdicts with stale-base invalidation and cited evidence.
SourceAuthority, enforcement, runtime and durable execution underneath every product.
Portable institution, authority, delegation, lifecycle, budget and revocation semantics.
SourceFail-closed runtime admission, policy enforcement, approvals, secrets and action audit.
SourceAgent lifecycle, orchestration, dispatch, checkpoints, metering and observability.
In AtlasDurable work state, scheduling, workers, leases, recovery, execution evidence and quittance.
SourceSource-neutral observation to canonical WorkItem inference, review, publication and promotion boundaries.
SourceContinuity, skills, models, scheduling, knowledge and the research that keeps claims honest.
Portable transfer of actionable context/state across model, agent, session and runtime boundaries.
In AtlasContinuity and containment fault-injection campaigns and verification harnesses.
In AtlasSPEC-001, MISSION-Bench methodology, scientific claims, experiments, assurance and publication evidence.
SourceGoverned skill discovery, trust, lifecycle, provenance, compatibility and distribution.
In AtlasReusable model research, experiment, evaluation, promotion and provenance methodology.
In AtlasAFM-specific model training, datasets, experiments, evaluations and artifact manifests.
In AtlasImmutable promoted model identities, versions, aliases, lifecycle, provenance and artifact locations.
In AtlasRead-only scheduled organization sensing, evidence gating, dedupe and Telegram escalation. It grants no execution authority.
SourceProvenance-pinned rendering, discovery, developer documentation and agent-readable context surfaces.
SourceSemantic compatibility, bounded effects, degradation and conformance for portable AI agent skills.
SourceToolFabric registry federation, semantic capability resolution, health-aware routing plans and non-authoritative tool selection.
In AtlasContracts, brand, community, the front door, business domains and systems in transition.
Platform topology, cross-repo boundaries, contract registration and generated org-state mechanics.
SourceLegacy product, Hermes integration and migration-source behavior pending governed extraction.
In AtlasInternal assurance-product incubation concept under naming/clearance hold. Topology membership does not imply public or production maturity.
In AtlasPublic website, marketing information architecture and system launcher.
SourceVisual identity, semantic design tokens, master assets and public communication design rules.
SourceOrganization profile, contribution defaults, security/support routing and shared community infrastructure.
SourceOpen benchmark and evaluation suite for semantic portability of skills across models, runtimes and capability environments.
In AtlasCanonical tenant-neutral service-business domain state, invariants, migration mappings, charge-source facts and shadow-conformance semantics.
In AtlasRendetalje-specific cleaning semantics, pricing policies, estimator behavior, playbooks, communication policy, tenant configuration, migration mappings and tenant-specific Business Ops composition.
In AtlasPlatform · Illustrative system walkthrough
V4 keeps semantic ownership explicit. Evidence and Verified Outcome are lifecycle results — not extra planes.
Lifecycle: Intent / Experience → Intelligence → Authority → Trust → Runtime → Execution → Evidence → Verification → Verified Outcome.
Architecture sourceEvidence
A claim can be useful without being promoted. Every surface tells you what kind of evidence you are looking at.
SPEC-001 and MISSION-Bench make research claims reproducible and inspectable.
Governance defines boundaries and contracts without silently becoming implementation.
WORKS, Trust Gateway and other repos expose what is actually built.
Only independent evidence can justify a stronger operational claim.
Research evidence can justify a promotion decision; it is never runtime authority by itself.
Inspect evidencePrinciples
Permissions are scoped to the mission, never ambient.
Long work survives interruption with leases and recovery.
Claims point to inspectable artifacts, not opinions.
Efficiency measured against what was proven.
Prototype, research and production stay visibly distinct.
History
Merged history plus the current branch direction. Every production entry is inspectable on GitHub.
Explore the system topology, read the contracts, inspect evidence, then launch governed work.