Axiom v0.10.1 — GPT-5.4 validation unavailable

Warning

GPT-5.4 publication validation is unavailable for the frozen codex-core-v2 / gpt-5.4 / ChatGPT authentication combination. Full-profile publication validation is incomplete.

Each of the two release attempts ended with the first case UNKNOWN and the remaining sixteen NOT-RUN. Only the second attempt has a confirmed HTTP 400 model/authentication rejection; the first attempt's cause remains undetermined because its error text was not retained.

The maintainer accepts this disclosed release gap for v0.10.1 only. This release does not claim 17/17 PASS. The attached status/exception record is not a passing observation or a test-pass proof.

gpt-5.4 will no longer be used for new Axiom maintenance runs. The benchmark and historical contracts in this existing tag have not been rewritten or migrated, and no replacement model is validated by this release. This is not a claim that the entire Axiom product is unavailable.

Single-version release exception

This Release uses the existing GitHub-signed commit 79be4a893549c9b8e390f416cb5f8dad1739493e, tree b921cbc1e29d8ded5652fc6f93cdd7c8c20ef986, and unchanged v0.10.1 tag. The maintainer's exception replaces only this version's 17/17 business acceptance condition and the two standard proof assets that depend on it. Signatures, tag integrity, actual permissions, immutability and data protection are not waived. Future versions retain their own validation requirements; the generic validators and historical results are unchanged.

No passing codex-core-v2 observation or standard Axiom release-evidence attestation is supplied. The sole attached JSON records the validation status and exception. Any GitHub-native release attestation establishes release/asset integrity only, not model acceptance. GitHub Latest identifies the maintainer's selected release; it does not certify complete validation.

Fixed

• Clarified six canonical Skill discovery descriptions: compound requests retain prerequisite order, and mutually exclusive architecture or installation scopes require one clarification. Existing routes and action authority are unchanged.
• Advanced both manifests and the full-profile runtime identity for this compatible correction. Derived no-Hook packages bind the corrected canonical source; prior packages and observations retain their original identities and outcomes.
• Separated clarification before a material Git workflow choice from necessary questions after that workflow is selected. Plugin architecture or installation choices remain pending after asking, without a same-reply default based on read-only authority or current feasibility.
• Pinned historical builder regression inputs and clarified the shared front-door measurement definition. The no-Hook observer uses a supported native environment-context setting with unchanged read permissions and separately bound observations.

Behavioral impact

Descriptions expose existing ordering and ambiguity boundaries during native Skill discovery. Original case requests, classifications, expected routes and scoring are unchanged. Hooks and their wrappers are unchanged. Static validation and version-specific host observations remain distinct evidence categories.

Required action

None. See the v0.10.1 release notes for migration and compatibility evidence boundaries.

Preserved evidence limits

Integration uses separately bound no-Hook evidence, not a new 16/16 batch. A11 remains benchmark FAIL for execution 16c13a3056a463149d93080cdd9f6102f31b8a3f, result cbab9b393bc19801d4ceaae7bbf29b4669509d2064bc206e9c5bff9b5267477a. Only its no-route/unavailable classification difference was accepted; exact distinction between missing discovery and an available catalog with no match is not promised, and no other failure receives that waiver.

B13's limited PASS retains the selection and public reading of Skill guidance before the business-choice question, followed by a pending business workflow. It is not evidence that no Skill was selected before clarification or a native loading receipt. A5's complete intermediate messages, historical failures, and the scoped R4/FCR and R5 host limitations remain as disclosed in Field Validation. Historical documents at the frozen tag retain their original pre-publication state; this Release and its status attachment record the present exception.

Cumulative canonical attempts / observation CLI starts remain 135/135. This publication adds zero model observations, probes, installations or authentication handoffs. Internal model requests remain unknown and all prior observation windows remain closed.

Status attachment: axiom-v0.10.1-validation-status-dcae3e8e94a425e51fe46bab0b631284f3cb3aea537de118322943e0fd1f7a6d.json. SHA-256: dcae3e8e94a425e51fe46bab0b631284f3cb3aea537de118322943e0fd1f7a6d. This is the sole uploaded asset; no compatibility ZIP or standard PASS proof is included.