Roadmap and releases

Roadmap and releases

Tocyn separates architecture, work, readiness and releases:

• architecture/capability completion → GitHub milestones M0.x–M9.x;
• implementation work → GitHub issues and dependencies;
• release readiness → cross-cutting labels such as beta-blocker;
• deployable snapshots → SemVer Git tags and GitHub Releases.

Version-number milestones (v0.1.0, v0.2.0, v0.3.0, v0.4.0) were superseded on 8 September 2026 and remain historical only.

Architectural phases

Phase	Focus
M0	Engineering quality, cost/capacity and delivery environments
M1	Core data model, intake, ticket-feed validation and transactional mail
M2	Human workspace, productivity, real-time state and design system
M3	Context aggregation, triage/summarisation and operator AI assistance
M4	Tool boundaries, autonomous reference resolution and human handoff
M5	Authorisation, audit/oversight, analytics, privacy and workflow administration
M6	Portal/service-user experience, SLA, cross-channel continuity, deterministic self-service
M7	WhatsApp, Telegram, Slack, Teams and support-email integrations
M8	Realtime support sessions, browser media, telephony and recording
M9	Linked work, knowledge, applets, feedback/reporting and Access

Full milestone membership and target dates are maintained on Approved-architectural-roadmap. The integrated revision and open acceptance work are maintained on Current-delivery-status.

First private beta

Accepted application: 049ea82a02571681f834bcd87d43253603edf71f. v0.4.0-beta.1 was accepted on 9 September 2026 and formally published on 10 September 2026, with PR #125 as repository evidence. It was local-only synthetic API/portal/operator acceptance with local mail capture; no remote application deployment occurred.

Future candidate: v0.4.0-beta.2, gated by the Operator Workspace acceptance, including full SLA clocks/calendars/pause/resume/waiting semantics and responsible- handler ownership/routing (#73/#137). Production/cutover #42 remains separate.

Purpose: prove the core multi-tenant API/portal conversation flow with human operators and isolated test tenants. Slack, full support email and autonomous customer-backend resolution are not first-beta prerequisites unless future implementation evidence requires a roadmap change.

The authoritative beta-blocker set is the GitHub beta-blocker label, not this prose page.

Release convention

Use SemVer prerelease tags such as v0.4.0-beta.1, v0.4.0-beta.2 or v0.4.0-rc.1 only for actual tested snapshots. Do not mechanically increment a version because an architectural milestone closed.

No production deployment date is currently committed.

The original alignment forecast was beta.2 acceptance on 18 February 2027 and expanded scope on 9 February 2028; retain those values as history. The current accepted forecast ledger records the earlier 22 January 2027 and 21 January 2028 forecast, after evidenced completion was incorporated in PR #171. This is the same conservative two-workstream model, not a new baseline or a release promise. No further date change is inferred from the partial work described below. The owner-approved review policy uses zero default Copilot/automated review requests and a standing owner PR bypass only after required checks; required checks and security evidence remain mandatory.

Living schedule

After accepted #48 integration, the same conservative model recalculates beta.2 to 23 January 2027 and expanded scope to 11 January 2028. The two-lane scheduling order accounts for the one-day beta movement; original baselines remain immutable. The updated reproducible ledger is included with the ongoing #129 delivery record.

After accepted #129 completion on11September, the same model forecasts beta.2 on 18 January 2027 and expanded scope on 5 January 2028. These are current forecasts, not changed baselines or promises of provider availability. The original #129 forecast is preserved alongside its actual completion.

Project planning preserves baseline dates separately from forecasts and actual dates. Reforecasting must not overwrite the original approved baseline. See ADR-0014 and repository AGENTS.md.

Historical delivery snapshot — 10 September 2026

This section preserves the 10 September evidence. For current delivery state, see Current-delivery-status.

Beta.2 is not ready. Accepted main is 32fba86fd659ca9d729ff8d0ff683b4770e81454.

• #48 / PR #167 is accepted: retained shared controls, public TypeScript contracts, security/retry recovery, corrected built-widget styles, scoped browser/VoiceOver evidence and numeric performance gates. Exact-revision CI/security passed; the verified signed merge tree matches the reviewed head and CI runner. Owner review-only bypass was recorded, with zero Copilot reviews. Themes (#66), wrapper lifecycle (#67) and the persistent workspace (#128) retain separate acceptance.

• #159 / PR #170 merged as a partial foundation after required checks and a verified signed integration. Privacy-safe local diagnostics, bounded resource accounting, credential decisions and canonical mutation summaries are on main. #159 remains open for full active-path coverage and remaining runtime evidence; production telemetry stays disabled under #42. The owner-authorised review-only bypass was recorded; no independent human approval or Copilot review is claimed.

• #129 / PR #173 was the partial foundation at signed33dfe0b. PR #174 completes #129 at signeda412734: selected-ticket/context-panel and list view/filter/sort preferences, server-side stable sorting, and owner-approved48-hour local draft retention. Required CI/security pass and reviewed/CI/merge trees match. The expanded browser receipt covers draft/mode/attachment and preference restoration plus failed-save navigation/retry, using Node application routes and real Miniflare storage; this is not deployed/workerd application evidence. Cleanup is local-only and preserves attachment objects. Full #128 layout, #130 future work-view predicates and #131 durable send idempotency remain separate requirements. Owner review-only bypass recorded; zero Copilot requests and no production or beta.2 release claim.

Issue receipts, Project status and each branch's .agents/state/ provide current operational details; this dated snapshot does not replace their acceptance records. The workspace, full SLA clocks/calendars/waiting/pause behavior and ownership/routing remain mandatory before #140 can accept beta.2. No new release or remote deployment has occurred. Zero routine Copilot reviews; required validation remains mandatory.