Skip to content

docs(readme): add "Where ARK fits" — position ARK (runtime) vs AAP (assurance) #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mikim merged 1 commit into from
Jul 25, 2026
Merged

docs(readme): add "Where ARK fits" — position ARK (runtime) vs AAP (assurance) #21

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,6 +79,17 @@ ARK follows five strict principles:

All modules are TypeScript, ESM-only, and compose independently.

## Where ARK fits

ARK operates at **runtime**: it decides how a live agent recovers from a
failure and turns each incident into a structured signal. That is a different
layer from the [Agentic Assurance Profile (AAP)](https://github.com/MosslandOpenDevs/agentic-assurance-profile)
— a repository-level profile for governing whether an AI-agent-built project's
claims, invariants, and evidence still hold as the code changes. The two
compose rather than compete: you **run** ARK as a reliability substrate and
**adopt** AAP as an assurance profile — under which ARK's deterministic policies
and JSON incident artifacts can serve as runtime evidence.

## Quickstart

> **Not yet published to npm.** Until the first release, use the `@ark/*`
Expand Down