triad-plus 1.6.0 → 1.8.0

package/skills/triad-loop-bootstrap/assets/loop-template/handoff-report.template.md

@@ -22,6 +22,19 @@
 
 - Evidence/review chain: `<verification/review/evaluator references>`
 
+## Quality Contract closure
+
+- Quality Baseline: `<path, revision, fingerprint or legacy PRD-only mode>`
+- Product-quality Evaluator+ verdict: `<PASS|FAIL|INDETERMINATE|not configured>`
+
+| Criterion | Scope | Verdict | Evidence references |
+| --- | --- | --- | --- |
+| `<delivery criterion ID>` | `delivery_closure` | `<PASS|FAIL|INDETERMINATE>` | `<refs>` |
+
+Delivery is `delivered` only when every configured `delivery_closure` criterion
+is recorded as `PASS`. Product-quality criteria are evaluated by the fresh
+Evaluator+ packet and are never silently evaluated during delivery closure.
+
 ## Local-worktree integration
 
 | Card | Consumer worktree | Provider worktree | Branch/commit map | Setup command | Data/event/callback gate |

package/skills/triad-loop-bootstrap/assets/loop-template/quality-baseline.json

@@ -0,0 +1,15 @@
+{
+  "schema_version": 1,
+  "id": "REPLACE_ME_QUALITY_BASELINE_ID",
+  "revision": 1,
+  "sources": [
+    {
+      "id": "prd",
+      "role": "intent",
+      "path": "artifacts/prd.md",
+      "sha256": "REPLACE_ME_SHA256"
+    }
+  ],
+  "criteria": [],
+  "fingerprint": "REPLACE_ME_SHA256"
+}

package/skills/triad-loop-bootstrap/assets/loop-template/run-state.yaml

@@ -7,9 +7,16 @@ delivery:
   handoff: null
   branches: []
   evaluator_report: null
+  quality_criteria: [] # delivery_closure results; product_quality stays in Evaluator+
   delivered_at: null
   owner_message: null
 
+quality_contract:
+  baseline: null
+  fingerprint: null
+  revision: null
+  rebaseline_events: []
+
 feature_plan:
   path: feature-plan.md
   status: declared

package/skills/triad-loop-bootstrap/assets/loop-template/runtime/assignments/assignment.template.json

@@ -16,6 +16,8 @@
   "expected_prd_sha256": "REPLACE_ME_SHA256",
   "expected_card_sha256": "REPLACE_ME_SHA256",
   "expected_gates_sha256": "REPLACE_ME_SHA256",
