​

OneLink Platform Overview

​

Status

• document type: mixed overview
• source of truth for current implementation: code plus /platform/current-architecture
• source of truth for target direction: this page plus the linked planning docs

​

Current Implemented System

• a Rails monolith with Vue 3/Vite frontend surfaces inherited from the upstream base platform
• an account-scoped omnichannel support platform
• a system organized around Account, Inbox, ContactInbox, Conversation, and Message
• a product with CRM-adjacent primitives such as Contact, Company, Note, Label, and CustomAttributeDefinition
• an event-driven application with an inherited enterprise/ technical split, active Captain/AI, automations, integrations, and help center; for OneLink this split is technical rather than a separate product tier

​

Target Direction

• a shared communication and CRM foundation
• white-label and product-specific capabilities
• isolated domain zones such as healthcare and construction
• controlled compatibility with the upstream base

​

Target Layers

​

Layer Responsibilities

​

Upstream / Core

• keep compatibility with the upstream base where practical
• absorb upstream fixes and product updates
• avoid unnecessary hard forks

​

Shared Platform

• branding and product direction
• shared access model
• shared CRM behavior and future CRM entities
• shared integrations
• shared UI shell and patterns

​

Domain Zones

• domain-specific fields
• workflows and validations
• specialized screens and reports
• domain-specific vocabulary and lifecycle rules

​

Working Rule

• if a capability is needed by multiple domains, move it into the shared platform
• if a capability is needed by one domain only, keep it inside that domain zone
• if a need is specific to one tenant, prefer configuration before new shared code

​

Reading Guide

• current codebase structure: Current Architecture
• repository and repo-boundary map: Repository Map
• backend execution workflow for AI agents and contributors: Backend Agent Playbook
• backend feature blueprint: Backend Feature Template
• frontend stack and component sourcing rules: Frontend Implementation Guide
• frontend execution workflow for AI agents and contributors: Frontend Agent Playbook
• frontend dependency rules: Frontend Dependency Policy
• dashboard feature blueprint: Dashboard Feature Template
• UI conventions and token usage: Design Tokens And UI Conventions
• concrete implementation references: Implementation Examples Map
• verification guidance: Testing Strategy For Agents
• implementation sequence and build order: Implementation Roadmap
• current access and native entity rules: Domain Access Architecture
• target CRM shape: CRM Architecture
• target entity reuse rules: Entity Matrix
• target decision rules: Decision Matrix
• target domain profile direction: Domain Profiles

​

Key References

• Domain Access Architecture
• Current Architecture
• Repository Map
• Backend Agent Playbook
• Backend Feature Template
• Frontend Implementation Guide
• Frontend Agent Playbook
• Frontend Dependency Policy
• Dashboard Feature Template
• Design Tokens And UI Conventions
• Implementation Examples Map
• Testing Strategy For Agents
• Implementation Roadmap
• CRM Architecture
• Entity Matrix
• Decision Matrix
• Integrations Architecture
• Domain Profiles
• Development Guide