Skip to content

v0.1.0.dev4

Pre-release
Pre-release

Choose a tag to compare

@chaniri01 chaniri01 released this 16 Oct 10:44
· 59 commits to main since this release
087af94

Development prerelease of the common TRIAD Python library. Requires Python 3.12
or later; distributed under the MIT license.

This version provides original-JSON parsing, canonical v2 verdict admission,
named roster merging and validation, shared prompt rendering, output-carrier
extraction, agreement reduction and bounded asynchronous host callbacks. It also
includes safe roster diagnostics and transport-object shape validation. Codex,
Claude, Gemini CLI and AGY entries are configurable; native execution remains
owned by each consumer.

The canonical specification, common prompt assets and deterministic implementation
are maintained together in this repository. The public API and conformance maps
describe the implemented contracts and their limits.

Obtain the library

The release workflow attaches these assets after the tagged source passes native
macOS/Ubuntu verification with Python 3.12 and 3.14:

Use the library installation and source-build guide
to select and verify exact artifacts, install in an isolated environment and
check the installed API/bundles. See the API contract
and conformance map.
This package is distributed through GitHub Releases, not a Python package index.

Consumer integration and deployment remain independent. Release-notice PRs report
library changes and artifact links; they do not automatically adopt or install
the library in a host.

Consumer change list — dev4 (clarified 2026-10-22)

This section describes the already published dev4 package. The source is
087af94a7078de0ae9701fb057840b5492f51f66; the wheel SHA-256 is
c5bfdf10c4ce81f431ec7f77106e4d77b1556ac9c7b6b01bdb6616f988e8b2cc.
This clarification changes release notes only, not the tag, package version or assets.

  • Admission diagnostics: AdmissionError.field, schema .path and
    selected-required-only .missing provide structured, value-free diagnostic
    metadata. Keep refusal codes and invocation-binding checks intact.
  • Prompt provenance: render_review_clauses(..., with_manifest=True)
    optionally returns rendered text with an ordered clause-name/hash manifest.
    The default return remains text; host custody remains host-owned.
  • Separate roster stages: merge_roster validates defaults and override
    inputs and returns an independent merge; validate_resolved validates the
    final roster. The intermediate merge can be incomplete, so validate before
    consuming it. resolve_roster retains its validated-result behavior.
  • Roster diagnostics: RosterError.path, .missing and .document
    identify the selected schema failure and defaults/override/resolved stage.
    The path is a schema path, not an input index; anyOf can leave
    .missing=None. Fixed messages and first-error selection remain intact.
  • Transport shape: validate_transport_receipt and ReceiptError
    validate the parsed nested transport object. They do not establish truthful
    execution, invocation equality, current attempts or packet/receipt custody.

These additions do not change all-selected unanimous agreement. Keep
acceptance metadata required, including for informational entries; keep
legacy schema $id identities and exact bundle/provenance verification.
Native spawning, provider controls, host diagnostics and deployment remain
consumer responsibilities.

Post-release follow-up — not included in dev4

  • Issue #9:
    instance-location diagnostics remain optional and unimplemented. Do not assume
    an instance_path API or infer an input location from the schema path.
  • Issue #17 and
    issue #21:
    preserve existing schema identities and the acceptance contract pending any
    separately approved transition.
  • Issue #5:
    additional extraction boundaries remain held.
  • PR #20 proposes
    wording-only corrections; draft PR #22
    reconciles adoption status and records the release plan. Both are open as of
    2026-10-22 and are not changes to these release assets.

Host maintainer handoff

The inspected Codex, Claude and AGY manifests already record this exact dev4
source and wheel. No package refresh is required solely because of this notice.
Each host maintainer should review the relevant API/diagnostic behavior, make
needed adapter/test/documentation changes in its owning repository, and report
an implementation PR or evidence that no change is needed. Any later library
upgrade must use its own published version and verified manifest.

These handoffs convey changes and integration responsibilities. Each host owns
its implementation, verification, release and installation decisions.