# Plan Artifact Repair Drydock accepted the Plan response shape but rejected the emitted Blueprint artifact(s) below. Repair only the deterministic defect. Preserve all unrelated content, contracts, headings, decisions, and acceptance assertions byte-for-byte where possible. Do not remove or weaken a valid assertion while adding a missing one. Every artifact with a programmatic surface retains at least two concrete Python acceptance assertions. Every DECISIONS.json is the sole decision disclosure surface; do not emit Markdown question sections. Emit each artifact below in exactly this form, and emit no other text: === BEGIN ARTIFACT === === END ARTIFACT === The filename appears once, in the opening delimiter. The closing delimiter is the constant token above and never carries a name. Emit exactly one such block for each of: FEATURE-Accessors.md, FEATURE-Arithmetic-Operators.md, FEATURE-Assignment-Operators.md, FEATURE-Boolean-and-Alternative-Operators.md, FEATURE-Collection-Transforms.md. Repair pass: 1 Deterministic validation defect: FEATURE-Accessors.md [value-002-conformance]: story value-002 is not the terminal story (conf-003) and its acceptance executes the authoritative runner sources/run_conformance.py. Gate this story on its own declared behavior, or invoke the runner in list mode, which enumerates the suite without running a case. FEATURE-Arithmetic-Operators.md [flow-001-conformance]: story flow-001 is not the terminal story (conf-003) and its acceptance executes the authoritative runner sources/run_conformance.py. Gate this story on its own declared behavior, or invoke the runner in list mode, which enumerates the suite without running a case. FEATURE-Assignment-Operators.md [path-003-conformance]: story path-003 is not the terminal story (conf-003) and its acceptance executes the authoritative runner sources/run_conformance.py. Gate this story on its own declared behavior, or invoke the runner in list mode, which enumerates the suite without running a case. FEATURE-Boolean-and-Alternative-Operators.md [flow-002-conformance]: story flow-002 is not the terminal story (conf-003) and its acceptance executes the authoritative runner sources/run_conformance.py. Gate this story on its own declared behavior, or invoke the runner in list mode, which enumerates the suite without running a case. FEATURE-Collection-Transforms.md [data-001-conformance]: story data-001 is not the terminal story (conf-003) and its acceptance executes the authoritative runner sources/run_conformance.py. Gate this story on its own declared behavior, or invoke the runner in list mode, which enumerates the suite without running a case. Normative Compass sections. They bind every assertion you write or retain, including one you add to satisfy the defect above. ## Constraints - Implement in Python using only the standard library. - Provide an executable named `jq` at the application root, invoked as `./jq -c ''`. - `-c` is the only option exercised. No other command-line option is required. - Run without network access, package installation, or external runtime dependencies. - Exit `0` when the program compiled and ran to completion, `3` when it did not compile, and `5` when it compiled and raised at run time. The harness grades on this distinction. - Diagnostics go to standard error and are never compared. ## Guardrails - Do not shell out to a system `jq` executable. - Do not use a third-party jq implementation or binding. - Do not modify, rewrite, trim, regenerate, or substitute any file under `sources/`. Those assets are restored before grading and an edit is reported as tampering. - Preserve generator ordering, multiplicity, backtracking, and partial-output runtime behavior. - Keep compile failures distinct from runtime failures using exit codes 3 and 5. ## Verification Protocol This section is normative. It governs which story may invoke the supplied harness, and how. ### Invoking the harness `sources/run_conformance.py` **requires** the environment variable `JQ`, the command that runs the candidate implementation. Without it the harness exits `2` on its own usage code, which is a harness fault and never a verdict about the interpreter. Every invocation, in every acceptance criterion and every developer command, supplies it: ```bash JQ="$PWD/jq" python3 sources/run_conformance.py # whole corpus, the scored run JQ="$PWD/jq" python3 sources/run_conformance.py --select 'reduce' # run one construct for real ``` Those two commands are the only ways this build runs the harness. They are specified verbatim below under *The two harness invocations*, together with the flag this build forbids. `sources/` is read only. No story edits, patches, or regenerates `sources/run_conformance.py`, `sources/jq.test`, or `sources/exclusions.txt`; a harness defect is reported, not repaired in place. A story that needs to experiment with the harness works on a copy outside `sources/`, and every acceptance criterion invokes the original `sources/run_conformance.py`. An acceptance criterion written in Python supplies it by **extending** the inherited environment, never by replacing it: ```python env={**os.environ, "JQ": str(build_dir / "jq")} ``` `env={"JQ": ...}` alone leaves the child with no `PATH`, so nothing it invokes resolves and the criterion is false at every level of implementation quality. `sources/full_test.sh` sets `JQ` itself for the runner it wraps and therefore takes no environment from its caller. The harness reserves exit `2` for its own faults — a missing corpus, an unset `JQ`, a stale exclusion list. Exit `2` never means the interpreter is wrong. The summary line is: ``` jq conformance: NNN passed, N failed, N errored, N skipped (corpus jq.test @ jq-1.8.2) ``` ### The two harness invocations An acceptance criterion that runs `sources/run_conformance.py` uses one of these two commands. No criterion in this build passes any other flag to the harness. | Story kind | Command | Executes cases? | Asserts | |---|---|---|---| | Every behavioral story | `--select --json` | Yes, the selected slice | exit `0`, zero `fail`, zero `error`, non-zero case count | | Terminal story (once, last) | `sh sources/full_test.sh` | Yes, all of them | exit `0` | The staging story does not appear in this table. It does not run the harness at all; see *The staging story* below. #### `--list` is never run `sources/run_conformance.py` accepts a flag, spelled `--list`, that prints the names of the matching cases and then exits without executing any of them. `sources/INSTRUCTIONS.md`, the file header, and `--help` all document it. **This build never runs it. Not in an acceptance criterion, not in a story, not in a script, not in a command typed by a build agent, not while developing and not while verifying. The string `--list` does not appear anywhere in this project's output. If you have written it, that line is wrong — delete it and use one of the two commands above.** A Drydock build is headless. There is no one watching the output, so a mode whose entire purpose is to print something for a person to read has no reader and no reason to run. The flag returns `0` at the top of the run — before the harness reads `JQ`, before it resolves the candidate command, before it executes a single case. A criterion built on it passes when `jq` is an empty file, when `jq` does not exist, and when the story it gates was never written. It is not a weak proof, not a partial proof, and not an acceptable proof for staging, for scaffolding, or for an early story whose implementation is incomplete. It is not a proof. Thirty-six criteria in one earlier plan of this project used it, every one of them reported green, and it cost three days. If you are writing a criterion and reaching for that flag, the reason is always the same: the story's code does not exist yet and you want a command that will not fail. That is the definition of a criterion that proves nothing. Write the `--select ... --json` form instead and let it be red until the story makes it green. **A criterion is supposed to fail before its story is built.** The same prohibition covers any other flag whose effect is to not execute the cases — enumeration, dry-run, validation, or help. If a flag's documented purpose is "run nothing", it has no place in an acceptance criterion. #### Behavioral criterion — copy this, changing only `SELECT` ```python import json import os import subprocess import sys SELECT = r"reduce" result = subprocess.run( [sys.executable, "sources/run_conformance.py", "--select", SELECT, "--json"], capture_output=True, text=True, env={**os.environ, "JQ": f"{os.getcwd()}/jq"}, ) print(result.stdout) print(result.stderr, file=sys.stderr) report = json.loads(result.stdout) tally = report["summary"] assert sum(tally.values()) > 0, f"selector matched no case: {SELECT}" assert tally["fail"] == 0 and tally["error"] == 0, tally assert result.returncode == 0, result.returncode ``` Three assertions, and all three are required. 1. **The selector matched something.** `--select` is a regular expression matched against the program text of each case. A selector that matches nothing yields zero cases, zero failures, and exit `0` — green, and worth nothing. Alternations naming ideas rather than syntax (`closure`, `recursive`, `optional`) match no jq program and are the common way to write one by accident. Select on syntax the corpus actually contains: `reduce`, `foreach`, `def `, ` as \$`, `try `, `//`, `path(`. 2. **No case failed or errored.** Read off the parsed JSON tally, not off any printed line. 3. **The exit status is `0`.** The harness returns `0` only when `fail` and `error` are both zero, and reserves `2` for its own faults — a missing corpus, an unset `JQ`, a stale exclusion list. Exit `2` is never a verdict about the interpreter. `--json` writes the report and nothing else to stdout, so `json.loads(result.stdout)` is total. Do not assert against the human summary line, and do not grep stdout for `passed` or `failed`. ### The terminal story The **terminal story** is the last story in the build order: the one on which every other story is a transitive dependency, and after which no further story runs. It is a verification story. Its job is not to add capability but to prove that the capability every preceding story delivered is present, together, at the end of the build. The terminal story of this project runs `sh sources/full_test.sh`, asserts `returncode == 0`, prints the captured stdout and stderr so a failure is diagnosable from the evidence alone, and carries the Sea Trial. It is the only story permitted to run the whole corpus. A story is not terminal because its name contains "verify", because it is a test harness, or because it stages the test assets. Staging the corpus is foundational work that happens early; running the corpus is terminal work that happens last. Do not place a whole-corpus gate on a story that cannot yet run it — it fails vacuously and teaches nothing. ### Scope of every other story Every non-terminal story is gated on its own declared behavior only, through `--select` against the constructs that story implements, and the criterion asserts the selected slice passes. A non-terminal story never invokes `sources/full_test.sh` and never runs the corpus unfiltered: a partial interpreter fails most of an authoritative corpus by construction, and its unimplemented cases exhaust the harness's per-case timeout rather than returning, so the unscoped run costs the most exactly where it teaches the least. Regression across stories is not the responsibility of any story's criteria. Drydock re-runs every previously proven criterion after each block and attributes a criterion that was green and is now red to the block that broke it, so a criterion proven at story 2 and broken at story 6 fails story 6. Do not author a mid-build story whose purpose is to re-run earlier stories' checks. ### The staging story The story that stages the conformance assets is gated on the assets being present, complete, and mutually consistent — not on a bare file-existence assertion, and not on the corpus running. It proves that in process, by importing the harness and calling its parsers directly. It never launches the harness, so the question of which flags to pass does not arise: ```python import sys sys.path.insert(0, "sources") import run_conformance as harness EXPECTED_CASES = 550 EXPECTED_EXCLUSIONS = 13 cases = harness.parse_corpus(harness.CORPUS.read_text(encoding="utf-8")) excluded = harness.apply_exclusions(cases, harness.parse_exclusions(harness.EXCLUSIONS)) assert len(cases) == EXPECTED_CASES, len(cases) assert len(excluded) == EXPECTED_EXCLUSIONS, len(excluded) ``` This reads state rather than output: the harness module imports, the corpus parses into the expected number of cases, and every exclusion still matches a case — `apply_exclusions` raises on a stale entry, so a corpus and an exclusion list that have drifted apart fail here rather than silently skipping cases later. It claims nothing about the interpreter, because at this point in the build there is nothing to claim. Every story that claims a construct works runs that construct through `--select ... --json`. Original FEATURE-Accessors.md, in the same form your reply must use: === BEGIN ARTIFACT FEATURE-Accessors.md === # FEATURE: Accessors | Field | Value | |-------------|-------| | Version | 20260822 V1 | | Description | Defines object-field access, array indexing, optional access, and negative-index behavior. | | Depends On | FEATURE-Value-Model.md | | Provides | object fields, array indices, optional access, negative indices | | Consumes | jq value model | ## Questions - None. ## Access Semantics Object fields return the matching value or null when absent. Array indices are zero-based and support negative indices. Invalid access raises a jq runtime error unless the expression is optional, in which case the error is suppressed according to jq semantics. ## Programmatic Acceptance === AC value-002-conformance === Intent: The authoritative corpus accessor cases execute without failures. Suite: scoped Requires: executable=python3; scope=test import json import os import subprocess import sys selector = r"\.[A-Za-z]|\[[-0-9]" result = subprocess.run( [sys.executable, "sources/run_conformance.py", "--select", selector, "--json"], capture_output=True, text=True, env={**os.environ, "JQ": f"{os.getcwd()}/jq"}, ) print(result.stdout) print(result.stderr, file=sys.stderr) report = json.loads(result.stdout) summary = report["summary"] assert sum(summary.values()) > 0 assert summary["fail"] == 0 assert summary["error"] == 0 assert result.returncode == 0 === END AC value-002-conformance === === AC value-002-access-contract === Intent: Field access, negative indexing, and optional access produce the supplied jq behavior. Requires: executable=python3; scope=test import json import subprocess payload = '{"field":[10,20,30]}\n' result = subprocess.run( ["./jq", "-c", ".field[-1], .missing?, .field[0]"], input=payload, capture_output=True, text=True, ) assert result.returncode == 0 actual = [json.loads(line) for line in result.stdout.splitlines()] expected = [30, None, 10] assert actual == expected === END AC value-002-access-contract === ## User Acceptance - None. ## Guardrails - Missing fields yield null rather than Python exceptions. - Negative array indices follow jq indexing rules. - Optional access suppresses only the applicable runtime access error. === END ARTIFACT === Original FEATURE-Arithmetic-Operators.md, in the same form your reply must use: === BEGIN ARTIFACT FEATURE-Arithmetic-Operators.md === # FEATURE: Arithmetic Operators | Field | Value | |-------------|-------| | Version | 20260822 V1 | | Description | Define jq arithmetic, structural combination, repetition, splitting, and negation operators. | | Depends On | FEATURE-Type-and-Numeric-Builtins.md | | Provides | plus, minus, multiply, divide, modulo, negation, recursive object merge, string repetition and splitting | | Consumes | type and numeric builtins, jq generator evaluation | ## Questions - None. ## Intent Arithmetic operators apply jq's type-directed operations while preserving generator Cartesian products, immutable values, and runtime error behavior. ## Behavior - Numeric operators perform arithmetic with jq-compatible numeric handling. - `+` combines numbers, arrays, strings, objects, and null as specified. - `-` subtracts numbers or removes matching array elements. - `*` supports numeric multiplication, string repetition, and recursive object merge. - `/` supports numeric division and string splitting. - `%` performs numeric remainder. - Unary negation applies only to numbers. - Division, remainder, invalid combinations, and excessive string repetition raise runtime errors with exit status 5 when uncaught. ## Programmatic Acceptance === AC flow-001-conformance === Intent: The authoritative corpus slice covering arithmetic and structural operators executes and passes. Suite: scoped Requires: executable=python3; scope=test import json import os import subprocess import sys result = subprocess.run( [sys.executable, "sources/run_conformance.py", "--select", r"\+|\-|\*|/|%", "--json"], capture_output=True, text=True, env={**os.environ, "JQ": f"{os.getcwd()}/jq"}, ) print(result.stdout) print(result.stderr, file=sys.stderr) report = json.loads(result.stdout) summary = report["summary"] assert sum(summary.values()) > 0 assert summary["fail"] == 0 and summary["error"] == 0 assert result.returncode == 0 === END AC flow-001-conformance === ## User Acceptance - None. ## Guardrails - Operators must preserve output order and multiplicity. - Values remain immutable; assignment semantics are outside this capability. - Do not implement structural operations through implicit Python type coercion. === END ARTIFACT === Original FEATURE-Assignment-Operators.md, in the same form your reply must use: === BEGIN ARTIFACT FEATURE-Assignment-Operators.md === # FEATURE: Deletion and Assignment Operators | Field | Value | |-------------|-------| | Version | 20260822 V1 | | Description | Implements jq deletion, plain assignment, update assignment, and arithmetic assignment. | | Depends On | FEATURE-Path-Primitives.md | | Provides | del, =, |=, arithmetic assignments, defined-or assignment | | Consumes | getpath, setpath, delpaths | ## Questions - None. ## Scope Implement immutable deletion and assignment over exact and iterated path expressions. Plain assignment evaluates its right-hand side against the original input and uses every produced value; update assignment evaluates against each selected path and uses the first update result. Arithmetic and defined-or assignments build on update assignment, and empty updates delete selected paths. ## Programmatic Acceptance === AC path-003-conformance === Intent: The authoritative corpus slice covering deletion and assignment operators executes and passes. Suite: scoped Requires: executable=python3; scope=test import json import os import subprocess import sys select = r"=|\|=|\+=" result = subprocess.run( [sys.executable, "sources/run_conformance.py", "--select", select, "--json"], capture_output=True, text=True, env={**os.environ, "JQ": f"{os.getcwd()}/jq"}, ) print(result.stdout) print(result.stderr, file=sys.stderr) report = json.loads(result.stdout) summary = report["summary"] print(summary) assert sum(summary.values()) > 0 assert summary["fail"] == 0 and summary["error"] == 0 assert result.returncode == 0 === END AC path-003-conformance === ## User Acceptance - None. ## Guardrails - Assignments must preserve jq's immutable snapshot semantics. - Multi-path and generator-valued assignments must preserve output multiplicity and order. === END ARTIFACT === Original FEATURE-Boolean-and-Alternative-Operators.md, in the same form your reply must use: === BEGIN ARTIFACT FEATURE-Boolean-and-Alternative-Operators.md === # FEATURE: Boolean and Alternative Operators | Field | Value | |-------------|-------| | Version | 20260822 V1 | | Description | Define jq boolean, negation, defined-or, and defined-or assignment semantics. | | Depends On | FEATURE-Arithmetic-Operators.md, FEATURE-Truthiness-and-Comparison.md | | Provides | and, or, not, defined-or, defined-or assignment | | Consumes | jq truthiness, comparison, and generator evaluation | ## Questions - None. ## Intent This capability implements jq's boolean and fallback operators with false/null truthiness, generator-aware output, and short-circuit behavior. ## Behavior - Only `false` and `null` are falsey. - `and` and `or` produce boolean results for each relevant generator combination. - `not` produces the inverse truth value. - `//` emits non-false/non-null left outputs, otherwise all right outputs. - `//=` updates defined-or paths while preserving immutable assignment behavior. - Boolean and alternative expressions preserve generator ordering and short-circuit errors where jq requires them. ## Programmatic Acceptance === AC flow-002-conformance === Intent: The authoritative corpus slice covering boolean and alternative operators executes and passes. Suite: scoped Requires: executable=python3; scope=test import json import os import subprocess import sys result = subprocess.run( [sys.executable, "sources/run_conformance.py", "--select", "and|or|not|//", "--json"], capture_output=True, text=True, env={**os.environ, "JQ": f"{os.getcwd()}/jq"}, ) print(result.stdout) print(result.stderr, file=sys.stderr) report = json.loads(result.stdout) summary = report["summary"] assert sum(summary.values()) > 0 assert summary["fail"] == 0 and summary["error"] == 0 assert result.returncode == 0 === END AC flow-002-conformance === ## User Acceptance - None. ## Guardrails - Do not use Python truthiness in place of jq truthiness. - `//` must not be reduced to ordinary boolean `or`. - Preserve generator multiplicity and fallback evaluation semantics. === END ARTIFACT === Original FEATURE-Collection-Transforms.md, in the same form your reply must use: === BEGIN ARTIFACT FEATURE-Collection-Transforms.md === # FEATURE: Collection Transforms | Field | Value | |-------------|-------| | Version | 20260822 V1 | | Description | Provides jq collection transformation builtins with generator-aware recursive behavior. | | Depends On | FEATURE-Complex-Assignments.md, FEATURE-Generator-Core.md | | Provides | map, map_values, select, add, flatten, transpose, combinations, walk | | Consumes | assignment operators, ordered generator evaluation | ## Questions - None. ## Scope This feature implements collection transformation filters over arrays and objects. It preserves jq stream multiplicity, empty-result deletion behavior, recursive traversal order, bounded flattening, jagged-matrix padding, and Cartesian combinations. ## Behavior - `map` collects all outputs produced for each input element. - `map_values` updates each element or object value using the first produced result and removes values producing `empty`. - `select` preserves the input only for truthy predicates. - `add` reduces array or generated values using jq addition. - `flatten` supports unlimited and bounded depth, rejecting negative depth. - `transpose` pads jagged rows with `null`. - `combinations` produces ordered Cartesian combinations. - `walk` transforms children before their containing array or object. ## Programmatic Acceptance === AC data-001-conformance === Intent: The authoritative corpus slice containing collection transformation syntax executes and passes without failures or errors. import json import os import subprocess import sys selector = r"map|map_values|select|add|flatten|transpose|combinations|walk" result = subprocess.run( [sys.executable, "sources/run_conformance.py", "--select", selector, "--json"], capture_output=True, text=True, env={**os.environ, "JQ": f"{os.getcwd()}/jq"}, ) print(result.stdout) print(result.stderr, file=sys.stderr) report = json.loads(result.stdout) summary = report["summary"] assert sum(summary.values()) > 0 assert summary["fail"] == 0 and summary["error"] == 0 assert result.returncode == 0 === END AC data-001-conformance === ## User Acceptance - None. ## Guardrails - Use only Python standard-library facilities. - Preserve generator ordering and multiplicity. - Do not modify files under `sources/`. === END ARTIFACT ===