PHASE 01 SHIPPED
Foundation
Typed registry, reusable workbench contract, canonical routes, explicit error states, analytics vocabulary, and automated coverage.
Loading UtilityForge…
BLUEPRINT / PRODUCT ROADMAP
The product roadmap describes intended phases. It is not a list of existing APIs, tools, providers, or operational systems.
PHASE 01 SHIPPED
Typed registry, reusable workbench contract, canonical routes, explicit error states, analytics vocabulary, and automated coverage.
PHASE 02 SHIPPED
269 published local workbenches. Expansion continues only where repeated jobs, completion, and related actions justify the work — never to raise a count.
PHASE 03 SHIPPED
Five named providers behind fixed adapters, with freshness labels, provenance links, per-identity ceilings, and no arbitrary-request proxy.
PHASE 04 SHIPPED
HTTPS-only API playground with DNS pinning, redirect revalidation, and response redaction; a direct browser request builder; a provenance-first API directory that publishes nothing until evidence exists.
PHASE 05 SHIPPED
Email accounts with server-side sessions and PayPal subscriptions, with plan ids supplied by environment. Paid plans raise the live-data ceiling the server enforces and unlock the stored half of saved work; third-party advertising renders only when a publisher id is configured, and never on a paid plan — free pages otherwise carry labelled first-party Pro promotions only.
PHASE 06 SHIPPED
Sync is opt-in and stored on the account under transport encryption — not end-to-end encrypted, which the product does not claim. Favorites, recents, and run counts follow every signed-in plan; stored collections, presets, playground environments, and redacted request history come with Pro; shareable read-only collection links come with Business. Lists merge by union, preferences by newest write, counters by maximum, and a preset never carries a credential-shaped field.
PHASE 07 IN PROGRESS
An automated WCAG 2.2 AA rules engine audits every route and the whole stylesheet cascade (`pnpm a11y:audit`; the generated report is `docs/ACCESSIBILITY-AUDIT.md`) and fails the run when a checked rule regresses. The report prints each route's focus stops with the name each control exposes, which is the baseline for the six manual runs specified in docs/ACCESSIBILITY-MANUAL-PASS.md; their results table is still empty. No assistive-technology pass and no third-party certification exist yet, so no conformance claim is made.
PHASE 08 PLANNED
A verified API inventory with source snapshots, licence review, verification queues, and health scoring — this stays in beta until the records are useful.
OPERATING RULE
UtilityForge does not call a tool, provider, API record, verification process, or revenue channel implemented until the corresponding product behavior, documentation, and controls are actually in place.