Tally 0.6.0 turns the private day counter into a fuller travel-planning and record-readiness toolkit, without changing its offline boundary.
Plan without rewriting history#
You can now add hypothetical trips with scheduled dates and conflict hints, or keep an undated country wishlist. Plans are visually separate from recorded crossings and never change authoritative country totals.
The new next-actions view brings together country return deadlines, upcoming plans, document expirations, and record problems. A dedicated audit identifies gaps, overlaps, incomplete periods, and ambiguous same-day crossing order without pretending to make a legal conclusion.
Understand and export the journey#
Crossings can be grouped into named trips and tagged with a purpose. Journey search includes those fields, while the annual recap summarizes travel without exposing document identity. Tally can export a plain CSV ledger or create a human-readable PDF recap for the user to save through Android’s document picker.
Twenty-nine milestones now cover exploration, journey depth, record quality, planning, and document readiness. The nearest achievements appear on the journey dashboard, with a separate screen for the full set.
Keep complete document records private#
Passport, ID-card, driver’s-license, and other-document records now support document number, holder, nationality, birth details, issuer, validity dates, and licence categories. These fields stay in the encrypted SQLCipher database and encrypted backups. Optional expiry alerts run locally, and CSV/PDF reports deliberately exclude sensitive identity fields.
The public additive JSON format now imports complete document records, trip metadata, and hypothetical plans. Its published schema and llms.txt guide make it practical for another local tool or agent to prepare a file, while Tally validates the whole batch before writing anything.
Safer updates and cleaner internals#
Tally can install offline rule-pack updates selected by the user, but only when they are signed by Tally’s production identity. Modified or third-party packs are rejected before they can affect calculations.
Under the UI, Room entities, DAO transactions, migrations, backup validation, and local write coordination now have explicit boundaries. Database and encrypted-backup payloads advance to schema 11 with a data-preserving migration.
Verification#
The release was built from public source revision f5dfdb2e85d2ff25caf6ce7ac35601b22ff048e4. The full deterministic suite contains 261 JVM tests. Core JVM coverage is 95.4% line, 72.5% branch, 87.0% method, and 96.8% class across 37 source files; Android-only behavior is covered separately on a physical Pixel 6a.
Android lint, the optimized release build, database migrations, encrypted-database recovery, and 92 physical-device instrumentation methods passed. Two clean release builds produced the same unsigned APK byte for byte.
The production APK has SHA-256 821ffccef330df1c074ff386d4ff075a68ea7814885df4a05b870753af910d05 and retains certificate SHA-256 5ee1b08fa518db8c0952759f323d5bc9bf4e7a4b6806906956ff42b2d5da9659.
Tally remains offline, account-free, and encrypted on device. Its calculations and reminders are planning aids; verify cited sources and your circumstances before relying on them for legal, tax, visa, or immigration decisions.
Source, import schema, llms.txt, and build instructions: https://gitworkshop.dev/npub1k7cwt3kmvahdtzc8n2ek08n9c7fz7n2zq88yzyqmjxmjehvdykfqwtu78y/relay.ngit.dev/tally
Comments
No comments yet. Start the conversation.