NURA · The app

Security and testing: the engineering behind NURA

Trust in an app that touches worship, health, and your daily plans has to be earned in code, not in adjectives. NuroNova Genix Co. (Delaware; headquartered in Houston, Texas) hardened NURA through deterministic engineering, a large automated test suite, and two independent adversarial reviews. Here is what that actually consisted of — stated precisely, and without claiming anything we can't defend.

Deterministic engines, and roughly 1,327 tests

NURA's core is a set of pure, deterministic engines — prayer times, presence, Qibla, health — where the same inputs always produce the same outputs, with no network call and no model in the path. Prayer times in particular are computed by explicit solar astronomy (Julian day to sun declination and the equation of time to hour angles) and nothing else; the assistant may explain a setting but can never produce or nudge a time.

Because the engines are pure, every rule is a test, and a wrong answer is a test failure rather than a surprise on your wrist. The suite spans 101 test files and roughly 1,327 automated tests, all passing, run with the platform's own test runner. Among them are honesty tests: that the assistant can never announce work she didn't do, and that changing your city moves the real computed times rather than just relabeling the screen.

A 14-agent adversarial bug audit

NURA was put through an adversarial bug hunt run by fourteen agents — seven trying to find defects, seven trying to refute each finding. The result: 22 confirmed bugs (1 critical, 2 high, 8 medium, 11 low), with 5 candidate findings refuted. 21 were fixed in code and shipped; the single remaining item is the deletion of a dead file, held back deliberately for the owner's go-ahead. A few of the fixes, concretely:

• Critical: the notification reconciler used to cancel every pending notification it didn't recognize — which meant it could silently wipe your own agenda alarms. It now cancels only prayer-owned notifications.
• High: a same-day prayer-time change (a new calculation method, offset, or city) previously failed to reschedule because the notification identity ignored the fire time. The identity now folds in the minute, so a moved time is properly re-scheduled.
• A blocked autoplay of the athan no longer permanently silences that prayer — the "played" flag is only set after the sound actually plays, so a tap can still sound it.

Each fix landed with tests that assert the corrected behavior — the tests were updated to prove the fix, never to hide the defect.

A 14-agent adversarial security review

A second fourteen-agent review, structured the same way (seven finders, seven verifiers), examined NURA as what it is: a personal Muslim-companion app with no backend, whose AI and voice are bring-your-own-key. It confirmed 5 issues (1 high, 4 low) and classified 10 more as accepted-by-design or refuted. The confirmed items were addressed:

• A warning when a lock-controlling Home Assistant token would be sent to a non-HTTPS address, steering you to a secure connection.
• Android app backups disabled, so a device backup can't exfiltrate app data.
• A corrected privacy screen that names the actual AI provider and enumerates precisely what a request can carry — location, address, health, and looked-up contacts.
• A guard that refuses a mis-filed key so it can never be disclosed to the wrong provider.
• A dependency bump for a known build-time issue.

One follow-up is documented honestly rather than quietly skipped: moving the stored keys and tokens from local storage into the iOS Keychain. It is a low-severity item (it requires a compromised, unlocked device to matter) and an asynchronous refactor, so it is scheduled as its own focused task instead of being rushed.

Honesty built into the architecture

The most important safety property isn't a patch — it's a boundary. The optional AI reaches the engines through read-only tools. Noora can ask what a prayer time is, or what the day looks like; she cannot overrule an engine, change a setting, or reach the network on her own. Actions are validated separately and handed to the app, which owns every engine handle. The presence engine is written to hedge on purpose: it reports what the phone did ("it looks like," "I can't tell"), and it will never accuse you of missing an appointment, because a phone left behind looks identical to a phone that never went.

What this rigor means — and what we don't claim

We will not tell you NURA is "unhackable" or "100% secure." Instead, here is the honest posture: there is no backend to breach, the engines are deterministic and heavily tested, the app has survived two adversarial reviews, the confirmed findings were fixed and shipped, and the one remaining hardening step is written down for anyone to see. That is what serious engineering looks like — specific, tested, and candid about what's left.

NURA is a free, watch-first Muslim life companion from NuroNova Genix Co. It is coming soon to iPhone.