# Roadmap Ledger

> Check a developer platform's public roadmap as the promise ledger customers, competitors and your own sales team
> treat it as - before you publish it. Answer a short interview and paste the roadmap items with their phase, date,
> category and status; the browser ranks the six publication postures, runs every item through the exclusion gate,
> caps every date with a release phase, finds silent removals and shipped items never closed, and ranks the feedback
> surface. Metered runs write the roadmap policy, and the slip notices. Built on the SkillSafe skill
> @samber/public-roadmap-strategy, from samber/developer-platform-skills (MIT), by Samuel Berthe.

https://roadmap-ledger.skillsafe.ai/

## What is free
- The postures: a horizon roadmap (the default), a direction page, no public roadmap, customer briefings under NDA, an interactive board, dated quarters - ranked with the moves your interview causes. Every public posture is deleted while sales promise unbuilt features and leadership will not sign the citation rule; dated quarters only when release phases exist, few committed items slipped, buyers plan around your dates and finance reviewed revenue recognition.
- The item gate: security work, unannounced deprecations, pricing and packaging, partner names and M&A, competitive bets, customer-specific commitments and internal plumbing kept off the page.
- The dates and lifecycle: a date without private preview or later is a bare date; removed items with no state, shipped items with no changelog link, stale items, solution-named items and community proposals that read as plans; contracts that name roadmap items; a board nobody triages.
- The gates: the citation rule signed, nothing excluded public, every date capped by a phase, no silent removal, a named owner with a cadence; plus a public ledger draft, an items CSV, the checks (.csv) and everything (.json).

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (policy or slips), `company`, `items`, `carry` (slips only: the policy's decisions) and `facts`.
- `policy` replies with `summary`, `posture`, `vocabulary`, `gate`, `guardrails`, `feedback`, `lifecycle` and `caveats`.
- `slips` replies with `summary`, `slips` (each slipped item with its status, reason, workaround, who to notify and whether a contract customer hears first) and `caveats`.
The page holds every reply to its own facts: the ranked posture and vocabulary family, every gated item in order, a disclaimer and at least three citation rules, the feedback surface and the owner as given; every slipped item in the page's order, never deleted.

## Links
- API tutorial: https://roadmap-ledger.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/public-roadmap-strategy