SHP Specification

SHP-PWIA-1.1

SHP Public Website & Information Architecture Specification v1.1

Superseded

SHP Public Website & Information Architecture Specification v1.1

This specification defines the required information architecture, publication model, discovery structure, presentation boundaries, qualification requirements and structural governance of the public Structured Hardening Project website.

Status: Active

Version 1.1 is a Minor amendment reconciling authority, dependency, lifecycle and publication metadata with current SHP governance.

The Specification Authority Registry lifecycle-vocabulary reconciliation inherited from v1.0 is complete. The permanent publication-governance reconciliation requirement remains outstanding.

No website architecture, certification mathematics, platform admission, verification semantics, cryptographic trust rules or certification outcome semantics are changed by this amendment.

The ODT identified below is the immutable normative publication artefact for this version. The rendered website page is a derived public representation and does not replace the normative artefact.

Normative artefact

Document: SHP-PWIA-1.1 Version: 1.1 Status: Active Authority: S7 — Tooling and Utility Specifications Publication date: 26 September 2026 Effective date: 26 September 2026

Download the immutable normative artefact

SHA-256

f1d16b5705c39bfe3094c2572d8151d8e544f280f71b024414a42e45c74a9ab8

Governing dependencies

  • SHP Charter v3.0
  • SHP Specification Authority Registry v2.1

Publication boundary

Publication of this specification does not establish platform support, certification-service availability, production qualification or signing authority.

Repository provenance

The repository object identified below is byte-identical to the normative publication artefact. Its SHA-256 digest matches the publication digest shown above.

View commit-bound repository object · View repository commit

Repository location and commit history provide provenance and traceability. They do not determine SHP normative authority, lifecycle status, platform support, or certification eligibility.