REMIT starts in shadow mode: two weeks, on your own servers, with your own data, zero actions taken.See the pilot

Changelog

What changed

Dated changes to the REMIT console and its specifications. Product, not marketing.

  1. Integration boundary specified

    • Machine principals: client certificates from the bank’s CA, scopes, a named human owner; never an administrative role.
    • Versioned POST /v1/ingest, scoped masked reads, outbound delivery as a subscription onto the ledger, POST /v1/verify.
    • Connectors as signed declared artifacts staged shadow → gate → auto. The v1 catalogue is published on the Integrations page.
    • Branch console title fixed.

  2. From queue to platform

    • Six surfaces: review, intake, oversight, proof records, administration, branch console; senior desk, SLA board and reports.
    • Case state machine with hold, waiting-on-customer, escalation, dual approval, reopen and correction; the case timeline rendered from the ledger.
    • Shadow mode as the default day one, with agreement and disagreement recorded per case.
    • Insurance motor-claims FNOL workflow rendered by the same console from its own declared schema.
    • Proof-record registry with verification status, key history, failure states and exports.
    • Identity bar showing sign-in via the bank’s IdP; the role switcher labelled as a demo control; full seven-role matrix.

  3. Reviewer flow

    • Queue, case, decision, record and proof for the worked banking case, with the four confidence states, evidence-first layout and a Thai language pass.

  4. Edge inference note published

    • FORGE and HELIX engineering note, weights on Hugging Face.