Verbara — Roadmap

Status: SCAFFOLD — structure is ready; the priorities and dates marked ⟨NEEDS PRODUCT-OWNER INPUT⟩ must be set by Harol. Every OpenSpec proposal’s roadmap_ref frontmatter should link to a line item here, so specs trace back to a strategic priority.

Last updated: 2026-06-22 | Horizon owner: Harol

How to use this file

Each item gets a stable anchor id (e.g. R-001) so specs can reference it via roadmap_ref.
Status: now (in flight) · next (committed, not started) · later (intended) · shipped.
When an item ships, mark it shipped with the release tag; do not delete it (append-only).

Now (in flight)

⟨NEEDS PRODUCT-OWNER INPUT⟩ — Confirm current committed work. From repo state as of 2026-06-22, the Typification train and per-tenant BYO-LLM work were the most recent active threads; verify what is genuinely now vs already shipped before listing.

id	Item	Repos	Status	Notes
R-001	⟨set⟩		now

Next (committed)

⟨NEEDS PRODUCT-OWNER INPUT⟩

id	Item	Repos	Target	Notes
R-010	⟨set⟩		⟨Qx⟩

Later (intended)

⟨NEEDS PRODUCT-OWNER INPUT⟩ — Candidates surfaced by the audit that need a product call: cloud/SaaS offering, target-segment scope decisions, deferred channel/feature work.

id	Item	Repos	Notes
R-100	⟨set⟩

Shipped (recent — verify against CHANGELOGs)

Authoritative shipped history lives in each repo’s CHANGELOG.md, docs/decisions/ (ADRs), and docs/plans/completed/. This is a cross-repo digest only; reconcile before relying on it.

Release	Repo	Summary
⟨tag⟩