Skip to content

Releases

Raintree Standards v1.1.1

Choose a tag to compare

@admin-raintree admin-raintree released this 04 Sep 21:15
Immutable release. Only release title and notes can be modified.
5f68ad5

Fixes validation of the installed Codex plugin layout by excluding skill instructions from governed OKF content. No governed rule or maturity status changed.

Raintree Standards v1.1.0

Choose a tag to compare

@admin-raintree admin-raintree released this 04 Sep 20:54
Immutable release. Only release title and notes can be modified.
77bf14e

Adds status-aware dependency validation, deterministic profile routing, and the standards-navigator Codex packaging recipe. The catalog now contains 7 stable and 69 draft documents.

Raintree Standards v1.0.0

Choose a tag to compare

@admin-raintree admin-raintree released this 01 Sep 20:47
Immutable release. Only release title and notes can be modified.
7cb65c1

First stable release of the Raintree Standards library contract.\n\n- Establishes the catalog structure, stable rule IDs, task profiles, and automated validation.\n- Includes 515 rules across 74 governed documents.\n- Keeps document maturity explicit through status and review metadata; the library version does not certify each individual standard.\n- Adds AI-search guidance, llms.txt routing, canonical Markdown representations, content negotiation, schema guidance, and the expanded engineering standards corpus.

Raintree Standards v0.1.0-pre.1

Pre-release

Choose a tag to compare

@admin-raintree admin-raintree released this 30 Aug 21:50
Immutable release. Only release title and notes can be modified.
3f26d1b

First public pre-v1 checkpoint of Raintree Standards.

This prerelease contains an open-source library of testable requirements, task profiles, playbooks, templates, and verification routes for software, data, security, AI, product, and web work. It includes 73 governed documents, 487 rules, a software-testing standard and field guide, functional-writing guidance, integration capability bundles, and repository validation tooling.

Pre-v1 means document structure, routes, and requirements may still change. Use stable rule IDs when citing requirements and review the repository status before adopting them as policy.