One name. One current public ULTRA release. Several historical artifacts.
PBHP-ULTRA v0.9.5 is the supplied public release and says it supersedes every earlier PBHP-ULTRA version. Historical prose, working specifications, code, tests, and website tools keep their own identities; none may silently borrow v0.9.5 status.
The field manual keeps the explanation visible.
Read the argument, numbered procedure, worked cases, failure contrasts, and evidence state behind this chamber.
The current public line
Current status is declared by the exact artifact—not by a nearby page, filename, test count, or larger version number from another line.
CURRENT PUBLIC ULTRAPBHP-ULTRA v0.9.5
The supplied document labels itself “Version: 0.9.5 (Public Release)” and says it supersedes all previous PBHP-ULTRA versions.
+
PBHP-ULTRA v0.9.5
The supplied document labels itself “Version: 0.9.5 (Public Release)” and says it supersedes all previous PBHP-ULTRA versions.
A distribution should bind the exact v0.9.5 bytes, checksum, release source, and correction state. The label does not establish safety, efficacy, legal compliance, certification, independent validation, or permission to deploy.
INTERNAL SKEWForward-labeled v0.9.6 passages inside the supplied v0.9.5 file
The v0.9.5 document contains several passages labeled v0.9.6. They are visible version skew, not evidence that a separate v0.9.6 public release has been admitted here.
+
Forward-labeled v0.9.6 passages inside the supplied v0.9.5 file
The v0.9.5 document contains several passages labeled v0.9.6. They are visible version skew, not evidence that a separate v0.9.6 public release has been admitted here.
Until the maintainer publishes an exact reconciled artifact, receipts should name the exact v0.9.5 file and disclose this internal labeling conflict rather than silently upgrading or deleting it.
HISTORICAL LINESv0.7-era prose, internal v1 snapshots, code, and test ledgers
Earlier materials remain useful for history, migration, and evidence attribution, but are not the current PBHP-ULTRA public release.
+
v0.7-era prose, internal v1 snapshots, code, and test ledgers
Earlier materials remain useful for history, migration, and evidence attribution, but are not the current PBHP-ULTRA public release.
Their version numbers and test counts describe their own artifacts and environments. They cannot be combined into a fictional aggregate version or validation claim.
What changes require a new version
A semantic change is more than edited copy; it changes what the protocol asks, binds, permits, records, or refuses.
MAJORAuthority or gate behavior
Change to thresholds, absolute floors, step order, provenance meaning, challenge rights, or required ownership.
+
Authority or gate behavior
Change to thresholds, absolute floors, step order, provenance meaning, challenge rights, or required ownership.
Major changes require migration guidance, regression tests, adversarial review, updated examples, and an explicit statement about how old receipts are interpreted.
MINORNew module or compatible field
Adds an optional or backward-compatible check, template, domain mapping, or evidence field.
+
New module or compatible field
Adds an optional or backward-compatible check, template, domain mapping, or evidence field.
Minor does not mean unimportant. If an 'optional' field becomes operationally required or changes the action, it is major in effect and should be versioned honestly.
PATCHClarification without changed behavior
Corrects wording, references, display, or examples while preserving the same decision contract.
+
Clarification without changed behavior
Corrects wording, references, display, or examples while preserving the same decision contract.
A patch note should explain why the change is non-semantic. Corrections to a public claim remain visible rather than being silently overwritten.
Website and workbench boundary
This website explains, teaches, and preserves material. It does not mint a protocol version or silently become the canonical implementation.
WEBSITEExplanatory public surface
The chamber pages consolidate concepts for reading and navigation.
+
Explanatory public surface
The chamber pages consolidate concepts for reading and navigation.
Edited website copy is not automatically a PBHP specification change. When this site and the exact v0.9.5 artifact differ, the site must disclose the difference rather than imply conformance.
WORKBENCHSimplified local teaching matrix
The public workbench loads fictional examples and exports unsigned local records.
+
Simplified local teaching matrix
The public workbench loads fictional examples and exports unsigned local records.
It is not PBHP-ULTRA v0.9.5, a canonical runtime, a conformance test, a signed receipt, or evidence that a real action is permitted. Clear the worked example before entering a custom case.
RECONCILIATIONBind future claims to exact artifacts
Version, date, hashes, schema, thresholds, tests, change log, license, maintainer, and known divergences belong together.
+
Bind future claims to exact artifacts
Version, date, hashes, schema, thresholds, tests, change log, license, maintainer, and known divergences belong together.
Independent reproduction, external challenge, field evidence, and maintained adoption evidence must remain separate from creator-led or model-assisted checks.
A protocol name is not an artifact identity. Every consequential receipt names the exact policy and runtime that governed it.