@agent-delivery-harness/conformance 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,5 @@
+delivery-harness
+Copyright the delivery-harness authors
+
+This product includes software developed by the delivery-harness authors
+(https://github.com/kwam1na/agent-delivery-harness).

package/README.md

@@ -0,0 +1,159 @@
+# Delivery Evidence Conformance Kit
+
+Golden vectors for validators of the **delivery-evidence/1** specification
+(envelope) and the **review.green/1** payload. A validator implementation that
+produces the expected outcome for every vector conforms to the machine-checkable
+core of the spec.
+
+The corpus is derived from a production recorder's test suite
+(`athena:scripts/harness-review-evidence.test.ts`, ~1,000 lines) that has gated
+agent-delivered merges since mid-2026, restated against the generalized
+envelope. Provenance is recorded per vector.
+
+## Layout
+
+```
+kit.json                    index: every vector with id, file, rules, expectation
+context/repo-config.json    the repository gate configuration vectors assume
+context/environment.json    the submission-time state the harness must establish
+vectors/accept/*.json       manifests a conforming validator MUST accept
+vectors/reject/*.json       manifests a conforming validator MUST reject
+generate.ts                 regenerates everything above (bun generate.ts <outDir>)
+```
+
+## Vector format
+
+Each vector is self-contained:
+
+```jsonc
+{
+  "vectorVersion": 1,
+  "id": "rg-7-defer-p0",
+  "title": "Illegal deferral: p0",
+  "rules": ["RG-7"],                    // spec rule ids this vector exercises
+  "provenance": "athena:… | new in spec | spec-tightened",
+  "expect": { "result": "rejected", "codes": ["illegal_deferral"] },
+  "environment": { … },                 // optional overrides of context/environment.json
+  "extra": { … },                       // optional protocol notes (multi-step vectors)
+  "artifacts": { "reviewers/correctness.json": "<exact file bytes>" },
+  "manifest": { … }                     // the delivery-evidence/1 manifest to submit
+}
+```
+
+## Running a vector
+
+For each vector, the harness under test:
+
+1. Loads `context/repo-config.json` as the repository's gate configuration.
+2. Establishes the submission environment from `context/environment.json`,
+   merged with the vector's `environment` overrides:
+   - `currentCandidate` is what the recorder's candidate capture returns at
+     submission time.
+   - `prepared: false` means preparation is absent/failed (the capture reports
+     an unprepared state).
+   - `manifestLocation: "outside-run-root"` means the harness places the
+     manifest file somewhere other than the allocated run root.
+3. Allocates a run root for `manifest.provider.runId` and materializes each
+   entry of `artifacts` at its path (exact bytes) relative to that root. An
+   artifact path that is itself invalid (e.g. `../outside.json`) is part of the
+   vector's point; materialize it where the path indicates, or skip
+   materialization if the validator rejects on path shape before file access.
+4. Submits the manifest through the recorder.
+5. Compares the outcome to `expect`.
+
+### Multi-step vectors
+
+- `a-idempotent-resubmission` (`extra.submitTwice`): submit the same manifest
+  twice. Both submissions succeed and the record ids are identical.
+- `sub-4-record-conflict` (`extra.submitFirst`): submit `extra.submitFirst`
+  (accepted), then the vector's `manifest`. Same record identity, different
+  content — the second submission is rejected with `record_conflict`.
+
+## Expectation semantics
+
+- `result: "accepted"` — the submission MUST be accepted and one evidence
+  record written per claim. No rejection codes.
+- `result: "rejected"` — the submission MUST be rejected, no record written,
+  and the response MUST include **every** code listed in `expect.codes`.
+  Additional codes are permitted: several vectors violate more than one rule by
+  construction (SUB-5 requires reporting all violations), and the kit does not
+  over-specify cascade behavior. The listed codes are the floor, not the
+  ceiling.
+
+## Provenance markers
+
+- `athena:…` — restates a case from the production test corpus.
+- `new in spec; no Athena antecedent` — covers spec surface the production
+  contract did not have (claims array, artifact digests, attestation levels,
+  strict unknown-member parsing, repository requirement).
+- `spec-tightened; Athena accepted a looser form` — the spec is deliberately
+  stricter here; the production recorder accepted this shape. Two cases:
+  - `env-9-empty-run-history` — Athena accepted an empty mutation sequence;
+    the spec requires a non-empty `runHistory` whose final entry names the
+    candidate tree and final pass.
+  - `rg-9-iteration-count-mismatch` — Athena accepted an explicit
+    `iterationCount` that disagreed with the mutation sequence; the spec
+    requires `iterationCount == runHistory.length`.
+
+## Known divergences from the production contract
+
+Beyond the two tightenings above, the spec-shaped manifest differs from the
+production manifest in ways the kit reflects:
+
+1. **Claims array.** Production bound one manifest to one obligation; the
+   envelope carries `claims[]` and the recorder writes one record per claim.
+2. **Artifact digests.** Production validated artifacts at record time but did
+   not hash them into the manifest; the envelope requires per-artifact
+   `sha256` (`env-11-artifact-digest-mismatch` is new surface).
+3. **Strict parsing.** Production tolerated some unknown members; the spec
+   rejects any (`gen-1-*`). Production's summary-count fields
+   (`unresolvedActionableCount`, `blockingCount`) were removed as pure
+   derivations — their presence now trips `unknown_member`
+   (`gen-1-legacy-count-field`).
+4. **40-hex object ids.** Production fixtures used symbolic ids
+   (`"tree-a"`); the spec requires real git object-id shapes, so all kit ids
+   are deterministic hex derived in `generate.ts`.
+5. **Approval stamp shape.** Production stamps carried flat
+   `providerId`/`runId` fields; the spec nests them under `provider` and
+   renames `worktreeId` to `workspaceId` (§9.2).
+
+## Coverage
+
+89 vectors: 8 accept, 81 reject. Every rule in spec §8 (GEN, ENV, SUB) and §9.3
+(RG) is exercised by at least one vector except: GEN-3 and SUB-5 (meta rules
+about validator behavior, observable through the multi-code vectors), GEN-5
+(prohibition on time-based decisions — not observable from a single
+submission), and ENV-3/ENV-7 (subsumed by schema-shape vectors). The signing
+profile, additional payload specs, and gate-policy behavior (freshness at gate
+time, waivers, delegation) are out of the kit's scope, as they are out of the
+spec's.
+
+## Regenerating
+
+```
+bun generate.ts <outDir>
+```
+
+The generator is table-driven — one entry per vector, mirroring the structure
+of the source test corpus. Accept-vector artifact digests are computed from the
+emitted bytes, so edits to artifact content stay internally consistent
+automatically.
+
+---
+
+## Vendored layout in this repo
+
+This README is the kit's own, carried verbatim. Two paths differ from the layout
+above because the kit is vendored into an npm workspace:
+
+| Kit path | Path here |
+|---|---|
+| kit root (`kit.json`, `context/`, `vectors/`) | `packages/conformance/vectors/` |
+| `generate.ts` | `packages/conformance/src/generate.ts` |
+
+Regenerate with `npm run kit:generate` (the generator is also runnable directly
+under either runtime: `node --import tsx packages/conformance/src/generate.ts <outDir>`
+or `bun packages/conformance/src/generate.ts <outDir>`). The vendored tree is
+guarded against drift by `packages/conformance/src/generate.test.ts`, which
+regenerates into a temp directory and requires byte-identical output — so the
+vectors are never hand-edited, only regenerated.

package/fixtures/repo-config-adapter.ts

@@ -0,0 +1,250 @@
+/**
+ * The conformance kit's `context/repo-config.json`, adapted into a harness
+ * config.
+ *
+ * The kit declares the repository policy a validator needs to judge its
+ * vectors, and nothing else: a gate id, the envelope specs and identity
+ * versions it accepts, and one obligation with its payload specs, providers and
+ * minimum attestation level. A harness config is a much wider surface, so the
+ * adapter does three separable things, and the test beside it checks each one:
+ *
+ *   MAPS the fields the kit declares. These are the dimensions the vectors are
+ *   bound to — a vector that expects `unregistered_provider` is expecting it
+ *   against *this* provider list — so they are carried across verbatim.
+ *
+ *   STRIPS `configVersion`. It versions the kit's own file format and has no
+ *   counterpart in a harness config; carrying it would fail the closed grammar.
+ *
+ *   DEFAULTS every remaining dimension. Each default is either vector-
+ *   independent (no vector's expectation can turn on it) or forced by a config
+ *   invariant. There is exactly one of the latter, and it is named below.
+ *
+ * THE ONE CONSTRAINED DEFAULT. The kit declares `deliverable-tree/v1` as its
+ * identity version, and the config invariants bind that token to its narration
+ * set in both directions. So `reviewNeutral` is not free here: it must be the
+ * `deliverable-tree/v1` narration set or the config will not load. This is
+ * harmless for kit runs, which stub candidate capture with each vector's own
+ * values and never recompute an identity from a real tree — but it is a
+ * constraint rather than a free choice, and pretending otherwise would hide the
+ * one place the adapter's hands are tied.
+ *
+ * NEGATIVE SPACE. Four tokens must stay *absent* from this config, because four
+ * reject vectors expect a rejection that only happens while they are absent:
+ * the obligation `qa.exercised`, the payload spec `review.green/0`, the provider
+ * `unknown.provider`, and the identity version `deliverable-tree/v0`. A default
+ * that quietly widened the config to include one of them would turn a reject
+ * vector green without changing a single expectation. `negativeSpaceViolations`
+ * exists so that widening is caught rather than discovered.
+ */
+import { readFileSync } from "node:fs";
+import path from "node:path";
+import { fileURLToPath } from "node:url";
+import {
+  DELIVERABLE_TREE_V1_NARRATION_SET,
+  defineHarnessConfig,
+  type HarnessConfig,
+  type HarnessConfigInput,
+} from "@agent-delivery-harness/kernel";
+
+/** The kit's own file format, as declared in `context/repo-config.json`. */
+export interface KitRepoConfig {
+  readonly configVersion: number;
+  readonly gateId: string;
+  readonly acceptedEnvelopeSpecs: readonly string[];
+  readonly identityVersions: readonly string[];
+  readonly obligations: Readonly<
+    Record<
+      string,
+      {
+        readonly acceptedPayloadSpecs: readonly string[];
+        readonly providers: readonly string[];
+        readonly minimumAttestationLevel: string;
+      }
+    >
+  >;
+}
+
+/** Dimensions carried across from the kit's declaration. */
+export const KIT_MAPPED_DIMENSIONS: readonly string[] = [
+  "gateId",
+  "acceptedEnvelopeSpecs",
+  "identityVersions",
+  // Derived from the declaration: the kit names exactly one identity version,
+  // and a recorder must accept the identity it computes.
+  "computingIdentityVersion",
+  "providers.ids",
+  "obligations.ids",
+  "obligations.providers",
+  "obligations.acceptedPayloadSpecs",
+  "obligations.minimumAttestationLevel",
+];
+
+/**
+ * Dimensions the kit does not declare, each with the reason its default is safe.
+ * `invariant-constrained` means the value is not a free choice; every other
+ * entry is a dimension no vector expectation can turn on.
+ */
+export const KIT_DEFAULTED_DIMENSIONS: Readonly<Record<string, "vector-independent" | "invariant-constrained">> = {
+  baseRef: "vector-independent",
+  storageNamespace: "vector-independent",
+  reviewNeutral: "invariant-constrained",
+  recordNeutral: "vector-independent",
+  pathClassification: "vector-independent",
+  sensitivePaths: "vector-independent",
+  activationThreshold: "vector-independent",
+  agentEnvSignals: "vector-independent",
+  ciPolicies: "vector-independent",
+  ciPolicyEnvKey: "vector-independent",
+  preparationWiringPaths: "vector-independent",
+  deliveryRecordPath: "vector-independent",
+  deliveryRecordVerification: "vector-independent",
+  "providers.findingCodes": "vector-independent",
+  "obligations.activation.kind": "vector-independent",
+  "obligations.activation.sensitiveGroupIds": "vector-independent",
+  "obligations.activation.relevantBinaryChangeActivates": "vector-independent",
+  "obligations.activation.relevantZeroLineChangeActivates": "vector-independent",
+  "obligations.freshness": "vector-independent",
+  "obligations.providerPolicy": "vector-independent",
+  "obligations.allowedResolutionKinds": "vector-independent",
+  "obligations.humanWaiverAllowed": "vector-independent",
+  "obligations.ciDelegationPolicyIds": "vector-independent",
+  "obligations.remediation": "vector-independent",
+  "obligations.waivableCodes": "vector-independent",
+  "obligations.nonWaivableCodes": "vector-independent",
+};
+
+/** Tokens whose absence four reject vectors depend on. */
+export const KIT_NEGATIVE_SPACE: readonly string[] = [
+  "qa.exercised",
+  "review.green/0",
+  "unknown.provider",
+  "deliverable-tree/v0",
+];
+
+/**
+ * The gate's structural finding codes, restated so the adapter's classification
+ * is a decision this file makes rather than a set it inherits. A structural code
+ * added to the contract shows up here as an unclassified-code finding at load
+ * time, which is the intended way to learn about it.
+ */
+const STRUCTURAL_CODES: readonly string[] = [
+  "review_evidence_missing",
+  "stale_evidence",
+  "evidence_not_green",
+  "unresolved_actionable_findings",
+  "ambiguous_records",
+  "malformed_record",
+  "unknown_provider",
+  "live_provider_missing",
+  "ambiguous_live_provider",
+  "live_provider_failed",
+  "resolution_not_allowed",
+];
+
+function requireRecord(value: unknown, label: string): Record<string, unknown> {
+  if (typeof value !== "object" || value === null || Array.isArray(value)) {
+    throw new Error(`${label} must be an object.`);
+  }
+  return value as Record<string, unknown>;
+}
+
+/**
+ * Maps a parsed kit repo-config into a harness config. Pure: the caller supplies
+ * the parsed value, so the mapping is testable against a synthetic declaration
+ * without touching the vendored kit.
+ */
+export function adaptKitRepoConfig(raw: unknown): HarnessConfig {
+  const declared = requireRecord(raw, "kit repo-config");
+  const obligations = requireRecord(declared["obligations"], "kit repo-config obligations");
+
+  const identityVersions = declared["identityVersions"] as readonly string[];
+  const providerIds = [
+    ...new Set(
+      Object.values(obligations).flatMap((obligation) => (requireRecord(obligation, "kit obligation")["providers"] as readonly string[]) ?? []),
+    ),
+  ];
+
+  const input: HarnessConfigInput = {
+    // ── Mapped ──
+    gateId: declared["gateId"] as string,
+    acceptedEnvelopeSpecs: declared["acceptedEnvelopeSpecs"] as readonly string[],
+    identityVersions,
+    // The kit declares one identity version; a recorder must accept the identity
+    // it computes, so the sole declared version is the computing one.
+    computingIdentityVersion: identityVersions[0] as string,
+    // The kit registers providers per obligation and declares no finding codes
+    // for them, so the registry is their union with an empty code surface. That
+    // leaves the emittable universe equal to the structural registry, which is
+    // what the classification below partitions.
+    providers: providerIds.map((id) => ({ id, findingCodes: [] })),
+    obligations: Object.entries(obligations).map(([id, declaredObligation]) => {
+      const obligation = requireRecord(declaredObligation, `kit obligation ${id}`);
+      return {
+        id,
+        acceptedPayloadSpecs: obligation["acceptedPayloadSpecs"] as readonly string[],
+        providers: obligation["providers"] as readonly string[],
+        minimumAttestationLevel: obligation["minimumAttestationLevel"] as "self",
+        // ── Defaulted, per obligation ──
+        activation: { kind: "relevant_change" },
+        freshness: "exact_candidate",
+        allowedResolutionKinds: ["satisfied_evidence", "not_applicable"],
+        humanWaiverAllowed: false,
+        ciDelegationPolicyIds: [],
+        remediation: {
+          default: [
+            {
+              id: "submit-evidence",
+              kind: "manual_action",
+              summary: `Submit a manifest claiming ${id} for the current candidate.`,
+            },
+          ],
+        },
+        waivableCodes: [],
+        nonWaivableCodes: STRUCTURAL_CODES,
+      };
+    }),
+    // ── Defaulted ──
+    baseRef: "origin/main",
+    storageNamespace: "delivery-harness/",
+    reviewNeutral: [...DELIVERABLE_TREE_V1_NARRATION_SET],
+    recordNeutral: [{ prefix: "docs/reports/" }],
+    pathClassification: {
+      generated: [{ kind: "prefix", value: "generated/" }],
+      test: [{ kind: "glob", value: "**/*.test.ts" }],
+      lockfile: [{ kind: "glob", value: "**/package-lock.json" }],
+    },
+    sensitivePaths: [],
+    activationThreshold: 1,
+    agentEnvSignals: [],
+    ciPolicies: [],
+    ciPolicyEnvKey: "DELIVERY_HARNESS_CI_POLICY",
+    preparationWiringPaths: ["harness.config.ts"],
+    deliveryRecordPath: "docs/reports/delivery-record.json",
+    deliveryRecordVerification: { baseMovement: "stale" },
+  };
+
+  return defineHarnessConfig(input);
+}
+
+/** Repo-relative path of the vendored declaration this adapter reads. */
+export const KIT_REPO_CONFIG_PATH = "packages/conformance/vectors/context/repo-config.json";
+
+export function readKitRepoConfig(): KitRepoConfig {
+  const here = path.dirname(fileURLToPath(import.meta.url));
+  const file = path.join(here, "..", "vectors", "context", "repo-config.json");
+  return JSON.parse(readFileSync(file, "utf8")) as KitRepoConfig;
+}
+
+/** The kit's own configuration, loaded and validated. */
+export function loadKitRepoConfig(): HarnessConfig {
+  return adaptKitRepoConfig(readKitRepoConfig());
+}
+
+/**
+ * Which negative-space tokens a config has let in. Empty is the only correct
+ * answer for a config the kit is evaluated under.
+ */
+export function negativeSpaceViolations(config: HarnessConfig): readonly string[] {
+  const declared = JSON.stringify(config);
+  return KIT_NEGATIVE_SPACE.filter((token) => declared.includes(token));
+}

package/package.json

@@ -0,0 +1,24 @@
+{
+  "name": "@agent-delivery-harness/conformance",
+  "version": "0.1.0",
+  "type": "module",
+  "description": "delivery-evidence/1 conformance kit (89 golden vectors) and its generator",
+  "license": "Apache-2.0",
+  "engines": {
+    "node": ">=22"
+  },
+  "dependencies": {
+    "@agent-delivery-harness/kernel": "0.1.0"
+  },
+  "exports": {
+    ".": "./src/index.ts"
+  },
+  "files": [
+    "src",
+    "!src/**/*.test.ts",
+    "vectors",
+    "fixtures/repo-config-adapter.ts",
+    "LICENSE",
+    "NOTICE"
+  ]
+}