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--

65%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 Build75%Executable native foundation

Integration65%Database and cross-service integration

Staging70%Deployed end-to-end staging

Production Readiness15%Migration, rollback and live gates

Overall65%

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

✓

Last verified milestonePostgreSQL-backed staging verified

Native FamilySuite staging is live on Railway with PostgreSQL 16, migrations 0001-0005, persistent synthetic data and a passing database-aware end-to-end smoke test.

→

Next critical milestoneRC close-out

Close remaining Identity/Directory/FT-003 and release-evidence gaps without crossing production owner gates.

RefreshEvery 5 minutes

Live evidence refreshes automatically with safe snapshot fallback.

Architecture workstream85%

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

Runtime foundation80%

Radar, durable control-plane runtime and PostgreSQL-backed native FamilySuite staging are live in isolated environments.

Telemetry servicesLive / attention

GitHub/CI, Linear and Railway evidence are live; Neon database validation is green through CI while its ChatGPT connector remains an attention item.

Decisions required

Owner decisions

None right now

Current blockers

Delivery blockers

No current staging blocker: the native FamilySuite application and PostgreSQL 16 staging database are healthy and database-aware E2E smoke is green.

Remaining release gaps are Identity/Directory/FT-003 close-out, final integrated release evidence and owner-gated production activities.

Main-branch protection cannot currently be administered through the connected GitHub integration; CI, PR and Watchdog 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.

RUNNative staging live

Deployment / Runtime

80%

Growing nowRailway hosts the Radar, durable control-plane runtime and isolated PostgreSQL-backed native FamilySuite staging.

Next milestoneKeep staging green through RC close-out and preserve production separation until explicit release approval.

Working now

Current focus

Close remaining Identity, Contacts, Directory and FT-003 integration gaps against the current nine-check-green RC.

Keep PostgreSQL-backed native staging green while extending synthetic E2E coverage to the latest ComSuite bulk campaign APIs.

Consolidate deployment-only staging hardening back into the RC without importing temporary infrastructure artefacts unnecessarily.

Prepare the independent release-candidate evidence pack, rollback/restart proof and owner-gated production checklist.

Executive signals

Live status

Railway control-plane runtimeLive

Custom domain / TLSVerified

GitHub durable lanes A-EAll green

Integrated RC PR #179/9 checks green

PostgreSQL stagingLive / migrations green

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. Close core gapsComplete Identity, Contacts, Directory and FT-003 integration against the current RC contracts.

2. Extend staging E2EAdd synthetic bulk Email/SMS/WhatsApp campaign API coverage to the PostgreSQL-backed staging smoke suite.

3. Consolidate staging hardeningBring validated migration/runtime hardening into the RC while keeping deployment-only files isolated where appropriate.

4. Independent RC reviewRun Watchdog verification across security, privacy, persistence, restart/retry, rollback and staging evidence.

5. Owner release gateNo main merge, live-data migration, live communications or production cutover without explicit approval.

Safety position

Automatic guardrails

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