Release signal
Keep the public
path honest.
Every signed build created in the private repository is mirrored to the public Rekha-releases repository before users are notified.
REKHACONTROL ROOM
PRIVATE / OPERATIONSRK / 01Private operations console
Manage access, understand AI usage, publish user updates, and keep the public release path connected to the build pipeline.
Access is granted by the Firebase custom claimadmin: true.Signed in, not approved
Ask the project owner to grant the Firebase admin claim, then sign in again.
A live view of the moving parts
Release signal
Every signed build created in the private repository is mirrored to the public Rekha-releases repository before users are notified.
Who is using it
What needs attention
Accounts and access
Changing a tier is a server-checked admin action. It updates the Firebase user record used by the app entitlement gate.
| User | Last active | AI use | Tier | Access |
|---|
Operational facts
AI audit records contain operational metadata only. Document text, prompts, images, and answers are not shown here.
Model use
Cost estimate
Estimated from recorded Gemini token counts and the standard API rates configured in the backend.
| When | User | Operation | Model | Tokens | Cost | Status |
|---|
One message, two surfaces
Publishing creates an in-app announcement and sends an FCM push to registered devices. Users can tap an HTTPS action link from the notification.

Before publishing
Source of truth
The console reads the latest release from Rekha-releases, identifies APK assets, and lets you prepare an update notification without copying version numbers by hand.
Checking GitHub...