Design stage: there is no released app yet. This site separates what exists in the repository from what is planned. See status

Capabilities

Offline-first architecture

The design is offline-first: every sale is written locally first and synced between devices on the local network. The stack (Rust core and Flutter UI) is a recommendation; no spike has been done.

Status

Planned Everything on this page is a plan. The repository contains a catalog and design documents, not a released app. Entries are tagged with their own status.

Designed

Offline-first design

The shop must keep selling without internet.

Read →
Not decided

Local database

The recommended stack uses SQLite with write-ahead logging; a spike to confirm has not been done..

Read →
Not decided

Stack recommendation

The repo recommends a Rust core with a Flutter UI.

Read →
Planned

Sync between devices

Devices in one shop sync over the local network.

Read →
Planned

Multi-register shops

Several tills sharing one database or syncing peer to peer..

Read →
Planned

Time and ordering

Hybrid logical clocks are listed as a way to order events without perfect clocks..

Read →
Planned

Crash and power-cut safety

Atomic writes and journaling so a failure never loses a completed sale..

Read →
Built (repo)

Core and logistics isolation

The ARCH module keeps logistics separate from the core POS so a fault in one cannot corrupt the other.

Read →
Built (repo)

Packaging engine

Per ADR-0001 and ADR-0002, Simca Packaging is a server-side or developer-side engine that assembles and signs a package from a package spec.

Read →
Planned

Performance goals

The README says reliability over speed; the catalog lists performance targets as items..

Read →
Built (repo)

Data model

The app core stores data in SQLite (write-ahead logging, full sync, integrity check at open, verified backups) with forward-only migrations that come from each element's pack; Logistics has its own database file.

Read →
Not decided

Update model

Acquisition is free (ADR-0007), which replaces the earlier buy-once and yearly-fee wording.

Read →
Planned

Localization

English and Spanish, local number and date formats, accessible UI..

Read →
Planned

Local logs and diagnostics

Logs stay on the device and are shared only on request..

Read →
Designed

Launcher

The one download.

Read →
Designed

Offline mode

Offline mode is a login mode of the app: the app signs into no cloud and makes no network request.

Read →
Built (repo)

User-initiated signed updates

Updates are signed packages.

Read →
Built (repo)

Package spec

A small JSON file written by the launcher that lists the chosen elements.

Read →
Designed

Online sign-in

Only features that inherently need the online network need a sign-in: Tap to Pay, the co-op price counter, referral validation and the Logistics board relay.

Read →
Designed

Elements, not roles

ADR-0001 removed separate role builds.

Read →
Built (repo)

Paired development

ADR-0002: every element is built first in Simca Packaging (thin manifest, prebuilt artifact, dependency links) and then immediately in Simca or Simca Logistics.

Read →
Built (repo)

Build delivery

ADR-0002: packages are assembled from per-element prebuilt pieces and cached by spec hash; nothing is recompiled per customer and identical specs give identical builds.

Read →
Designed

Offline/Online toggle

ADR-0002 and ADR-0003: the launcher shows a plain-sight toggle that governs only the app's login mode.

Read →
Designed

Update notice

ADR-0003 replaced the earlier rule that nothing is contacted until the user presses Check.

Read →
Not decided

Free start and the profit threshold

Acquiring Simca is free.

Read →
Designed

iOS launcher parity

ADR-0002: the iOS launcher must look and work like the other platforms; Apple rule limits are checked later and recorded as per-feature exceptions instead of being designed around now..

Read →
Built (repo)

Offline guard tests

Tests in the Rust workspaces fail the build if network crates, sockets, URLs, process spawning, demo keys, default network binding or remote asset loads appear.

Read →
Designed

The launcher's one opening request

ADR-0003: the launcher has no account.

Read →
Designed

The launcher has no account

ADR-0003: the launcher is free to download and use and has no login, profile or cloud state, like a game-store launcher.

Read →
Not decided

Simca's own launcher, forked from an earlier private one

ADR-0007: Simca gets its own launcher, copied from the author's earlier private launcher and stripped of seats, presence, polling timers, a demo key and telemetry; it is not registered in the stock launcher.

Read →
Built (repo)

What the app core can do today

The Simca core is Rust library code, tested, with no screen: money in integer minor units with cash rounding, a SQLite store, and seven elements (products and stock ledger, price lists, sale with cash settlement and void, open tickets, takeout orders, double-entry books, waybills with receiving into stock).

Read →
Built (repo)

What the Logistics core can do today

Simca Logistics is Rust library code, tested, with its own database file: signed jobs, bids, assignment and the waybill handshake, positive-or-neutral attestations with draft Elo math, an outbox and inbox for the contract with the core, and a service that runs as a separate process.

Read →
Built (repo)

The quarterly cost model

ADR-0008, amended by ADR-0009 (tentative): the quarter's cost lines are signed data; the fee is that cost, less any public donations, split evenly among the paying members and rounded down, the same for every product including Simca Logistics.

Read →
Built (repo)

Your bill has dropped X percent

ADR-0008: a member's change in bill is computed locally from the signed quarterly documents already on the computer, and says dropped, same or rose.

Read →
Built (repo)

Two independent signatures on price documents

ADR-0008: a cost model or price table is accepted only with two signatures from two separate key sets; the ordinary single-signature check refuses these document types.

Read →
Built (repo)

Entitlement per package

ADR-0006 and ADR-0007: a package is used offline under a signed entitlement file that names the package and its elements.

Read →
Designed

The customer app front end is a plan

simca-app holds only a plan: a Flutter interface over the Rust libraries through a generated bridge, with no business rules in the interface and screens in this order: cash sale, products and prices, tickets, end of day, elements, updates, settings.

Read →
Not decided

No margin on the fee

ADR-0009 (tentative): the fee is the plain cost split with nothing on top.

Read →
Built (repo)

Owner pay and affiliated-company costs

ADR-0009 (tentative): the owner may pay himself and his other companies from the cost base.

Read →
Built (repo)

Public and private donations

ADR-0009 (tentative): public donations may appear as labelled lines on the cost page and are applied against the cost before it is split (to be confirmed, D40).

Read →
Not decided

Billing, notices and what a lapse stops

ADR-0009 (tentative): billing happens at the quarter turnover and the business then continues or its paid services end; once billed it has until the next turnover to pay.

Read →

Questions

What is the tech stack?
The repo recommends a Rust core with a Flutter UI and SQLite. It is not decided and not built.
Does it need internet?
The design says no for selling. Updates and optional adapters may use it.