Make ATS-1 draft.3 the new-authoring default

CHANGELOG.md

@@ -8,6 +8,12 @@ the imported normative package is a separate, receipted import, never an edit in
 
 ## [Unreleased]
 
+### Changed — draft.3 authoring cutover candidate
+
+- New durable authoring and the checked-in fleet policy now resolve ATS-1 `1.0.0-draft.3`; legacy unlabeled interpretation remains draft.1 and explicit version pins still win.
+- Public authoring/review skills carry the draft.3 version law and D-G behavioral acceptance-criterion boundary.
+- Canonical public skill bytes changed, so the generated skill-pack candidate advances to `0.1.4`; the published release remains `0.1.3` until separately tagged/released.
+
 ### Proposed — draft.3 acceptance-criterion hardening
 
 - Added `docs/ATS_1_DRAFT_3_AC_HARDENING.md`, a prospective normative delta that

README.md

@@ -36,7 +36,7 @@ Use ATS to write the implementation specification for this change.
 ```
 
 The `ats` front door chooses the right public skill. New durable authoring uses
-ATS-1 `1.0.0-draft.2`, the result stays readable as prose, and the local runtime
+ATS-1 `1.0.0-draft.3`, the result stays readable as prose, and the local runtime
 performs deterministic checks. [Install ATS](#install) or
 [jump straight to the four skills](#the-four-skills).
 
@@ -277,8 +277,8 @@ export PATH="$HOME/.local/bin:$PATH"
 ats spec status
 ```
 
-`ats spec status` should list both `1.0.0-draft.1` and
-`1.0.0-draft.2`. Restart an already-running agent once so it discovers the new
+`ats spec status` should list `1.0.0-draft.1`, `1.0.0-draft.2`, and
+`1.0.0-draft.3`. Restart an already-running agent once so it discovers the new
 skills.
 
 ### 3. Ask for the artifact

config/policies/fleet_policy.json

