Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
i.1Wiki
Agentic AI Atlas · Quality, Verification, and Delivery
qaa5c.ai
Search the atlas/
Wiki · section map

Trail and section pages

I.In this sectionpp. 1 - 1
QA ArchitectureVersioning and DeliveryCI/CDCoverageEvidence Boundaries
I.
Wiki article

qa

Reading · 1 min

Quality, Verification, and Delivery guide

Tests, evidence-boundary checks, versioning, CI/CD, and downstream artifact distribution. The phase that enforces every guarantee the earlier phases promise.

Page nodewiki/qa/README.mdSection pages · 5Documents · 0

Pages in this section

Start with the section hub, then move sideways into adjacent pages when you need more detail.

QA Architecture

Page

wiki/qa/00-qa-architecture.md

Versioning and Delivery

Page

The schema itself follows semver, governed by graph/schema/versioning.md. Every version is a CatalogVersion node in the graph (the meta-graph references itself).

wiki/qa/01-versioning-and-delivery.md

CI/CD

Page

Every PR against main runs:

wiki/qa/02-cicd.md

Coverage

Page

wiki/qa/03-coverage.md

Evidence Boundaries

Page

Most edges in the graph are internal: AgentVersion → boundto → ModelVersion is fully under our control — both endpoints are nodes we author. But every Claim → evidencedby → EvidenceSource ultimately points outward: at a vendor doc page, a published package, a captured observation, an external attestation. That outward arrow is the evidence boundary.

wiki/qa/04-evidence-boundaries.md

Quality, Verification, and Delivery

Tests, evidence-boundary checks, versioning, CI/CD, and downstream artifact distribution. The phase that **enforces** every guarantee the earlier phases promise.

Files in this directory

PathPurpose
`00-qa-architecture.md`Test pyramid, evidence-boundary checks, regression detection.
`01-versioning-and-delivery.md`Schema semver, downstream artifact tagging, release pipeline, consumer pinning.
`02-cicd.md`CI gates, CD pipeline, promotion environments.
`03-coverage.md`Coverage definitions across the catalog.
`04-evidence-boundaries.md`Where graph claims meet external truth; staleness detection; refresh.
tests/Test fixtures, integration harnesses, e2e scripts.

Acceptance

  • Every NodeKind has at least one test.
  • Every generator has an integration test against a known graph fixture.
  • E2E tests cover key user flows (schema change → regenerated docs → SDK consumer compiles).
  • CI gates schema/graph PRs on validator + invariant + freshness checks.

Trail

Wiki

Quality, Verification, and Delivery

In this section

QA Architecture
Versioning and Delivery
CI/CD
Coverage
Evidence Boundaries

Page record

Open node ledger

wiki/qa/README.md

Documents

No documented graph nodes on this page.