Eve library

Neith QA Support Infrastructure

Guide

Revision 1

On this page

Support guide for @neith/qa.

Intake Channels#

  • package-level QA review for failing certification or report-drift cases
  • repository test failures that indicate an implemented claim has fallen out of sync with its published evidence
  • documentation-index drift affecting the standalone Neith or Oshun-local refs

Escalation Flow#

  1. Identify the failing auditor, certification ledger, or documentation index.
  2. Attach the failing test, report output, or affected evidence path.
  3. Assign ownership to the package or domain surface that owns the claim.
  4. Escalate to the shared support hub only when multiple implemented surfaces must change together.

Operational Evidence#

  • libs/neith/qa/src/code-quality/*.spec.ts provides repo-backed certification coverage for the implemented Neith completion criteria
  • docs/domains/neith/*.md and docs/releases/v1/domains/neith/* are kept in sync with the QA auditors to avoid evidence drift
  • support-oriented ownership is preserved by requiring each certification change to update docs, tests, and discoverability links together