From 8c7f6281a6691b1d407c542e9cbfc7793fbb93b9 Mon Sep 17 00:00:00 2001 From: mikim <1441941+mikim@users.noreply.github.com> Date: Sat, 25 Jul 2026 09:31:22 +0900 Subject: [PATCH] =?UTF-8?q?docs(readme):=20add=20"Where=20ARK=20fits"=20?= =?UTF-8?q?=E2=80=94=20position=20ARK=20(runtime)=20vs=20AAP=20(assurance)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Adds a short positioning section clarifying that ARK is a runtime reliability layer, a different layer from the Agentic Assurance Profile (AAP) — a repository-level assurance profile you adopt. Frames the two as complementary (run ARK / adopt AAP), with ARK's deterministic policies and JSON incident artifacts usable as runtime evidence under AAP. Placed after Core Modules so the referenced packages/artifacts are already defined (no forward references). Co-Authored-By: Claude Opus 4.8 --- README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/README.md b/README.md index d2b016c..2f78df9 100644 --- a/README.md +++ b/README.md @@ -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/*`