Versions¶
Current status¶
| Component | Version | Status | Scope |
|---|---|---|---|
| Evidence Backbone and Research | v0.9.0 |
Stable publication baseline | Sources, claim compatibility, DI state of the art, PULSE and agenda with maturity preserved |
| Source candidate | v0.9.0-rc.1 |
Ratified, merged, deployed and promoted | Traceable source of stable release v0.9.0 |
| Previous bilingual portal | v0.8.2 |
Stable and historical | Spanish localization, business clarity and independent ES/EN search |
| Previous bilingual baseline | v0.8.1 |
Stable and historical | Complete ES/EN routes, localized interface and translation-drift gates |
| Source bilingual candidate | v0.8.1-rc.1 |
Ratified, merged, deployed and promoted | Traceable source of stable v0.8.1 |
| CDI-BoK governance | v0.2.0 |
Approved and normative | Architecture, authority, claims, brand and Sprint 0 |
| Technical portal | v0.3.0-rc.1 |
Integrated and deployed | MkDocs, navigation, CI/CD, checks and custom domain |
| Foundational core | v0.4.0 |
Stable | Constitution, CDI boundaries, glossary, domains and PULSE specification |
| Practice and evidence | v0.5.0-rc.1 |
Deployed candidate, not ratified | Catalog and first instrumented B2B case, without observed outcome |
| Learning experience | v0.6.0-rc.1 |
Ratified and deployed candidate | Outcome-oriented home, five modules and Decision Brief |
| Quality and measurement | v0.7.0-rc.1 |
Ratified and deployed candidate | Decision Quality, six lenses, anti-metrics and Measurement Record |
| Conversational patterns | v0.8.0-rc.1 |
Ratified, merged and deployed candidate | Five patterns, six anti-patterns, language, template and stopped B2B demonstration |
| Stable portal baseline | v0.8.0 |
Editorially and technically stable | Reproducible build, navigation, traceability, gates and authority boundaries |
The portal version does not automatically raise the doctrinal maturity of its content. Infrastructure, knowledge and evidence may evolve at different rates, but must remain traceable.
Current policy¶
- Stable releases require an immutable tag and GitHub Release.
- Candidates are traced through notes, changelog, manifest, PR, merge SHA, validation and deployment. They receive a tag only when the owner explicitly authorizes freezing them as an immutable prerelease.
- Ratification, deployment and stability are different states.
decision.javierforero.codisplays the latest merged public build; the portal version does not raise every document's authority or evidence strength.- Drafts do not appear in stable navigation.
- Spanish is canonical during
0.x; English translations are versioned and linked through a controlled parity registry.
ADR-022 replaces ADR-005's initial rule and avoids ambiguous retrospective
tags. governance/releases/index.yml preserves the complete lineage.
Historical RCs remain intentionally untagged; stable tags are created only by
their governed post-merge workflows. v0.9.0-rc.1 remains untagged as the
promoted source candidate for stable v0.9.0; the stable release does not
automatically raise the authority or evidential strength of its content.
Why there is no later v0.1.0
The initial roadmap named Sprint 2 as v0.1.0, but the sequence had already published v0.2.0 and v0.3.0-rc.1. ADR-014 assigned v0.4.0-rc.1; ADR-017 records its ratification and stable promotion to v0.4.0.
History¶
See CHANGELOG.md and the repository releases.