FamilySuite Operations Radar

FamilySuite is growing as one connected family platform.

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.

LIVE RADARTelemetry connecting--

38%evidence-weighted integrated release progress

Verified delivery activity

Connecting

Waiting for live evidence.

Last verified activity: --

Linear: --GitHub/CI: --Neon: --Railway: --

Architecture85%Design and platform boundaries

Native Build45%Executable native foundation

Integration25%Database and cross-service integration

Staging20%Deployed end-to-end staging

Production Readiness15%Migration, rollback and live gates

Overall38%

Evidence-weighted across architecture, native build, integration, staging and production readiness.

✓

Last verified milestoneDurable control plane verified

GitHub Actions lanes A-E and the Railway control-plane runtime are green; ChatGPT reduced to supervisory Orchestrator + Watchdog.

→

Next critical milestoneTelemetry

Secure GitHub and Neon status integration.

RefreshEvery 5 minutes

Live evidence refreshes automatically with safe snapshot fallback.

Architecture workstream85%

Generic multi-tenant platform hierarchy and V1.4 direction established.

Runtime foundation65%

Radar runtime is live; core FamilySuite application deployment remains separate.

Telemetry servicesPartial

GitHub and Neon credentials pending; Railway live.

Decisions required

Owner decisions

None right now

Current blockers

Delivery blockers

Native FamilySuite application is not yet deployed end-to-end to its governed staging environment.

PR #14 persistence and PR #15 Communication Centre remain draft/unmerged while integration evidence is consolidated.

Main-branch protection cannot currently be administered through the connected GitHub integration; CI and PR gates remain compensating controls.

Top risks

Guardrails

Do not mint ContactIDs until identity authority is resolved.

No production migration or live service cutover without parity and rollback evidence.

Core workstreams12 tracked

Native RC PRsCurrent candidates

Live GitHub telemetry determines the current draft/unmerged set.

GitHub telemetryConnecting

Awaiting live status.

FS-01Advanced

Core Platform Architecture

85%

Growing nowGeneric, multi-tenant FamilySuite hierarchy and V1.4 operating model.

Next milestoneConsolidate approved architecture into a clean main branch.

FT-003In progress

Family Tree

40%

Growing nowPostgreSQL genealogy foundation exists and FT-003 lossless GEDCOM staging is active with synthetic-only safeguards.

Next milestoneComplete lossless parser/import staging, provenance and re-import verification before any real GEDCOM use.

IDIn progress

Identity / ContactID

25%

Growing nowIdentity, Contacts and Directory discovery is active; ContactID, AFM, Rishta ID and service identifiers remain deliberately separate authorities.

Next milestoneComplete executable membership and identity contracts before any production identifier minting.

DIRIn progress

Rishta

60%

Growing nowNative Browse/Register contracts, exact 10-field public projection, PostgreSQL persistence and controlled request/share foundations now exist in the RC path.

Next milestoneIntegrate PostgreSQL-backed parity and synthetic end-to-end Browse, Register, Details and Secure Share flows.

COMNative implementation

Communication Centre

75%

Growing nowPR #15 implements the provider-neutral Recipients → Message → Review & Send flow with synthetic consent, suppression, safeguarding, audit, idempotency, queue/retry and provider adapters.

Next milestoneIntegrate PR #15 with PostgreSQL persistence and native staging, then prove synthetic end-to-end delivery and recovery.

BLDPlanned

Blood Bank

10%

Growing nowRecognised service domain within the generic platform.

Next milestoneDefine service contract when prioritised.

DNAFuture

DNA

Growing nowFuture FamilySuite service domain reserved.

Next milestoneArchitecture only when authorised.

RBACExecutable foundation

Admin / RBAC

60%

Growing nowTenant/service actor membership and executable authorisation foundations are included in the PostgreSQL persistence candidate.

Next milestoneIntegrate the role model across native Rishta, Directory and Communication Centre staging flows.

SAFEExecutable foundation

Audit / Safeguarding

65%

Growing nowTenant/actor/service audit persistence, database-level append-only protection, privacy boundaries and safeguarding controls now have executable test evidence.

Next milestoneCarry those controls through integrated staging and restart/retry recovery tests.

OBSLive telemetry

Analytics / Monitoring

60%

Growing nowOperations Radar, secure status service and sanitised GitHub/CI, Linear, Neon and Railway telemetry are live.

Next milestoneKeep telemetry snapshots fresh and extend evidence coverage to the integrated native staging application.

RUNRadar live

Deployment / Runtime

65%

Growing nowRailway hosts the Operations Radar and secure telemetry service.

Next milestoneKeep core FamilySuite application deployment separately governed.

Working now

Current focus

Build the clean integration branch from independently green PR #14 persistence plus PR #15 Communication Centre, without merging either into the RC or main.

Integrate PR #15 native Communication Centre and tenant UX shell with the persistence contracts.

Consolidate Native Rishta, Identity/Directory and FT-003 worker outputs without duplicate branches or contract drift.

After integration CI passes, deploy the native FamilySuite application to governed staging and prove synthetic end-to-end, restart/retry and rollback behaviour.

Executive signals

Live status

