Backlog migration 2026 09 08
Owner-authorised metadata and Wiki migration only. No application source, feature PR, deployment, resource provisioning, provider registration, email activation, release or tag is part of this work.
Original due date: 2026-09-12T00:00:00Z. Superseded destinations: M0.x engineering/platform/delivery, M1.1 data/tenancy, M5.1 security and M5.4 Fides. Preserve and close this milestone; do not delete it. Existing closed PR associations remain historical and are not counted as open implementation issues.
Original description:
This milestone focuses on refactoring the core Luminatik fork to support logical tenant isolation across the Cloudflare edge stack. The priority is establishing strict data boundaries and internal routing before expanding user-facing features. Implement tenantId mapping across HTTP routes and authentication middleware. Enforce logical isolation in D1 database queries via tenant-aware application middleware. Implement Workers RPC for secure, internal service-to-service communication and tenant context passing. Refactor Durable Objects to isolate WebSocket connections and state coordination per tenant. Establish base testing protocols to verify cross-tenant data leakage prevention.
Original due date: 2026-09-19T00:00:00Z. Superseded destinations: M2.4 headless architecture; #17 to M5.4 privacy metadata. Preserve and close this milestone; do not delete it. Existing closed PR associations remain historical and are not counted as open implementation issues.
Original description:
This milestone transitions the frontend from an opinionated, coupled application into a set of agnostic, un-styled component primitives. The goal is to expose interaction logic while deferring visual rendering to the adopting developer's preferred design system (e.g., Tailwind, shadcn/ui, Ant Design). Strip out existing hardcoded CSS and opinionated layout frameworks inherited from Luminatik. Extract core helpdesk interactions (ticket creation, message threading, status toggling) into un-styled headless components or React hooks. Expose state management handlers for D1 eventual consistency (e.g., optimistic UI updates following write operations). Document component APIs and provide a minimal implementation example wrapping the primitives in a basic design system.
Original due date: 2026-09-26T00:00:00Z. Superseded destinations: M1.2 shared infrastructure, M1.4 transactional mail and M7.x adapters. Preserve and close this milestone; do not delete it. Existing closed PR associations remain historical and are not counted as open implementation issues.
Original description:
This milestone moves all communication channels into a dedicated, tenant-configurable settings interface and expands the inbound vectors beyond email and web forms. Create a centralized settings dashboard for tenants to manage and toggle channel integrations. Refactor existing channel ingestors to act as modular, optional plugins. Implement Cloudflare Calls (WebRTC) integration, using Durable Objects for signalling to enable in-browser video and audio support. Build webhook ingestors and dispatchers using Cloudflare Queues for Signal, WhatsApp, and LinkedIn messaging. Ensure background tasks (inbound message parsing, API dispatching) gracefully handle rate limits and retries for third-party networks.
Original due date: 2026-10-03T00:00:00Z. Superseded destinations: M0.4 production readiness; beta becomes a prerelease gate. RMM/audio/video/Signal/LinkedIn remain uncommitted proposals pending specifications. Preserve and close this milestone; do not delete it. Existing closed PR associations remain historical and are not counted as open implementation issues.
Original description:
This milestone completes the integration endpoints required for enterprise use cases, ensuring the system is ready for initial production deployments. Build API endpoints and webhook receivers for third-party Remote Management and Monitoring (RMM) tools. Automate the mapping of remote session IDs and diagnostic payloads to specific tenant tickets. Finalise deployment documentation, highlighting the zero-maintenance edge architecture and vendor lock-in trade-offs. Conduct an end-to-end security review focusing on pre-signed R2 URL lifecycles and Durable Object race condition handling.
| Issue | Original title | Original milestone | New title | New milestone | Status |
|---|---|---|---|---|---|
| #12 | v0.1.0: verify CI and align repository protection | v0.1.0 - Multi-Tenant Architecture Foundation | Verify required checks on dependency-only pull requests | M0.1 | OPEN preserved |
| #13 | v0.1.0: review the whole codebase for security vulnerabilities | v0.1.0 - Multi-Tenant Architecture Foundation | Review and remediate codebase security vulnerabilities | M5.1 | CLOSED preserved |
| #14 | v0.1.0: agree and implement coding standards | v0.1.0 - Multi-Tenant Architecture Foundation | Standardise repository formatting and lint conventions | M0.1 | OPEN preserved |
| #15 | v0.1.0: audit general codebase health and test coverage | v0.1.0 - Multi-Tenant Architecture Foundation | Audit codebase health and test coverage | M0.1 | CLOSED preserved |
| #16 | v0.1.0: inventory and implement majority FidesLang coverage | v0.1.0 - Multi-Tenant Architecture Foundation | Establish measurable FidesLang coverage | M5.4 | OPEN preserved |
| #17 | v0.2.0: complete FidesLang coverage and optional end-user capabilities | v0.2.0 - Headless UI Extraction | Complete FidesLang coverage and optional user controls | M5.4 | OPEN preserved |
| #18 | v0.3.0: replace Resend with Cloudflare-native email | v0.3.0 - Omnichannel Configuration & Expansion | Migrate transactional mail to Cloudflare-native delivery | M1.4 | OPEN preserved |
| #19 | v0.1.0: define tenant isolation and cross-tenant regression tests | v0.1.0 - Multi-Tenant Architecture Foundation | Complete tenant-isolation acceptance coverage | M1.1 | OPEN preserved |
| #20 | v0.1.0: verify contributor setup from a clean checkout | v0.1.0 - Multi-Tenant Architecture Foundation | Verify reproducible local contributor setup | M0.1 | OPEN preserved |
| #21 | v0.1.0: review dashboard and portal accessibility | v0.1.0 - Multi-Tenant Architecture Foundation | Validate accessibility of core operator and portal workflows | M2.1 | OPEN preserved |
| #22 | v0.1.0: complete repository settings and community launch | v0.1.0 - Multi-Tenant Architecture Foundation | Complete remaining repository launch administration | M0.1 | OPEN preserved |
| #42 | Phase 1 Production Migration & Cutover | v0.1.0 - Multi-Tenant Architecture Foundation | Validate production cutover and rollback readiness | M0.4 | OPEN preserved |
| #44 | v0.1.0: retire inactive legacy services without losing regression coverage | v0.1.0 - Multi-Tenant Architecture Foundation | Retire inactive services while preserving regression coverage | M0.1 | OPEN preserved |
| #45 | Evaluate deferred major dependency and Actions upgrades | v0.1.0 - Multi-Tenant Architecture Foundation | Evaluate deferred major dependency and Actions upgrades | M0.1 | OPEN preserved |
| #48 | Establish headless UI architecture: Ark UI, tenant CSS tokens, standalone app and Shadow DOM widgets | None | Establish shared headless primitives for standalone Tocyn | M2.4 | OPEN preserved |
| #49 | v0.3.0: Tocyn omnichannel architecture roadmap | v0.3.0 - Omnichannel Configuration & Expansion | Track delivery of the omnichannel architecture | None — cross-roadmap tracker | OPEN preserved |
| #50 | v0.1.0: establish system-wide Cost & Capacity governance | v0.1.0 - Multi-Tenant Architecture Foundation | Define enforceable cost policies and resource budgets | M0.2 | OPEN preserved |
| #51 | v0.3.0: establish shared omnichannel ingestion and delivery contracts | v0.3.0 - Omnichannel Configuration & Expansion | Implement authenticated durable webhook ingress | M1.2 | OPEN preserved |
| #52 | v0.3.0: extend tenant API and implement reliable signed outbound webhooks | v0.3.0 - Omnichannel Configuration & Expansion | Deliver signed tenant webhook subscriptions reliably | M1.2 | OPEN preserved |
| #53 | v0.3.0: implement tenant-owned Slack support channels | v0.3.0 - Omnichannel Configuration & Expansion | Implement tenant-owned Slack support channels | M7.3 | OPEN preserved |
| #54 | v0.3.0: implement tenant-owned Microsoft Teams support channels | v0.3.0 - Omnichannel Configuration & Expansion | Implement tenant-owned Microsoft Teams support channels | M7.4 | OPEN preserved |
| #55 | v0.3.0: implement tenant-owned WhatsApp Cloud API messaging | v0.3.0 - Omnichannel Configuration & Expansion | Implement tenant-owned WhatsApp messaging | M7.1 | OPEN preserved |
| #56 | v0.3.0: implement tenant-owned Telegram support messaging | v0.3.0 - Omnichannel Configuration & Expansion | Implement tenant-owned Telegram support messaging | M7.2 | OPEN preserved |
Closed #13/#15 retain their original bodies, discussions, PR/commit links and completion evidence. Open issues retain original bodies in an explicitly historical section; current ownership and dependencies are authoritative. No open issue is closed by this migration.
- #18 → #89
- #48 → #66, #67
- #50 → #64, #90, #93
- #51 → #59, #87, #88, #91, #76, #74
- #52 → #60, #88, #92
- #42 → #57, #65
- #22 → #57, #65
| Proposal reference | Actual issue | Outcome |
|---|---|---|
| N01 | #57 | Establish isolated preview and beta deployments |
| N02 | #58 | Provision isolated test tenants reproducibly |
| N03 | #59 | Map API and portal intake onto canonical conversation contracts |
| N04 | #60 | Make API and portal mutations validated and retry-safe |
| N05 | #61 | Validate authenticated portal conversations end to end |
| N06 | #62 | Validate human handling of canonical ticket intake |
| N07 | #63 | Record attributable ticket and conversation audit events |
| N08 | #64 | Enforce resource budgets across active application paths |
| N09 | #65 | Rehearse and publish the human-led private beta |
| N10 | #66 | Apply tenant themes through standard CSS variables |
| N11 | #67 | Package isolated helpdesk Web Components |
| N12 | #68 | Add a rich conversation composer |
| N13 | #69 | Add reusable responses and safe operator macros |
| N14 | #70 | Add typing awareness and private colleague collaboration |
| N15 | #71 | Enable keyboard-first workspace navigation |
| N16 | #72 | Split and merge tickets without losing context |
| N17 | #73 | Expose SLA progress and responsible handlers |
| N18 | #74 | Preserve conversations across verified channel changes |
| N19 | #75 | Enrich intake with authorised operational context |
| N20 | #76 | Add bounded triage and conversation summarisation |
| N21 | #77 | Expand the operator copilot with translation and runbooks |
| N22 | #78 | Author and publish governed diagnostic workflows visually |
| N23 | #79 | Enforce granular human and agent capabilities |
| N24 | #80 | Validate governed actions against an isolated reference API |
| N25 | #81 | Bind human approvals to specific proposed actions |
| N26 | #82 | Resolve reference-service tickets through bounded autonomous workflows |
| N27 | #83 | Transfer live agentic work safely to human operators |
| N28 | #84 | Review agent interactions through auditable QA workflows |
| N29 | #85 | Report operational performance and quality metrics |
| N30 | #86 | Expose authorised deterministic self-service actions |
| N31 | #87 | Normalise provider events into reliable conversation state |
| N32 | #88 | Dispatch transactional outbound intents reliably |
| N33 | #89 | Enable verified canonical support-email conversations |
| N34 | #90 | Expose owner and tenant Cost & Capacity controls |
| N35 | #91 | Recover accepted payloads through durable storage journals |
| N36 | #92 | Attach bounded telemetry to programmatic support intake |
| N37 | #93 | Enforce private-beta resource guardrails |
Authenticated Project discovery is blocked because the available GitHub token lacks read:project. No existing Project has been positively identified/accessed, so none is edited and no replacement is created. This is the sole known access limitation; issue/milestone scheduling is recorded here and in issue bodies.
Current architectural schedule.
Read-back verification passed: 32 architectural milestones; four historical milestones superseded with original dates/descriptions retained; 22 existing titles renamed; 23 existing issues reassigned; 37 new issues (#57–#93) mapped exactly once; 125 native blocked-by relationships; 14 native tracker children; exact 12 beta blockers. #49 has no milestone. All 58 future issues remain open; #13/#15 remain closed with their original bodies and discussions unchanged. No duplicate issue titles or N-reference mappings were found. All approved milestone dates and dependency sets match.
Beta blockers: #19, #20, #21, #57, #58, #59, #60, #61, #62, #63, #65 and #93. One new beta-blocker label was created; relevant labels were applied and help wanted retained on #53–#56. Thirteen existing issues received label changes.
The application repository remains clean at 8ddd00ba7548f48ba4d461198adabb59fdd54a9e; branches, PR heads/states, tags and releases match the pre-migration snapshot. No application code, deployment, Cloudflare resource, provider setup or mail activation was changed by this migration. No automated reviewer was invoked. Project updates remain the sole access limitation described above.
- System-architecture
- Architecture-and-tenant-isolation
- Channels-and-conversation-model
- AI-and-autonomous-operations
- Architecture-decision-records