@@ -1,10 +1,10 @@
 {
   "schema_version": "ats.fleet_policy.v1",
-  "policy_id": "39a2e495346135ba9b03fe5b593a424ee73a73d282af214205f8a4097920a1f2",
+  "policy_id": "65ec7b601ab37111970dd720101beec1870830ac28b832095ff2fd5d810dadeb",
   "created_at": "2026-08-07T00:00:00Z",
   "text_policy": {
     "standard": "ATS-1",
-    "version": "1.0.0-draft.2",
+    "version": "1.0.0-draft.3",
     "required_for": [
       "architecture",
       "technical_proposal",

dist/skill-pack/agent-plugins/plugin.json

@@ -11,5 +11,5 @@
   ],
   "license": "Apache-2.0 AND CC-BY-4.0",
   "name": "ats-skill-pack",
-  "version": "0.1.3"
+  "version": "0.1.4"
 }

dist/skill-pack/agent-plugins/skills/ats-assess/SKILL.md

@@ -57,13 +57,13 @@ the CLI, schemas, and checks named below are the complete execution surface.
 
 ## Version behavior
 
-- New durable authoring resolves ATS-1 `1.0.0-draft.2` under the binding
+- New durable authoring resolves ATS-1 `1.0.0-draft.3` under the binding
   policy (which pins the edition; no `--spec-version` override unless the user
   passes one).
 - Legacy/historical material (corpus, annotation bench, unlabeled older
   artifacts) is interpreted under `1.0.0-draft.1` unless migration is explicit.
-- A draft.2 artifact under a draft.1 policy is a **refusal**, never a silent
-  downgrade; a draft.1 artifact must not silently acquire draft.2 semantics.
+- A draft.3 artifact under a draft.1 policy is a **refusal**, never a silent
+  downgrade; a draft.1 artifact must not silently acquire draft.3 semantics.
 
 ## Authoring vs transformation
 

dist/skill-pack/agent-plugins/skills/ats-review/SKILL.md

@@ -128,7 +128,7 @@ Regression fixtures demonstrating all three live at `fixtures/skills/review/` (m
 ## Version behavior
 
 - Reviewing arbitrary prose claims nothing about ATS conformance and resolves no standard version.
-- If the user requests an ATS conformance review, resolve the standard version by the two-default law: new durable authoring under the binding policy resolves to `1.0.0-draft.2`; legacy/historical material resolves to `1.0.0-draft.1` unless migration is explicit; an explicit version wins; a draft.2 artifact under a draft.1 policy is a refusal, never a silent downgrade.
+- If the user requests an ATS conformance review, resolve the standard version by the two-default law: new durable authoring under the binding policy resolves to `1.0.0-draft.3`; legacy/historical material resolves to `1.0.0-draft.1` unless migration is explicit; an explicit version wins; a draft.3 artifact under a draft.1 policy is a refusal, never a silent downgrade.
 - If the user's environment has a policy, `ats policy resolve` decides applicability and version; the review follows it.
 
 ## Deterministic machinery
@@ -177,7 +177,7 @@ An ATS artifact under a resolved policy can produce a deterministic BLOCK:
 
 ```text
 BLOCK — deterministic conformance failure
-Artifact: spec.md (ATS-1 1.0.0-draft.2, policy resolved)
+Artifact: spec.md (ATS-1 1.0.0-draft.3, policy resolved)
 Check: ats ir lint — IR-STRUCT-014 (requirement block missing actor)
 Span: REQ-004 "Jobs are retried on failure."
 

dist/skill-pack/agent-plugins/skills/ats-spec/SKILL.md

@@ -108,7 +108,7 @@ do not pad every unit with every slot, and do not drop a slot that is material.
 - non-goals — what this artifact explicitly does not address;
 - failure behavior — what happens when the behavior fails;
 - proof obligations — what must be demonstrated, and by whom;
-- acceptance criteria — falsifiable evidence obligations;
+- acceptance criteria — canonical falsifiable behavioral propositions; tests, probes, proofs, and receipts are evidence used to adjudicate them, not the criteria themselves;
 - update/reversal conditions — when the artifact or its decisions may change;
 - unresolved state — typed as such, never guessed.
 
@@ -140,8 +140,14 @@ Acceptance:
   after restart, accepted-but-unconsumed mail remains recoverable.
 ```
 
-The requirement declares the desired invariant; the acceptance converts it into a
-falsifiable evidence obligation. Do not "fix" the overlap by deleting either side.
+The requirement declares the desired invariant; the acceptance states the canonical
+falsifiable behavioral proposition. Tests, probes, proofs, or receipts are subordinate
+evidence used to adjudicate that proposition. Do not "fix" the overlap by deleting either side.
+
+For each normative REQ/AC pair, ask one adversarial question: **could a materially broken
+implementation satisfy this AC as written?** If yes, strengthen the AC or decompose the REQ.
+The AC must not compensate by adding an independent obligation, widening scope, or strengthening
+deontic force; normative behavior belongs in the REQ.
 
 ## Local semantic closure
 
@@ -187,11 +193,11 @@ Basis vocabulary at a glance (mechanics live in the internal authoring skill, no
 
 ## Version behavior
 
-- New durable authoring resolves ATS-1 `1.0.0-draft.2` under the binding policy. The
+- New durable authoring resolves ATS-1 `1.0.0-draft.3` under the binding policy. The
   policy pins the edition — no `--spec-version` override is needed.
 - Legacy / historical material stays `1.0.0-draft.1` unless migration is explicit.
-- A draft.2 artifact under a draft.1 policy is a refusal, never a silent downgrade.
-- A draft.1 artifact must not silently acquire draft.2 semantics.
+- A draft.3 artifact under a draft.1 policy is a refusal, never a silent downgrade.
+- A draft.1 artifact must not silently acquire draft.3 semantics.
 - An explicit `--spec-version` always wins.
 
 ## Procedure (standalone)
@@ -273,7 +279,7 @@ Dependency: clock synchronization within 100 ms.
 
 ```text
 AC-1  On a clean install, `ats spec status` prints the imported edition and exits 0.
-AC-2  A draft.2 IR linted under a draft.1 policy exits non-zero with a refusal —
+AC-2  A draft.3 IR linted under a draft.1 policy exits non-zero with a refusal —
       never a silent downgrade.
 ```
 

dist/skill-pack/agent-plugins/skills/ats/SKILL.md

@@ -80,6 +80,11 @@ execution surface.
 9. Acceptance evidence is not the same discourse role as the requirement it verifies.
 10. Ask only when unresolved meaning blocks the requested action.
 
+Draft.3 `SPECIFY` refinement: an acceptance criterion is the canonical falsifiable
+behavioral proposition for its REQ. Tests, probes, proofs, and receipts are evidence
+used to adjudicate that proposition, not substitutes for it; if a materially broken
+implementation can satisfy the AC, strengthen the AC or decompose the REQ.
+
 ## How to route
 
 ### Step 1 — Determine the mode
@@ -126,13 +131,13 @@ which enforcement gates apply.
 
 Two defaults, never collapsed into one:
 
-- **New durable authoring** resolves ATS-1 `1.0.0-draft.2` under the binding
+- **New durable authoring** resolves ATS-1 `1.0.0-draft.3` under the binding
   policy. The policy pins the edition; no `--spec-version` override is needed.
 - **Legacy / historical material** stays `1.0.0-draft.1` unless migration is
   explicit.
 - An explicit `--spec-version` always wins.
-- A draft.2 artifact under a draft.1 policy is a **refusal**, never a silent
-  downgrade. A draft.1 artifact must not silently acquire draft.2 semantics.
+- A draft.3 artifact under a draft.1 policy is a **refusal**, never a silent
+  downgrade. A draft.1 artifact must not silently acquire draft.3 semantics.
 
 ### Step 6 — Route to the right skill
 
@@ -159,22 +164,22 @@ identifies the installed layout.
 ```text
 "Use ATS to write an architecture proposal for this change."
 → new authoring · ASSESS + SPECIFY composition · ats-spec + ats-assess,
-  architecture recipe · 1.0.0-draft.2
+  architecture recipe · 1.0.0-draft.3
 
 "Use ATS to turn these design notes into an implementation specification."
-→ transformation · SPECIFY · ats-spec, implementation program recipe · draft.2,
+→ transformation · SPECIFY · ats-spec, implementation program recipe · draft.3,
   source semantics never strengthened
 
 "Review this existing RFC with ATS."
 → review mode · ats-review (BLOCK / REVIEW_REQUIRED / ADVISORY) · no conformance
   claim unless the user requested ATS conformance
 
 "Convert this incident analysis into an ATS postmortem."
-→ transformation · ASSESS · ats-assess, postmortem recipe · draft.2,
+→ transformation · ASSESS · ats-assess, postmortem recipe · draft.3,
   what-happened stays separate from why-we-believe-it
 
 "Use ATS for this technical assessment."
-→ new authoring · ASSESS · ats-assess · draft.2, uncertainty preserved
+→ new authoring · ASSESS · ats-assess · draft.3, uncertainty preserved
   (UNAVAILABLE is valid output)
 ```
 
@@ -187,7 +192,7 @@ identifies the installed layout.
    decides applicability when one is present).
 4. Select `ASSESS`, `SPECIFY`, or a declared composition.
 5. Resolve the standard version correctly — the two-default law above.
-6. Use draft.2 for new durable authoring.
+6. Use draft.3 for new durable authoring.
 7. Preserve draft.1 interpretation for historical material unless migration is
    explicit.
 8. Route to the selected public skill (`ats-spec`, `ats-assess`, or
@@ -244,7 +249,7 @@ merely because none exists — record `authority_precedence = UNAVAILABLE`.
 ```text
 User:  "Use ATS to write an architecture proposal for this change."
 Route: new authoring · ASSESS + SPECIFY · ats-spec + ats-assess ·
-       architecture recipe · 1.0.0-draft.2
+       architecture recipe · 1.0.0-draft.3
 Outcome:
   - ASSESS half: current state (observation), constraints, alternatives,
     judgment, unresolved points — each role preserved.
@@ -265,7 +270,7 @@ Outcome:
   - The source's causal claims remain causal *claims* — no observation is
     upgraded, no recommendation becomes a requirement.
   - A causal factor the source does not establish: UNAVAILABLE, not a guess.
-  - Edition reported as draft.1; never silently re-interpreted under draft.2.
+  - Edition reported as draft.1; never silently re-interpreted under draft.3.
 ```
 
 ### 3. Review stays review
@@ -286,7 +291,7 @@ Outcome:
 
 - Never force ATS onto casual prose, scratch notes, marketing, or exploratory chat.
 - Never collapse the two defaults into one global standard version.
-- Never let a draft.2 artifact silently downgrade to draft.1.
+- Never let a draft.3 artifact silently downgrade to draft.1.
 - Never dump TextIR, basis records, rule-registry, or receipt-schema internals into ordinary user output.
 - Never claim conformance the deterministic checks did not establish.
 - Never ask a human for a non-blocking unknown — type it `UNAVAILABLE` and continue.

dist/skill-pack/claude/ats-assess/SKILL.md

@@ -57,13 +57,13 @@ the CLI, schemas, and checks named below are the complete execution surface.
 
 ## Version behavior
 
-- New durable authoring resolves ATS-1 `1.0.0-draft.2` under the binding
+- New durable authoring resolves ATS-1 `1.0.0-draft.3` under the binding
   policy (which pins the edition; no `--spec-version` override unless the user
   passes one).
 - Legacy/historical material (corpus, annotation bench, unlabeled older
   artifacts) is interpreted under `1.0.0-draft.1` unless migration is explicit.
-- A draft.2 artifact under a draft.1 policy is a **refusal**, never a silent
-  downgrade; a draft.1 artifact must not silently acquire draft.2 semantics.
+- A draft.3 artifact under a draft.1 policy is a **refusal**, never a silent
+  downgrade; a draft.1 artifact must not silently acquire draft.3 semantics.
 
 ## Authoring vs transformation
 

dist/skill-pack/claude/ats-review/SKILL.md

@@ -128,7 +128,7 @@ Regression fixtures demonstrating all three live at `fixtures/skills/review/` (m
 ## Version behavior
 
 - Reviewing arbitrary prose claims nothing about ATS conformance and resolves no standard version.
-- If the user requests an ATS conformance review, resolve the standard version by the two-default law: new durable authoring under the binding policy resolves to `1.0.0-draft.2`; legacy/historical material resolves to `1.0.0-draft.1` unless migration is explicit; an explicit version wins; a draft.2 artifact under a draft.1 policy is a refusal, never a silent downgrade.
+- If the user requests an ATS conformance review, resolve the standard version by the two-default law: new durable authoring under the binding policy resolves to `1.0.0-draft.3`; legacy/historical material resolves to `1.0.0-draft.1` unless migration is explicit; an explicit version wins; a draft.3 artifact under a draft.1 policy is a refusal, never a silent downgrade.
 - If the user's environment has a policy, `ats policy resolve` decides applicability and version; the review follows it.
 
 ## Deterministic machinery
@@ -177,7 +177,7 @@ An ATS artifact under a resolved policy can produce a deterministic BLOCK:
 
 ```text
 BLOCK — deterministic conformance failure
-Artifact: spec.md (ATS-1 1.0.0-draft.2, policy resolved)
+Artifact: spec.md (ATS-1 1.0.0-draft.3, policy resolved)
 Check: ats ir lint — IR-STRUCT-014 (requirement block missing actor)
 Span: REQ-004 "Jobs are retried on failure."
 

dist/skill-pack/claude/ats-spec/SKILL.md

@@ -108,7 +108,7 @@ do not pad every unit with every slot, and do not drop a slot that is material.
 - non-goals — what this artifact explicitly does not address;
 - failure behavior — what happens when the behavior fails;
 - proof obligations — what must be demonstrated, and by whom;
-- acceptance criteria — falsifiable evidence obligations;
+- acceptance criteria — canonical falsifiable behavioral propositions; tests, probes, proofs, and receipts are evidence used to adjudicate them, not the criteria themselves;
 - update/reversal conditions — when the artifact or its decisions may change;
 - unresolved state — typed as such, never guessed.
 
@@ -140,8 +140,14 @@ Acceptance:
   after restart, accepted-but-unconsumed mail remains recoverable.
 ```
 
-The requirement declares the desired invariant; the acceptance converts it into a
-falsifiable evidence obligation. Do not "fix" the overlap by deleting either side.
+The requirement declares the desired invariant; the acceptance states the canonical
+falsifiable behavioral proposition. Tests, probes, proofs, or receipts are subordinate
+evidence used to adjudicate that proposition. Do not "fix" the overlap by deleting either side.
+
+For each normative REQ/AC pair, ask one adversarial question: **could a materially broken
+implementation satisfy this AC as written?** If yes, strengthen the AC or decompose the REQ.
+The AC must not compensate by adding an independent obligation, widening scope, or strengthening
+deontic force; normative behavior belongs in the REQ.
 
 ## Local semantic closure
 
@@ -187,11 +193,11 @@ Basis vocabulary at a glance (mechanics live in the internal authoring skill, no
 
 ## Version behavior
 
-- New durable authoring resolves ATS-1 `1.0.0-draft.2` under the binding policy. The
+- New durable authoring resolves ATS-1 `1.0.0-draft.3` under the binding policy. The
   policy pins the edition — no `--spec-version` override is needed.
 - Legacy / historical material stays `1.0.0-draft.1` unless migration is explicit.
-- A draft.2 artifact under a draft.1 policy is a refusal, never a silent downgrade.
-- A draft.1 artifact must not silently acquire draft.2 semantics.
+- A draft.3 artifact under a draft.1 policy is a refusal, never a silent downgrade.
+- A draft.1 artifact must not silently acquire draft.3 semantics.
 - An explicit `--spec-version` always wins.
 
 ## Procedure (standalone)
@@ -273,7 +279,7 @@ Dependency: clock synchronization within 100 ms.
 
 ```text
 AC-1  On a clean install, `ats spec status` prints the imported edition and exits 0.
-AC-2  A draft.2 IR linted under a draft.1 policy exits non-zero with a refusal —
+AC-2  A draft.3 IR linted under a draft.1 policy exits non-zero with a refusal —
       never a silent downgrade.
 ```