Task Contract Checker

Turn acceptance criteria and evidence references into an explicit completion report.

Version: 1.0.0. License: MIT. Status: tested reference baseline; no comparative ranking is claimed.

Contract

Require a nonempty outcome and at least one uniquely identified criterion. A criterion is proven only when it has evidence, every result passes, and every evidence reference is nonempty. Unknown criterion references are errors. Return complete plus each criterion status in input order.

The exact required input fields and types are in input.schema.json. Extra fields are rejected at declared object boundaries. JSON duplicate keys and non-finite numbers are rejected by the CLI. Input strings are case-sensitive unless stated otherwise. Array order is preserved unless the contract specifies sorting.

Use

Unpack the ZIP, enter its directory, and run:

python3 baseline.py < example.input.json
python3 -m unittest -v

Python 3.10 or newer, standard library only. The reference implementation exposes run(input_dict) and accepts one JSON object on standard input. Success returns {"ok": true, "result": ...} with exit code 0. Invalid input returns {"ok": false, "error": "..."} with exit code 1. example.output.json contains the result without the CLI envelope. Import callers receive exceptions for invalid input.

Example input

{
  "outcome": "Publish a guide",
  "criteria": [
    {
      "id": "live",
      "description": "Guide is readable"
    }
  ],
  "evidence": [
    {
      "criterion_id": "live",
      "reference": "receipt:42",
      "passed": true
    }
  ]
}

Example result

{
  "complete": true,
  "criteria": [
    {
      "id": "live",
      "proven": true,
      "references": [
        "receipt:42"
      ]
    }
  ]
}

Boundaries

References are recorded assertions. The checker does not inspect external evidence or judge whether criteria adequately describe the requested outcome.

This package performs no network calls, executes no submitted commands, and writes no user files. Host applications own authorization, resource budgets, and persistence. Example values are fixtures, not recommended policies or limits.

Acceptance and provenance

cases.json records named expected results and rejection cases. test_baseline.py runs those cases and checks the command-line contract. manifest.json records file digests. The specification, implementation, and evidence are separate files so a replacement implementation can target the same contract.

Original code and examples generated for this Arcomm collection. No third-party code is bundled. Read LICENSE for reuse terms.

Download

Download the file

SHA-256: 09752f82e2136592d68c5e832c12cbddfd59d6e5a47ee449019eed7bd194a274

Size: 6938 bytes.

Revisions

Revision history