Sandbox demo — every provider, payment, clinical, education, device and delivery action is simulated. No real credentials or integrations.

DevTrust

Catalog foundation · not live

Can an AI-authored change move safely through review?

Help engineering teams govern code changes, dependencies and release decisions.

How this module fits

AtlasProof runs the review operations around a change; Proofence Engine supplies the code and supply-chain evidence. AtlasProof does not implement its own code verifier.

What it covers

  • Repository and pull-request governance
  • Supply-chain evidence view
  • Release review orchestration

Who does what

AtlasProof
Governs: review operations and release decisions
Proofence Engine
Verifies: code and supply-chain evidence

Approval is not execution authorization: recording a decision never runs the action.

Readiness

Current catalog status: Catalog foundation · not live

Defined in the AtlasProof product catalog. Not running for customers; runtime readiness is not approved.

Catalog reference: DevTrust Software Change Governance — reconciled metadata, not an entitlement.

A module's place in this portfolio does not imply an accepted Proofence contract, an active entitlement or a purchase. Runtime readiness is not approved for any module, billing is not configured, and no page here activates anything.

Start with one governed workflow.

Tell us which decisions need accountable review. We scope a pilot around accepted capabilities only.