+  "quality_baseline_path": null,
+  "expected_quality_baseline_fingerprint": null,
   "required_gate_ids": [],
   "scope_contract": null,
   "required_repository_skills": [

package/skills/triad-loop-bootstrap/assets/project.yaml

@@ -12,6 +12,11 @@ project:
     snapshot: artifacts/prd.md
     sha256: null
     source_revision: null
+  quality_contract:
+    # Optional immutable target for v1.8 projects. Leave both values null for
+    # legacy PRD-only behavior; bootstrap fills them only from declared sources.
+    baseline: null # artifacts/quality-baseline.json
+    fingerprint: null
   loop: .loop
   control_plane:
     verification: optional

package/skills/triad-loop-evaluator/SKILL.md

@@ -31,13 +31,23 @@ values in the evaluation report. A missing or mismatched binding makes the
 evaluation `INDETERMINATE`; it never starts repair or changes the closed Triad
 result.
 
-Return a report conforming to `schemas/evaluator-plus-result.schema.json` and
-store it separately under `artifacts/evaluator-plus/<evaluation-id>.json`:
+When the approved packet declares an immutable Quality Contract, receive its
+fingerprint and only the criteria whose scope is `product_quality`. Do not
+receive or evaluate `delivery_closure` criteria; those belong to the delivery
+gate. Return a report conforming to `schemas/evaluator-plus-result.schema.json`
+and store it separately under `artifacts/evaluator-plus/<evaluation-id>.json`:
 
 - `PASS`: the final artifact meets the supplied target;
 - `FAIL`: the target is not met, with direct evidence/references;
 - `INDETERMINATE`: the artifact or target cannot be observed reliably.
 
+For a Quality Contract result, include `quality_baseline_fingerprint` and one
+criterion result for every product-quality criterion, exactly once. Use only
+`PASS`, `FAIL`, or `INDETERMINATE` per criterion. The overall `verdict` is
+deterministically checked by `runtime/triad-evaluator-validate.mjs`: any FAIL
+wins, otherwise any INDETERMINATE wins, otherwise PASS. A mismatch or missing
+criterion is invalid evidence, not a product verdict.
+
 Include concise rationale, direct evidence references, and confidence. Do not
 edit source, change the Triad queue/state, commit, push, approve delivery, or
 request automatic repair, and never reopen the Triad run. A `FAIL` leaves the

package/skills/triad-loop-orchestrator/SKILL.md

@@ -52,6 +52,14 @@ presentation for this invocation, do not repeat it.
    that exact card baseline for every rework attempt: preserved candidate changes
    are normal during rework. Do not create the first scope-bound assignment from
    unattributable dirty product changes; record `invalid_context` instead.
+   If `project.quality_contract` is configured, load and validate its
+   project-relative JSON manifest before dispatch. Verify the canonical
+   fingerprint and every bound source SHA-256, then bind
+   `quality_baseline_path` and `expected_quality_baseline_fingerprint` on the
+   assignment. A `quality_baseline_invalid` or `quality_baseline_drift`
+   result is `invalid_context`: do not dispatch the Developer, run expensive
+   gates, or consume retry/remediation budget. Legacy projects without the
+   quality contract retain PRD-only behavior.
 2. Choose one dependency-approved `ready` card, mark it `in_progress`, append an
    attempt, and create an active assignment before delegating. Before each
    delegation, publish an owner-facing activation notice that attributes the
@@ -80,6 +88,9 @@ presentation for this invocation, do not repeat it.
    catalog and fails closed if a stale assignment names a missing or invalid
    gate. It records the selection mode, card IDs, effective IDs, and required
    IDs in the verification evidence.
+   When a Quality Contract is bound, `triad-verify` performs that baseline
+   preflight before the expensive gates and records its fingerprint in
+   `evidence.baseline.quality_baseline_fingerprint`.
 5. A passing verifier result is **environment-derived evidence**. Move only then
    to `in_review`. Missing, stale, failed, timed-out, invalid-context, or
    invalidated evidence never advances the card.
@@ -196,3 +207,43 @@ or change the already closed Triad run. A per-run `--evaluator` or
 `--no-evaluator` request may override the configuration when the host exposes it.
 Before dispatching it, publish the corresponding attributed Evaluator+
 activation notice.
+
+When `project.quality_contract` is configured, the approved packet additionally
+binds the immutable Quality Baseline fingerprint and includes only criteria whose
+scope is `product_quality`. Never send `delivery_closure` criteria, queue state,
+handoff state, or attempt history to Evaluator+. Validate the returned report
+with a fresh source-integrity preflight from the control workspace first:
+
+```bash
+node .triad-runtime/triad-evaluator-validate.mjs --mode baseline \
+  --project /absolute/path/to/control-workspace \
+  --baseline artifacts/quality-baseline.json
+```
+
+Only after that command returns JSON `valid: true` may Evaluator+ be dispatched.
+Then validate the returned report with this exact command (substituting the real
+paths/fingerprint):
+
+```bash
+node .triad-runtime/triad-evaluator-validate.mjs --mode evaluator \
+  --project /absolute/path/to/control-workspace \
+  --baseline artifacts/quality-baseline.json \
+  --result artifacts/evaluator-plus/evaluation.json \
+  --expected-candidate-fingerprint <final-candidate-fingerprint>
+```
+
+The command reloads the baseline and every bound source immediately before
+dispatch; a non-zero result is a closed validation failure. The control-plane
+aggregate (FAIL over INDETERMINATE over PASS) is authoritative rather than an
+LLM-supplied summary. Immediately before delivery closure, run this second exact
+command with the delivery result array:
+
+```bash
+node .triad-runtime/triad-evaluator-validate.mjs --mode delivery \
+  --project /absolute/path/to/control-workspace \
+  --baseline artifacts/quality-baseline.json \
+  --result artifacts/delivery-closure.json
+```
+
+Record each delivery criterion and its evidence reference in the run/handoff,
+and declare delivery only when every required delivery criterion is `PASS`.