The decision is ready. The approver is in a taxi.

    Approvals, the full decision ledger, the AI assistant, and live collaborative notes and boards, on a phone. Everything written to the device is encrypted with a key held in secure hardware.

    Included with DecisionLedger. Android is in internal testing, and iOS is in progress.

    The app, screen by screen

    The whole ledger, sized for a thumb

    Ask the assistant, work a decision, clear the approvals holding somebody up, and see what changed. Tap any tab to explore it yourself.

    Chat
    Why did we hold the Frankfurt launch?
    searched decisions
    DEC-2280 delayed it in May. The blocker was the data residency review, not capacity. That review closed on 12 June, so the stated reason no longer holds.
    DEC-2280, Delay the Frankfurt region launch
    Ask a question
    |||

    A re-creation of the app, not a screenshot.

    Governance does not fail loudly

    It fails as a four day wait that nobody logs, repeated until people stop using the process at all.

    The approval is never the hard part

    The decision was made, the analysis was run, the workflow routed it correctly. Then it sat for four days because the one person who had to press approve was travelling.

    Executives do not live in a browser tab

    The people with approval authority are in meetings, in transit, or between buildings. Asking them to open a laptop to unblock a two-line request is how governance earns its reputation.

    And a queue that stalls stops being trusted

    Once a workflow is known to be slow, people route around it. The exception becomes the norm, and the ledger stops reflecting how the organization actually decides.

    One document, two devices

    Not a read-only viewer with a mobile skin

    The phone joins the same collaborative room as the browser. An edit typed on a train merges into a page someone else is editing at their desk, character by character, instead of overwriting their work.

    Phone
    Offline

    Vendor selection

    Vendor shortlist, final
    Rejected: incumbent renewal
    Blocker: SOC 2 report expired
    Cached encrypted, key in the device keychain
    Someone else, in a browser
    Vendor selection2 editing
    Vendor shortlist, final
    Rejected: incumbent renewal
    Blocker: SOC 2 report expired
    Live room. Notes and boards on the phone share the collaboration engine, the geometry, and the permissions used by the web app.

    What is actually in it

    Most enterprise mobile apps are a dashboard and a link to the desktop site. Here is the surface, in the detail an evaluator needs.

    Clear what is waiting on you

    The reason the app exists. Everything blocked on your signature, in one list, ordered by how late it is.

    • An approvals inbox with a pending count on the tab, so you can see the queue without opening it
    • Urgency is colored, so an overdue item does not look like one that is due next week
    • Approve or reject in place, with the same authority and the same audit record as the web app
    • Approval sections appear on the decision itself, so you can approve from the record you are reading

    Work the decision, not just a summary of it

    A real record you can change, not a read-only card with a link to the desktop site.

    • Browse and search the ledger, and create a decision from your phone
    • Filter the list by status and by priority, so a long ledger stays usable on a small screen
    • Edit fields inline on the record rather than through a separate form
    • Read and add comments, so the discussion does not have to wait for you to get back
    • Record an outcome with a star rating once the decision has played out

    Ask the assistant on the way to the meeting

    The full AI assistant, streaming, with the same grounding and the same guardrails as the web app.

    • Streaming answers, so you are reading while it is still writing
    • Conversations persist, so you can pick up a thread from your desk on your phone
    • The tools it used are shown by name, and its citations link to the records behind them
    • Choose the domain it should answer within, so a legal question is not answered as a finance one

    Notes and Canvas, as a real peer

    Not a viewer. The phone joins the same collaborative room as everyone on a laptop.

    • Notebooks, sections, and pages, with editing that merges into a live web session
    • Boards with pan, zoom, moving nodes, adding shapes, lines, and text, across multiple pages
    • Comments on both surfaces, so a review can happen away from a desk
    • If a collaborative room cannot be joined, the page opens read only rather than risking an overwrite

    That last point is deliberate. A whole-document save from a stale phone would silently discard whatever a colleague typed while you were offline, so the app refuses to make it.

    Handwriting that is the same object as the web

    Stylus input rendered from the same geometry the browser uses, not a picture of a drawing.

    • Pressure sensitive strokes with an Apple Pencil or any active stylus
    • A note written on a phone and one written in a browser are the same stored object
    • Ink lives on the page alongside typed blocks rather than in a separate attachment

    Goals, KPIs, and projects

    The execution side of the platform, sized for a phone.

    • Open and edit goals, KPIs, and projects
    • Log a KPI value from wherever you are, which is usually where the number actually comes from
    • A people directory, for when you need to know who owns something

    A phone is the device most likely to be lost

    Which is why the interesting engineering here is not the screens. It is what happens to the data once it lands on the device.

    Everything written to disk is encrypted

    AES-256 with an authentication tag, using a key held in the device keychain on iOS and the hardware backed keystore on Android. It covers the offline cache and the collaboration snapshots alike.

    No plaintext fallback, at all

    If the app cannot get a key from secure hardware, it turns persistence off rather than writing your decisions to disk unprotected. A lost phone does not become a data incident.

    Your existing sign-in, including MFA

    The same identity provider as the web app, with time-based codes or SMS as a second factor. No separate mobile credential to provision or revoke.

    Multiple workspaces, cleanly separated

    Switch between tenants from settings. Switching clears the cached data for the workspace you left, so nothing from one client is visible while you are working in another.

    The same permissions, not a looser copy

    Roles, grants, and tenant isolation are enforced by the same backend that serves the web app. There is no mobile-only path with weaker checks behind it.

    Offline reads, deliberate about writes

    Recently seen data stays readable with no signal, from the encrypted cache. Writes are not queued for later replay, because a write applied an hour after the fact would land on a record that has already moved on.

    The whole surface

    The short version, for the part of the evaluation that is a checklist.

    Approvals inbox

    With a pending count and urgency

    Decisions

    Browse, create, edit, comment, rate outcomes

    AI assistant

    Streaming, with tools and citations

    Alerts

    Inbox, unread badge, mark all read

    Notes

    Notebooks, sections, and pages

    Canvas

    Pan, zoom, shapes, lines, text, comments

    Live collaboration

    The same rooms as the web app

    Goals and KPIs

    Including logging a KPI value

    Directory

    Find the owner of anything

    Workspace switching

    Multi-tenant, with cache separation

    Encrypted at rest

    Keychain and keystore backed

    Offline reads

    Last known state, still encrypted

    Watch a note typed on a phone land in a browser

    We will put the app on a phone and the web app on the screen share, edit the same page from both, and approve a real request from the handset while you watch the audit trail update.