Akal RootsMake room for one idea.
Already have the test app? Try these three tiny tasks.
- Create a note and write two sentences.
- Make a checklist with three items; tick one.
- Close and reopen the app. Is your work still there?
THE AKAL ROOTS FLIGHT DECK
See the progress.
Shape what comes next.
Real apps, small experiments, and a clear view of the work ahead. You do not need to be technical to help.
Reviewed 12 November 2026 · Public tester roadmap
04app/platform test builds
01live developer website
NextR2 + D1 + audio pipeline
NO TECH SKILLS NEEDEDThree minutes.
Three minutes.
One honest reaction.
You do not need to find every bug. Just try a normal task and tell Sunny where it felt easy or confusing.
A small moment of reflection.
Try the current journal/routine features. Audio is coming later.
- Write a short journal entry and save it.
- Add a routine item or mala target; record progress.
- Reopen the app and check the saved entry and progress.
See one expense more clearly.
Use invented amounts for a quick first look.
- Add a small test expense and choose a category.
- Find it on Home and check the total.
- Open Receipts and see whether the next step is clear.
Need a test build? Ask the developer. This page does not offer public APK/installer downloads yet. Feedback is shared directly with Sunny; nothing is collected by this page.
WHAT WORKS / WHAT NEEDS WORKNo mystery.
No mystery.
Here is where things stand.
“Done” means implemented in the reviewed source. “Needs testing” names the real-world checks still to do. “Pending” is future work.
Showing all 5 app/platform entries.
JNJUST NOTEWindows · 1.6.6Test build available
Encrypted desktop notebooks with a broad editing workspace and manual Google Drive backup.
Done · in the reviewed build6
- Local profiles, passwords, recovery keys and encrypted notes/attachments.
- Notes, notebooks, checklists, journals, drawing and code/text notes.
- Rich formatting, inline images, search, notebook management and PDF exports.
- Offline English writing checks, optional Punjabi tools and a personal dictionary.
- Appearance palettes and adjustable workspace controls.
- Manual encrypted Google Drive snapshots and missing-note recovery.
Needs testing / confirmation4
- Retest the reported opacity slider and dark backup-button text in the next installer.
- Verify abandoned Google sign-in cancels or times out without blocking app exit.
- Check wider grammar coverage against the supplied example; no full grammar-engine claim.
- Clean-install/update and second-computer Drive recovery need end-to-end verification.
Pending / coming next4
- Finish and ship the next-update fixes with matching help documentation.
- Validate consistent installer/update behavior; current builds remain unsigned.
- Automatic multi-device synchronisation remains future work.
- R2 build archiving is planned; the separate existing Drive CI-archive workflow last failed.
How this status was checked
Windows build 42896326711 passed CI on source 22a34b2. Current main README and next-update implementation notes reviewed. Phone/installer observations are separate from automated checks.
Reviewed 12 November 2026. CI success does not mean all phone or installer workflows have been tested.
JNJUST NOTEAndroid · 0.8.0 testTest build available
Native encrypted notes on Android. Full Windows feature parity is a plan, not a completed port.
Done · in the reviewed build6
- Encrypted local accounts, recovery, background locking and optional biometric unlock.
- Notes, notebooks, favourites, search and native rich-text controls.
- Checklists, dated journals, templates and stylus/drawing tools.
- Punjabi typing, attachments and portable encrypted backup transfer.
- Manual Google Drive backup/restore implementation.
- Installer-artifact cleanup and serialised build safeguards are present on this branch.
Needs testing / confirmation3
- Install/update, keyboard layout, S Pen and hardware biometrics on the S26 Ultra.
- Live Google authorisation and encrypted backup/restore on the phone.
- Cross-device formatting/drawing compatibility and mobile backup-size boundaries.
Pending / coming next6
- Windows-style notebook rename/delete/export and recoverable Trash behavior.
- Full code editor, JSON/CSV/Markdown tools and offline writing assistance.
- Inline image placement, resizing/alignment and note/notebook PDF export.
- Authenticated previous-vault recovery and Drive recovery without duplicated notes.
- Persistent release signing and verified updates that preserve installed data.
- Complete the remaining mobile workspace and Windows-parity requirements.
How this status was checked
Android build 43002226656 passed CI for source 216d3a1. android/README.md, Gradle version and the explicit Windows-parity gap document reviewed.
Reviewed 12 November 2026. CI success does not mean all phone or installer workflows have been tested.
SSatsangatAndroid · 0.2.0 testTest build available
Today, Study, Journal and Routine are implemented. Shared cloud content and audio are the next proposed layer.
Done · in the reviewed build6
- Today, Study, Journal and Routine screens with saved navigation state.
- Encrypted journal editing, search, recovery drafts and portable backups.
- Editable checklist/mala targets, manual counts and dated routine history.
- Native SGPC/BaniDB reading with source dates and integrity checks.
- BaniDB keyword search, complete Shabads and Punjabi meanings where supplied.
- Visible source/network failures; unsupported SikhNet native encoding is disclosed.
Needs testing / confirmation3
- Live phone source loading, fonts and scrolling; India/New Zealand date boundaries.
- Journal save/reopen, encrypted routine persistence and backup restoration.
- Reminder delivery and failure behavior on the physical phone.
Pending / coming next6
- D1 approved text/session catalogue and Worker content API.
- R2-hosted approved audio and an online session player.
- Encrypted offline Download / Play offline / Remove download.
- Mood-based guided sessions, Kirtan/Simran lists and playback-speed controls.
- Approved content/reuse permissions, offline verified-text cache and SikhNet conversion validation.
- AI discussion, full language localisation and release signing remain future work.
How this status was checked
Test-content source 6b25bb4 passed CI in run 42417134029; later Hukamnama/routine run 42417847377 also passed. Latest branch README/design reviewed; older build-status notes are partly stale.
Reviewed 12 November 2026. CI success does not mean all phone or installer workflows have been tested.
SSpendCountAndroid · 0.3.0Test build available
An offline NZD spending app with statement import, receipt matching and remembered merchant categories.
Done · in the reviewed build6
- Simplified Home / Add / Receipts flow with a spending chart and categories.
- Statement previews, duplicate checks, import undo and manual entries.
- Remembered payer/payee aliases and confirmed category choices.
- Camera/image receipt capture, local OCR and statement matching.
- Encrypted offline storage, encrypted backup/restore and authenticated data wipe.
- Uncertain categories/receipt details go to Review; Android release has no Internet permission.
Needs testing / confirmation3
- Redesigned interface, camera/OCR accuracy and complete restore on the S26 Ultra.
- Real ANZ CSV fixtures; image-only PDFs and untested statement layouts remain unsupported.
- Installed update signing and Play Protect behavior.
Pending / coming next4
- Change the current four-day receipt-match tolerance to the agreed one-day test window.
- Persistent release signing and final device validation.
- iOS, Windows and Linux releases are future scope.
- Savings UI is deferred; notification capture and cloud finance storage remain out of scope.
How this status was checked
docs/STATUS.md records run 41818373772 passing 54 tests, TypeScript, Android assembly and three native instrumentation checks on source f7f2931. Current branch contains later source; that build is not claimed to cover every later commit. User confirmed an earlier build read the supplied statement.
Reviewed 12 November 2026. CI success does not mean all phone or installer workflows have been tested.
AAkal RootsWeb & shared infrastructure · Developer hubWebsite live
The public home for the apps. The shared archive/content architecture is agreed but not provisioned.
Done · in the reviewed build3
- Public developer website on Cloudflare Workers with Git-connected deployment.
- JUST NOTE product page, privacy/terms, backup guide and support page.
- Workers compatibility-date configuration and prebuilt static deployment output.
Needs testing / confirmation2
- Check this roadmap after the Git-triggered deployment finishes.
- Keep public policies aligned with the exact released apps.
Pending / coming next4
- Activate R2, separate build archives/media and set retention/access rules.
- Implement CI upload verification before removing temporary artifacts.
- Create D1 schemas and authenticated Worker APIs.
- Production Google branding/domain verification and a monitored support contact when needed.
How this status was checked
Homepage deployment and rendering were confirmed by the user's screenshots. Website source and Cloudflare Wrangler configuration are in the Akal Roots repository. This roadmap is a manually maintained snapshot.
Reviewed 12 November 2026. CI success does not mean all phone or installer workflows have been tested.
Snapshot, not a live build monitor. Updated manually after reviewing source, build results and tester feedback. No guessed completion percentages.
THE PLAN BEHIND THE APPSHow it all
How it all
fits together.
Three visual maps. Solid green cards mark existing pieces. Dashed violet cards are planned. User notebook backups to Google Drive remain separate.
BUILD & DOWNLOAD PLAN
From code to a saved app build
Builds already run in GitHub Actions. The R2 archive and verified cleanup sequence still need connecting.
Working nowApp source in GitHub
A separate source project for each app.
Working nowBuild + test the app
GitHub Actions creates an Android APK or Windows installer.
Checks decide the next step
Success pathChecks pass
Continue with a successful build.
PlannedUpload to R2
Store by app, platform and version.
PlannedVerify the saved copy
Check the uploaded object, size and checksum.
PlannedClean up temporary artifacts
Only after the R2 copy is confirmed.
Failure pathChecks fail
Diagnose the failure. Do not publish this build.
Safety ruleKeep the last good archive
A failed build must not replace a working download.
SATSANGAT · PROPOSED
From a session to your headphones
D1 holds information. R2 holds files. The Worker API and session player are planned, not connected yet.
PlannedYou choose a session
Press Play when you are ready. No autoplay on mood selection.
PlannedAsk the content service
A Cloudflare Worker returns approved session information.
PlannedD1 · the information
Titles, duration, Gurmukhi, Punjabi meanings and source references.
PlannedR2 · the audio files
Approved recordings; images and PDFs can also live here.
The app brings them together
PlannedListen inside Satsangat
Show the correct text/meaning alongside the session player.
PlannedOptional offline download
Save an encrypted copy for later listening.
OFFLINE AUDIO · AGREED REQUIREMENT
Download once. Listen privately.
No MP3 export or sharing button. Encryption discourages copying; playback can still be recorded.
PlannedChoose Download
Only for sessions approved for offline use.
PlannedFetch + verify the session
Authorised access, integrity checks and safe handling of interrupted downloads.
PlannedEncrypted audio
Kept in app-private storage; no ordinary MP3 export.
PlannedProtected device key
Android Keystore protects access to the decryption key.
PlannedPlay offline in the app
Decrypt for playback without leaving a permanent plaintext audio file.
PlannedRemove download
Remove the locally saved session when the user chooses.
Files ≠ private user data.
R2 build archives and approved shared audio are developer infrastructure. JUST NOTE backups can still go to each user’s own Google Drive. Satsangat journals/routines and SpendCount finance records stay on-device by default.