Arxi Decision Gate Asset Core
Docs
Decision Gate Docs

Deterministic, replayable gate evaluation with auditable decisions.

Asset Core docs

Decision Gate + AssetCore Integration

Tagline: DG evaluates requirements. ASC provides the world-state substrate for deterministic evidence.

Compatibility: Compatible with AssetCore.

AssetCore overview: assetcore.io/asset-core.

Work in progress: This hub is the focal point for testing external provider integrations and remains an open work in progress. See F:Docs/roadmap/README.md L73-L81 for the current OSS launch plan and status.

Table of Contents

Positioning

  • Decision Gate: deterministic checkpoint and requirement-evaluation control plane.
  • AssetCore: deterministic structured memory substrate for explicit world state (0d - 2d, 3d planned), replayable transactions, and namespace-backed proofs.
  • Integration: optional and explicit; no code coupling between repos.

Integration Boundaries

  • DG remains authoritative for scenarios, gates, decisions, and runpacks.
  • ASC remains authoritative for world-state and namespace validity.
  • Auth tokens from ASC are not parsed by DG; an integration layer maps principals to DG tool permissions.

Data Flow

Decision Gate + AssetCore data flow showing namespace checks, evidence queries, and runpack artifacts. Decision Gate + AssetCore data flow showing namespace checks, evidence queries, and runpack artifacts.

When to Use ASC

Use DG with ASC when:

  • Evidence must be replayable against a deterministic world-state snapshot.
  • Namespace authority must be enforced by a system of record.
  • Auditable anchors must reference ASC commit or sequence metadata.

Use DG without ASC when:

  • Evidence comes from local artifacts or non-ASC services.
  • A lightweight gating layer is sufficient.

Starting Points

References