Quick Start

ABS Core is a self-hosted runtime governance stack for AI agents. This guide covers local inspection, workspace setup, and source-based execution in a controlled environment.

1. Prerequisites

• Rust Toolchain: 1.75+.
• Node.js: v20+.
• pnpm: v9+.
• Environment: Linux or macOS recommended.

2. Access the source

ABS Core is not documented here as a public self-service product. Use the repository URL or source package provisioned through your licensed engagement or internal distribution channel.

git clone <provisioned-repository-url> abs-core
cd abs-core

3. Inspect the project structure

Relevant areas in the current repository topology (v3.5.0):

• core/engine-wasm — Rust/WASM policy engine.
• core/hub — governance hub and service clients.
• modules/vault — certified policy pack runtime.
• modules/audit — governance audit module.
• adapters/ — integrations with external ecosystems and frameworks.
• config/mint — documentation site source.
• evidence/ — diligence, benchmark, and investor-support material.

4. Build the WASM engine

The Rust engine currently lives under core/engine-wasm.

cd core/engine-wasm
cargo build --target wasm32-unknown-unknown --release

This produces the WASM build artifact for the policy engine.

5. Install workspace dependencies

Under the root project directory, install the workspace dependencies with pnpm:

pnpm install

6. Run workspace tasks

The root workspace exposes the following scripts across packages:

pnpm dev
pnpm build
pnpm lint
pnpm deploy

If a package requires a specific procedure not handled by these commands, refer to that package's local documentation.

7. Scope note

ABS Core should be evaluated here as:

• runtime governance infrastructure,
• policy enforcement middleware,
• and customer-controlled deployment software.

It is not described here as a turnkey public SaaS subscription.

8. Proof and maturity note

Treat the current repository as the source of truth for what is implemented. Broader claims should be validated against benchmark evidence, module status, and deployment-specific technical review.

9. Deployment note

Deployment topology depends on the target environment. Components may run in edge, self-hosted, or other customer-controlled environments depending on the governed workflow.