docs(roadmap): decouple forward direction from versions; re-theme Now to adoption#153
Merged
Merged
Conversation
… to adoption Closing the 0.8-cycle PR (#151) left the roadmap on `main` crowning `audit --fail-on-no-sbom` as the active frontier and marking *Later* empty — both now stale. #140 (SBOM on both copy + rebuild paths) means every freshly-placed image already carries an SBOM, so the gate only guards pre-unification backfill and regressions; it is no longer a headline. This restates the forward view by *direction, not version*: - Intro: the frontier is adoption (making the mandate demonstrable to a target org), and forward direction lives in Now/Deferred/Later decoupled from release tags — a version is cut when a real increment lands, but the roadmap always shows the heading. - Now: re-themed to "make the mandate demonstrable (adoption)" — the end-to-end CVE-to-owner blast-radius story on the reference deployment (the XZ loop + bypass blind spot already ship; the owner/runtime join and migration-parity narrative remain). The gate is demoted to a minor backfill-guard line. Notes that per-team fan-out is a policy `destinations` list, so houba replaces registry replication (which strips OCI referrers). - Later: populated with the developer coverage portal (Backstage TechInsights + an off-the-shelf SBOM/vuln platform) as the consumption surface — design captured, implementation Later, thesis-true (houba stamps, the portal consumes). No model change ⇒ no docs/reference drift. Co-Authored-By: Claude <noreply@anthropic.com>
The version-decoupling edit re-themed Now to adoption but dropped the docs-polish work that was scoped for the cycle. Adoption has two faces — a demonstrable end-to-end story and a self-serve docs surface — so restore the polish pass under the same theme: architecture presentation, richer examples, inline C4 diagrams, fenced runnable code blocks, and the readable-schema rendering item (kept as its own line since the renderer swap carries risk). Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Closing the 0.8-cycle PR (#151) removed the proposed roadmap edit, but left the roadmap on
mainstale in two ways:audit --fail-on-no-sbomas the active frontier / sole lever — which feat: unify SBOM generation on syft — both paths, SPDX + CycloneDX #140 (SBOM on both copy + rebuild paths, merged) hollowed out: every freshly-placed image now already carries an SBOM, so the gate only catches pre-unification backfill and regressions.(empty)despite a real standing directional bet.The fix is not "add a 0.8 section" — it's to make the forward view honest and version-agnostic. Now/Deferred/Later is exactly that tool; we were using it to point at a dissolved feature and an empty horizon.
What changed (
docs/roadmap.md, prose only)destinationslist, so houba replaces registry replication (which strips OCI referrers) rather than chaining behind it.No model change ⇒ no
docs/reference/drift. Generic throughout (no org-specific references).🤖 Generated with Claude Code