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.
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--
70%verified programme progress
FS
Overall70%
Architecture advanced; live Radar and telemetry foundation deployed.
✓
Last verified milestoneRadar live
Railway deployment, custom domain and TLS successfully established.
→
Next critical milestoneTelemetry
Secure GitHub and Neon status integration.
5m
RefreshEvery 5 minutes
Live evidence refreshes automatically with safe snapshot fallback.
A
Architecture workstream85%
Generic multi-tenant platform hierarchy and V1.4 direction established.
R
Runtime foundation65%
Radar runtime is live; core FamilySuite application deployment remains separate.
T
Telemetry servicesPartial
GitHub and Neon credentials pending; Railway live.
Decisions required
Owner decisions
None right now
Current blockers
Delivery blockers
GitHub private-main protection remains dependent on GitHub support / plan capability.
Neon controlled fail/pass proof remains outstanding.
Top risks
Guardrails
Do not mint ContactIDs until identity authority is resolved.
No production migration or live service cutover without parity and rollback evidence.
12
Core workstreams12 tracked
#
PR chain#4 → #10
Live verification pending.
GH
GitHub telemetryConnecting
Awaiting live status.
FT-003Held
Family Tree
35%
Growing nowFT-001 and FT-002 foundations exist in the stacked PR chain.
Next milestoneFT-003 only after stack close-out and separate approval.
IDUnresolved
Identity / ContactID
20%
Growing nowMapping and authority boundaries only.
Next milestoneResolve canonical issuance authority before any minting.
DIRPlanned
Directory
15%
Growing nowRecognised as a core FamilySuite domain.
Next milestoneDefine executable domain contract after identity foundations.
RISMigration path
Rishta
55%
Growing nowExisting Registration, Browse, Public Feed and inbox remain live authorities.
Next milestoneParity-first migration planning into FamilySuite.
COMDesign advanced
Communication Centre
70%
Growing nowRBAC, inbox, APIs, queues, retention and provider model defined.
Next milestoneComplete ComSuite parity inventory before implementation.
BLDPlanned
Blood Bank
10%
Growing nowRecognised service domain within the generic platform.
Next milestoneDefine service contract when prioritised.
DNAFuture
DNA
8%
Growing nowFuture FamilySuite service domain reserved.
Next milestoneArchitecture only when authorised.
RBACFoundation
Admin / RBAC
50%
Growing nowPermission and approval principles span major components.
Next milestoneCanonical role matrix tied to executable services.
SAFEFoundation
Audit / Safeguarding
55%
Growing nowPrivacy, audit, retention and safeguarding treated as platform controls.
Next milestoneExecutable audit contracts and automated tests.
OBSLive start
Analytics / Monitoring
40%
Growing nowOperations Radar and read-only status service are deployed.
Next milestoneComplete live GitHub and Neon telemetry.
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 focus01
Finish secure read-only GitHub telemetry for PR and CI status.
02
Finish secure Neon branch telemetry and controlled validation proof.
03
Maintain the Operations Radar as the visual command centre for FamilySuite delivery.
04
Continue Communication Centre read-only design and ComSuite parity mapping.
Executive signals
Live statusRailwayLive
Custom domain / TLSVerified
GitHub PR chainDraft / unmerged
Neon branchesReady
Real family data0 used
Full stack - current and possible future
Platform ecologyChatGPT
Programme orchestration, QA, planning and connected-stack actions.
IN USEGitHub
Authoritative code, PRs, version history and CI triggers.
IN USEGitHub Actions
Automated CI, QA and Neon validation workflows.
IN USECursor
Implementation environment when code work is authorised.
IN USENeon
PostgreSQL development database and disposable validation branches.
IN USEPostgreSQL 16
Core relational data layer for FamilySuite.
IN USELinear
Planning and delivery-status mirror, not technical authority.
IN USERailway
Active runtime for Operations Radar; Development Bridge remains separate and inactive.
IN USESecure Status Service
Read-only backend for GitHub, Neon and Railway telemetry.
IN USEGoogle Drive
Reference documents and supporting operational material.
IN USEGmail
Operational correspondence and support communication.
IN USEApps Script
Current business logic for Rishta and operational systems.
TRANSITIONALGoogle Sheets
Current data stores and operational ledgers.
TRANSITIONALWordPress
Current Ambala Arain Family public presentation layer.
TRANSITIONALComSuite
Communication authority until parity and explicit cutover.
TRANSITIONALPostHog
Possible future analytics, errors, experiments and usage insight.
FUTUREFamilySuite APIs
Future interfaces between modules and external systems.
FUTUREAutomations
Recurring checks, reminders, conditions and summaries.
IN USEEmail
Current and future communication channel.
IN USESMS / WhatsApp
Future omnichannel adapters under Communication Centre.
FUTURENext sequence
Controlled delivery1. Neon proofControlled synthetic fail/pass evidence.
2. GitHub protectionResolve private-main protection capability.
3. Consolidate PRs#4 → #10 one-by-one with approval.
4. Clean mainVerify consolidated baseline and CI.
5. FT-003Only after separate owner approval.
Safety position
Automatic guardrails
Radar deployment authorised/live0 real family data0 PR merges0 live Rishta changes0 ComSuite changes0 FT-003 start