Version and scope¶
Preparation only: 1.5.1 is unpublished. Use the published 1.5.0
guide for an installation today. The reviewed development
source is 0f2711b4c88ee4f231f61d71cd70a0c840be6357; the final release source
and artifact have not been selected.
The changelog places the maintenance changes after published 1.5.0: exact plugin-signature input validation, readable completed-assessment evidence, clearer setup and workflow guidance, and stronger documentation and continuation checks. Read the draft release notes and current readiness record. These documentation links use the reviewed release-preparation revision; the runtime source above remains distinct.
Full Windows parity remains deferred. Hosted Server software checks do not qualify Windows 11 desktop, all shell journeys, complete storage/recovery acceptance or live native-memory reliability. Native planning and building remain experimental. Browser forms save and review intent; they do not build.
Prepare installation and candidate validation¶
Keep Harness separate from Attune AI and preserve older evidence environments. Python 3.10 or later is required. Installing the runtime does not install a Claude Code plugin or Codex skill; follow the selected host's setup separately.
For validation before publication, obtain the explicitly selected candidate wheel and its source/hash record from the release owner. In a fresh environment, replace the example path with that reviewed local wheel:
python3 -m venv .venv
source .venv/bin/activate
python -m pip install /absolute/path/to/attune_harness-1.5.1-py3-none-any.whl
python -c "from importlib.metadata import version; print(version('attune-harness'))"
python -m attune_harness
attune-harness --help
Expected: version 1.5.1, a verified deterministic arithmetic receipt and the
command catalog. The example makes no model call and measures no model quality.
A metadata-only validation wheel can check preparation instructions, but it does
not establish the final release artifact. The selected final-wheel replay and
qualification remain release gates.
After publication, a managed CLI installation can use
uv tool install 'attune-harness==1.5.1', followed by uv tool list --show-paths
and attune-harness --help. For Python API use, install the published version
with pip in its own environment instead. Do not run these 1.5.1 index-install
commands before publication. Index delivery must be checked after release;
that delivery check does not replace candidate validation before release.
Windows setup uses py -3 -m venv .venv and
.\.venv\Scripts\python.exe for Python commands. This is reference syntax,
not a new Windows shell qualification. Keep task records outside checkouts
used for file effects and use canonical absolute paths.
Choose a useful next step¶
Attune AI is deprecated. Use Harness for new work; 1.5.1 is the intended replacement and remains in preparation. Before changing an existing setup, read the current migration guide. Preserve working environments while you validate the journeys you need. Deprecation does not qualify saved-work migration or complete host or Windows parity. The separate historical reference preserves the original 1.0.0 baseline.
Start with What do you want to accomplish?: 21 goals and six testing FAQs with prompts, instructions, expected outputs and review points. The learning category comes first. For command shapes and ordered handoffs, use AI tools and integrations.
Preparing a request, saving answers, accepting intent and authorizing execution are separate decisions. The local goals worksheet records proposed wording; it does not accept a spec, dispatch a model or implement the example app.
Inspect completed assessment evidence¶
For an existing completed document assessment, replace TASK with its saved
task directory and inspect:
attune-harness status TASK --format markdown
attune-harness status TASK --format html > assessment-report.html
Open the generated HTML report. Both formats present the accepted goal and criteria, recorded checker outcomes, retrieved-source identities and separately attributed participant judgments. A successful status command does not mean the assessment passed. Inspection does not rerun checks, refresh evidence or establish semantic acceptance. Other profiles and incomplete assessments keep their existing presentation. This addition is absent from published 1.5.0.
Read the inspection procedure.
Evidence and older versions¶
The preparation record identifies the current source and open artifact gate. The published 1.5.0 verification record retains the original environment, walkthrough outcomes and limits. The goals screenshots also remain explicitly 1.5.0 observations; illustrative examples are labeled separately.
The seven task guides were updated from 1.3.0 to published 1.5.0 before this preparation pass. Their original observation records are preserved. Review of 1.5.1 source is distinct from a final versioned-wheel replay and from independent user acceptance. Historical candidate tutorials remain historical.
Before website publication, reconcile the selected release commit, validate its exact candidate artifact, complete the release approval and verify index delivery. Then refresh the export from the reviewed merged Help source. A draft source or publisher PR does not authorize publication.