Core Platform Architecture
Growing nowGeneric, multi-tenant FamilySuite hierarchy and V1.4 operating model.
Next milestoneConsolidate approved architecture into a clean main branch.
A live programme view of the architecture, services, development stack and controlled delivery path. FamilySuite remains generic and configuration-driven; Ambala Arain Family is one implementation, AAFAQ its service arm, and Rishta Corner one service.
Evidence-weighted across architecture, native build, integration, staging and production readiness.
Railway deployment, custom domain and TLS successfully established.
Secure GitHub and Neon status integration.
Live evidence refreshes automatically with safe snapshot fallback.
Generic multi-tenant platform hierarchy and V1.4 direction established.
Radar runtime is live; core FamilySuite application deployment remains separate.
GitHub and Neon credentials pending; Railway live.
GitHub private-main protection remains dependent on GitHub support / plan capability.
Neon controlled fail/pass proof remains outstanding.
Do not mint ContactIDs until identity authority is resolved.
No production migration or live service cutover without parity and rollback evidence.
Live verification pending.
Awaiting live status.
Growing nowGeneric, multi-tenant FamilySuite hierarchy and V1.4 operating model.
Next milestoneConsolidate approved architecture into a clean main branch.
Growing nowFT-001 and FT-002 foundations exist in the stacked PR chain.
Next milestoneFT-003 only after stack close-out and separate approval.
Growing nowMapping and authority boundaries only.
Next milestoneResolve canonical issuance authority before any minting.
Growing nowRecognised as a core FamilySuite domain.
Next milestoneDefine executable domain contract after identity foundations.
Growing nowExisting Registration, Browse, Public Feed and inbox remain live authorities.
Next milestoneParity-first migration planning into FamilySuite.
Growing nowRBAC, inbox, APIs, queues, retention and provider model defined.
Next milestoneComplete ComSuite parity inventory before implementation.
Growing nowRecognised service domain within the generic platform.
Next milestoneDefine service contract when prioritised.
Growing nowFuture FamilySuite service domain reserved.
Next milestoneArchitecture only when authorised.
Growing nowPermission and approval principles span major components.
Next milestoneCanonical role matrix tied to executable services.
Growing nowPrivacy, audit, retention and safeguarding treated as platform controls.
Next milestoneExecutable audit contracts and automated tests.
Growing nowOperations Radar and read-only status service are deployed.
Next milestoneComplete live GitHub and Neon telemetry.
Growing nowRailway hosts the Operations Radar and secure telemetry service.
Next milestoneKeep core FamilySuite application deployment separately governed.
Business and platform components that form FamilySuite itself. These are distinct from hosting and database infrastructure.
Tenant, service configuration, shared contracts and native application foundations.
NATIVE BUILDShared native identity, contact and directory capabilities with governed identifier boundaries.
NATIVE BUILDNative Browse, Registration, Details, sharing, moderation and safeguarding services.
NATIVE BUILDProvider-neutral native communications orchestration, consent, suppression, audit and delivery controls.
NATIVE BUILDNative genealogy domain with PostgreSQL-backed data model and staged GEDCOM import architecture.
NATIVE BUILDCross-cutting native security, authorisation, audit and safeguarding controls.
NATIVE PLATFORM CONTROLInfrastructure that hosts, stores or executes FamilySuite. These platforms are replaceable implementation infrastructure, not FamilySuite business modules.
Relational database technology used by the native FamilySuite data layer.
DATABASE ENGINEManaged PostgreSQL infrastructure for development, disposable validation branches and governed database environments.
DATA INFRASTRUCTUREApplication hosting and deployment infrastructure for Radar and native FamilySuite services.
HOSTING INFRASTRUCTUREBuild, orchestration, QA, planning and operational-observability tools. Not FamilySuite business-runtime dependencies.
Programme orchestration, QA, planning and connected-stack delivery actions.
DELIVERY TOOLINGAuthoritative code, PRs, version history and release evidence.
SOURCE AUTHORITYAutomated CI, security, PostgreSQL assertions and Neon validation workflows.
CI / QAImplementation environment used where appropriate for authorised code work.
DEVELOPMENT TOOLPlanning and delivery-status mirror. GitHub remains technical authority.
PLANNINGBounded autonomous coding lane with evidence returned to Linear and GitHub.
CODING AGENTScheduled orchestration, recovery and independent verification for the delivery process.
CONTROL PLANERead-only operational telemetry for the Operations Radar. It is not a FamilySuite business service.
OBSERVABILITYVisual design, brand assets and concept prototyping only.
DESIGN TOOLReference documents and supporting development/operational material.
REFERENCE TOOLExisting temporary or predecessor systems retained only for continuity, migration, reconciliation or parity evidence.
Temporary Ambala Arain Family presentation layer retained during migration. Not part of native FamilySuite runtime.
LEGACY / MIGRATIONLegacy engine for temporary external services and controlled migration/reference only. Not a FamilySuite runtime dependency.
LEGACY / MIGRATIONLegacy source and operational ledger for temporary services, migration and reconciliation only. Not a FamilySuite runtime datastore.
LEGACY / MIGRATIONExisting communication authority retained until native Communication Centre parity and explicit cutover.
LEGACY / CUTOVERChannels and external services that FamilySuite may connect to through governed adapters.
External operational correspondence service, accessed through governed connectors or communication workflows.
EXTERNAL SERVICEExternal communication channel served through the native Communication Centre and provider adapters.
CHANNELPlanned capabilities not yet treated as current native runtime dependencies.
Governed interfaces between native modules and approved external systems.
FUTUREFuture omnichannel adapters under the native Communication Centre.
FUTUREPotential future analytics, product insight, errors and experimentation platform.
FUTURE