A Build Week journal for the real work.
Niqdah’s final Build Week architecture and production codebase were comprehensively re-engineered with Codex and GPT-5.6 Sol. That work is recorded as code, tests, architecture decisions, and explicit limitations—not a historical-origin claim.
Engineering journal
Change the structure. Preserve the truth.
“Re-engineer” did not mean deleting verified behavior or existing data. It meant replacing weak seams incrementally, keeping compatibility paths explicit, and requiring evidence before calling a phase complete.
View the repository ↗Financial truth
The Build Week pass established one hierarchy across current balances, safe-to-spend, protected commitments, savings, debt, accounts, imports, reminders, and notifications.
Evidence and ordering
Import event time, received time, created time, immutable evidence, account identity, and duplicate signals became explicit instead of being inferred from one mutable timestamp.
Public and private boundaries
The public flavor excludes SMS permissions and components. The private flavor keeps opt-in new-message capture without historical READ_SMS access.
Architecture audit
The re-engineering audit mapped god classes, coupling, repeated parsers, stale-state risks, transactional gaps, security boundaries, accessibility work, and migration constraints.
Email automation
Provider-neutral contracts, a signed Resend adapter, opaque revocable routing, Firestore transactions, idempotency, quotas, and Android lifecycle controls replaced the legacy shared-secret assumption.
Public explanation
This website makes product status, privacy, AI behavior, bank support, build differences, limitations, deletion, and setup guidance independently inspectable.
What still counts as unfinished.
A branch, test suite, or design is not the same as production verification.
Resend account, receiving domain, signed webhook, secrets, deployment, and a sanitized real email still require verification.
The website requires a Vercel preview, browser checks, logs, accessibility, and performance verification before production approval.
High-risk balance, transfer, import ordering, debt, multi-account, AI, profile, and notification flows require manual results.