Railway control-plane runtimeLive

Custom domain / TLSVerified

GitHub durable lanes A-EAll green

PR #16 control planeDraft / mergeable

Neon branchesReady

Real family data0 used

FamilySuite stack classification

Architecture boundaries

Native FamilySuite Application

Business and platform components that form FamilySuite itself. These are distinct from hosting and database infrastructure.

FamilySuite Core Services

Tenant, service configuration, shared contracts and native application foundations.

NATIVE BUILD

Identity / Contacts / Directory

Shared native identity, contact and directory capabilities with governed identifier boundaries.

NATIVE BUILD

Native Rishta

Native Browse, Registration, Details, sharing, moderation and safeguarding services.

NATIVE BUILD

Communication Centre

Provider-neutral native communications orchestration, consent, suppression, audit and delivery controls.

NATIVE BUILD

Family Tree

Native genealogy domain with PostgreSQL-backed data model and staged GEDCOM import architecture.

NATIVE BUILD

RBAC / Audit / Safeguarding

Cross-cutting native security, authorisation, audit and safeguarding controls.

NATIVE PLATFORM CONTROL

Runtime Infrastructure

Infrastructure that hosts, stores or executes FamilySuite. These platforms are replaceable implementation infrastructure, not FamilySuite business modules.

PostgreSQL 16

Relational database technology used by the native FamilySuite data layer.

DATABASE ENGINE

Neon

Managed PostgreSQL infrastructure for development, disposable validation branches and governed database environments.

DATA INFRASTRUCTURE

Railway

Application hosting plus the always-on familysuite-control-plane-runtime health service. The runtime is healthy and restart-protected; product staging remains separately governed.

HOSTING + HEARTBEAT

Development / Delivery Tooling

Build, orchestration, QA, planning and operational-observability tools. Not FamilySuite business-runtime dependencies.

ChatGPT

Programme orchestration, QA, planning and connected-stack delivery actions.

DELIVERY TOOLING

GitHub

Authoritative code, PRs, version history and release evidence.

SOURCE AUTHORITY

GitHub Actions

Primary durable execution layer for lane A-E integrity, CI, security, PostgreSQL assertions and Neon validation. Event-driven now; 15-minute schedule prepared in PR #16 and activates only after the owner-approved control-plane merge reaches the default branch.

DURABLE EXECUTION

Cursor

Implementation environment used where appropriate for authorised code work.

DEVELOPMENT TOOL

Linear

Planning and delivery-status mirror. GitHub remains technical authority.

PLANNING

Linear Coding Sessions / Codex

Bounded autonomous coding lane with evidence returned to Linear and GitHub.

CODING AGENT

ChatGPT Orchestrator + Watchdog

Two supervisory automations only: orchestration and independent verification. Former Workers A-E are retired as schedules and preserved as durable GitHub control-plane lanes.

SUPERVISORY

Secure Status Service

Read-only operational telemetry for the Operations Radar. It is not a FamilySuite business service.

OBSERVABILITY

Canva Pro

Visual design, brand assets and concept prototyping only.

DESIGN TOOL

Google Drive

Reference documents and supporting development/operational material.

REFERENCE TOOL

Legacy / Migration

Existing temporary or predecessor systems retained only for continuity, migration, reconciliation or parity evidence.

WordPress

Temporary Ambala Arain Family presentation layer retained during migration. Not part of native FamilySuite runtime.

LEGACY / MIGRATION

Apps Script

Legacy engine for temporary external services and controlled migration/reference only. Not a FamilySuite runtime dependency.

LEGACY / MIGRATION

Google Sheets

Legacy source and operational ledger for temporary services, migration and reconciliation only. Not a FamilySuite runtime datastore.

LEGACY / MIGRATION

ComSuite

Existing communication authority retained until native Communication Centre parity and explicit cutover.

LEGACY / CUTOVER

External Integration

Channels and external services that FamilySuite may connect to through governed adapters.

Gmail

External operational correspondence service, accessed through governed connectors or communication workflows.

EXTERNAL SERVICE

Email

External communication channel served through the native Communication Centre and provider adapters.

CHANNEL

Future

Planned capabilities not yet treated as current native runtime dependencies.

FamilySuite APIs

Governed interfaces between native modules and approved external systems.

FUTURE

SMS / WhatsApp

Future omnichannel adapters under the native Communication Centre.

FUTURE

PostHog

Potential future analytics, product insight, errors and experimentation platform.

FUTURE

Next sequence

Controlled delivery

1. Integrate persistenceBring the independently green PR #14 PostgreSQL foundation into the RC integration line.

2. Integrate communicationsCombine PR #15 Communication Centre and UX shell with persistence and shared contracts.

3. Consolidate service branchesResolve Native Rishta, Identity/Directory and FT-003 branch overlap against the latest RC.

4. Native stagingDeploy the integrated native application to governed staging and run synthetic E2E, restart and rollback tests.

5. Release-candidate gateIndependent Watchdog review before any main merge, live-data migration or production cutover.

Safety position

Automatic guardrails

Radar deployment authorised/live0 real family data0 main merges0 live Rishta changes0 live communicationsFT-003 synthetic-only