This directory is the repo-owned entrypoint for the spec-native harness.
Use it when you need to answer one of these questions quickly:
- what is the harness flow for a new task
- which risk pack owns the current change surface
- which checks are cheap blockers vs deeper validation
- where Kiro adapters should point instead of inventing local truth
Start here, then branch out:
| Need | Read |
|---|---|
| Overall workflow, conflict policy, and escalation rules | core.md |
| Canonical machine-readable routing source | routing-manifest.json |
| Human-readable routing summary | routing-manifest.md |
| Risk-pack index | risk-packs/README.md |
| Recent Git analysis and remediation closeout | risk-packs/harness-remediation.md |
| NGINX protocol/auth/cache/conditional safety | risk-packs/nginx-protocol-safety.md |
| Release gate and source-build governance | risk-packs/release-governance.md |
| Static security and supply-chain gates | risk-packs/security-static-supply-chain.md |
| System design and rationale for the harness itself | ../architecture/HARNESS_ARCHITECTURE.md |
| Contributor maintenance workflow for evolving harness rules | HARNESS_MAINTENANCE.md |
flowchart TD
A["Task or spec"] --> B["Spec resolver"]
B --> C["Short risk card"]
C --> D["Routing manifest"]
D --> E["Primary pack + supporting packs"]
E --> F["Verification matrix"]
F --> G["Execute"]
G --> H{"Loop or drift?"}
H -- "no" --> I["Finish with evidence"]
H -- "yes" --> J["Shrink diff + recompute route/verify"]
J --> K{"Converges?"}
K -- "yes" --> G
K -- "no" --> L["Escalate or outside voice"]
flowchart LR
A["AGENTS.md<br/>map + contract"] --> B["docs/harness/<br/>core + manifest + packs"]
B --> C["Make / CI / checkers"]
B --> D["Optional local adapters"]
B --> E["Rule-maintenance skills"]
F["Optional local spec hints (read-only)"] --> B
G["User-local state carrier"] --> E
E --> B
AGENTS.mdremains the Codex-first contract.docs/harness/owns reusable harness truth, not domain semantics already documented elsewhere.- Optional local spec inputs are read-only and must not serve as a cache or annotation store for repository truth.
- Optional local adapter layers can summarize and link, but they do not define independent rules.
- Outside voice is advisory. A different model family can challenge the current path, but it does not overrule the user.
- ../architecture/HARNESS_ARCHITECTURE.md
- HARNESS_MAINTENANCE.md
- ../architecture/ADR/0005-repo-owned-harness.md
- ../architecture/README.md
- ../testing/README.md
- ../DOCUMENTATION_DUPLICATION_POLICY.md
For local agent workflows, a repo-tracked helper skill is available at:
skills/nginx-markdown-harness-maintenance/SKILL.md- Setup guide for contributors and local IDE/agent wiring: HARNESS_SKILL_SETUP.md
This skill is an execution choreographer only. It must route and verify against
repo-owned truth surfaces (AGENTS.md, docs/harness/, tools/harness/,
Makefile, CI), and must not redefine runtime semantics.
| Version | Date | Author | Changes |
|---|---|---|---|
| 0.9.2 | 2026-08-06 | Kang | Added five generic pre-freeze release gate families: release-candidate-evidence, artifact-registry, release-evidence-manifest, fuzz-qualification, soak-qualification |
| 0.9.2 | 2026-08-05 | Kang | Added release-matrix verification family (release-matrix-check gate) for canonical release matrix schema/ABI/feature binding validation |
| 0.9.2 | 2026-07-30 | Kang | Added diagnostics-access-phase verification family (verify-diagnostics-access-phase-e2e gate) |
| 0.8.3 | 2026-06-26 | Kang | Added version-consistency verification family and release-manifest verification |
| 0.8.2 | 2026-06-13 | Codex | Added static security and supply-chain gate entrypoint |
| 0.6.2 | 2026-05-08 | Kang | Unified version narrative to 0.6.2 current release line |
| 0.5.5 | 2026-04-24 | Codex | Added harness-remediation entrypoint |
| 0.5.5 | 2026-04-24 | Codex | Added nginx-protocol-safety (auth/cache/conditional safety) and release-governance entrypoints |
| 0.5.0 | 2026-04-21 | docs-standardization | Added update tracking section |