# Standards and documentation governance

Availability: **Reference**  
Documentation: **1.1** | Updated: **19 September 2026**

[Documentation home](../README.md)

### S1 JSON Schema Draft 2020 12

[JSON Schema Draft 2020 12](https://json-schema.org/draft/2020-12)

Structural schema language used by the local task schema. Runtime constraints still apply.

### S2 RFC 8785 JSON Canonicalization Scheme

[RFC 8785 JSON Canonicalization Scheme](https://www.rfc-editor.org/rfc/rfc8785.html)

Candidate network canonicalization profile. This RFC is Informational, not Standards Track; the local reference does not implement it.

### S3 RFC 9457 Problem Details for HTTP APIs

[RFC 9457 Problem Details for HTTP APIs](https://www.rfc-editor.org/rfc/rfc9457.html)

Reference format for the proposed network error envelope.

### S4 RFC 8032 Edwards Curve Digital Signature Algorithm

[RFC 8032 Edwards Curve Digital Signature Algorithm](https://www.rfc-editor.org/rfc/rfc8032.html)

Ed25519 candidate signature algorithm. A complete Ocean6 profile still requires review and interoperability tests.

### S5 RFC 8174 and BCP 14 requirement language

[RFC 8174 and BCP 14 requirement language](https://www.rfc-editor.org/rfc/rfc8174.html)

Clarifies the uppercase requirement keywords defined by RFC 2119.

## Version policy

Maintain separate versions for documentation, protocol contracts, workload profiles and executable artifacts. A documentation revision records its reason and affected requirements. A protocol change records compatibility impact and migration behavior. Editorial improvements do not imply a new runtime capability.

## Publication requirements

Each developer page should state availability, applicable version and required prerequisites. A guide should include a runnable path and an expected outcome. A reference page should define fields, constraints and errors. An operational page should define evidence, failure handling and recovery.

Network specifications require engineering review before being described as stable. Promotion to a production contract requires an approved schema, deployed implementation, current operational ownership and linked acceptance evidence. If documentation and code disagree, classify and resolve the discrepancy openly; do not rewrite historical validation records.

This English edition is a technical review specification with an implemented local reference. It is suitable for engineering review and integration planning. Production readiness must be assessed against the release criteria, not the completeness of the document.

[Previous](./industry-references.md)