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

Hardware, platform and safety

Offline-first architecture

How Simca is designed: local database, sync between devices, crash safety, isolation of logistics, the packaging builder

Status labels: Built in the repository (checked files or tested library code; not a product you can run yet) Designed in a document, no code yet Planned: listed in the catalog, not built Not decided Not in the catalog yet (a gap) No claim made

How risky is “Offline-first design” to get wrong, considering power loss mid-sale?

Designed C0222

The shop must keep selling without internet. Every sale is written locally first. Plan for: power loss mid-sale; clock errors; disk full. It is designed in a document and no code exists.

Open this answer on its own page

How risky is “Local database” to get wrong, in particular regarding corruption recovery?

Not decided C0223

The recommended stack uses SQLite with write-ahead logging; a spike to confirm has not been done. Plan for: corruption recovery; migration; file locks. It is not decided.

Open this answer on its own page

Which edge cases come up around “Stack recommendation”, with a focus on platform coverage?

Not decided C0224

The repo recommends a Rust core with a Flutter UI. It is a recommendation, not a decision, and no spike was done. Plan for: platform coverage; printer plugins; team skills. It is not decided.

Open this answer on its own page

What goes wrong with “Sync between devices” in a shop, considering conflicts?

Planned C0225

Devices in one shop sync over the local network. The sync engine is catalogued. Plan for: conflicts; clock drift; late devices. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

What is the plan for “Multi-register shops”, thinking about leader device fails?

Planned C0226

Several tills sharing one database or syncing peer to peer. Plan for: leader device fails; split network; duplicate numbers. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

Where does “Time and ordering” fit in Simca, with a focus on device clock jumps?

Planned C0227

Hybrid logical clocks are listed as a way to order events without perfect clocks. Plan for: device clock jumps; daylight saving; time zones. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

Is “Crash and power-cut safety” supported today, considering printer prints but sale lost?

Planned C0228

Atomic writes and journaling so a failure never loses a completed sale. Plan for: printer prints but sale lost; half-written receipt; battery drains. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

What should owners check about “Core and logistics isolation”, considering contract transport not chosen?

Built (repo) C0229

The ARCH module keeps logistics separate from the core POS so a fault in one cannot corrupt the other. In the repository, the app core and the Logistics core are separate code folders with separate database files, separate version numbers and a versioned contract, and a Logistics service can run as a separate process. This exists as tested library code only: there is no screen, the contract transport is not chosen and the process watchdog is not built. Plan for: contract transport not chosen; no watchdog yet; process isolation per platform not decided. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

Where does “Packaging engine” fit in Simca, thinking about spec validation?

Built (repo) C0230

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. It is not a website builder. Milestone 2 exists in the repository as Rust code with a command-line tool: a registry of every catalog element, a dependency resolver, a package-spec validator, a deterministic package container with a content-addressed cache, signed documents, delta manifests and a paired-development check. Only eight elements have real prebuilt artifacts; the other elements still have stubs, so the engine does not yet produce a full installable product. Plan for: spec validation; reproducible output; dependency resolution. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

Why does “Performance goals” matter for a small business, in particular regarding old hardware?

Planned C0231

The README says reliability over speed; the catalog lists performance targets as items. Plan for: old hardware; large catalogs; report speed. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

How does Simca approach “Data model”, especially around schema changes?

Built (repo) C0232

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. This exists as tested library code, with no screen. A changed shipped migration is refused, and no encryption at rest exists yet (an open decision). Plan for: schema changes; encryption at rest is open; kept data after removal. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

Is “Update model” supported today, especially around updating offline?

Not decided C0233

Acquisition is free (ADR-0007), which replaces the earlier buy-once and yearly-fee wording. A flat fee, charged quarterly and the same for every product including Simca Logistics, would apply only after a locally measured profit threshold that is tentative and not final. The fee is the quarter's published costs shared by the paying members, so it falls as members join (ADR-0008). Updates are signed packages applied only on the user's action. The fee calculator exists as library code with MOCK numbers; nothing is charged and no price exists. The threshold is not final. Plan for: updating offline; licence keys; downgrade. It is not decided.

Open this answer on its own page

Why does “Localization” matter for a small business, thinking about translation quality?

Planned C0234

English and Spanish, local number and date formats, accessible UI. Plan for: translation quality; right-to-left; currency symbols. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

How does Simca approach “Local logs and diagnostics”, considering support without telemetry?

Planned C0235

Logs stay on the device and are shared only on request. Plan for: support without telemetry; log size; privacy of logs. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

Where does “Launcher” fit in Simca, thinking about windows first?

Designed C0236

The one download. It is a regular program with no account of its own (ADR-0003). It installs, starts and updates Simca, shows a plain-sight Offline/Online toggle for the app's login mode and is the only place to pick, add or remove elements. When opened and connected it makes one disclosed update-manifest request and offers any update, even if the app is set to Offline. Groundwork exists as a tested library (spec writer, settings, signed update check, staging, rollback, offline install, removal choices) with a mock fetcher; there is no screen, no HTTP fetcher and no installer. Plan for: windows first; ios must match other platforms with apple limits checked later; shell technology not decided. It is designed in a document and no code exists.

Open this answer on its own page

Which edge cases come up around “Offline mode”, in particular regarding clock skew?

Designed C0237

Offline mode is a login mode of the app: the app signs into no cloud and makes no network request. It does not stop the launcher from making its one disclosed update-manifest request when it is opened and connected (ADR-0003). Plan for: clock skew; expired manifests cannot be detected offline; mixed online and offline devices. It is designed in a document and no code exists.

Open this answer on its own page

How does Simca approach “User-initiated signed updates”, considering power loss mid-update?

Built (repo) C0238

Updates are signed packages. The launcher offers a found update in a visible, dismissible notice; applying it is always the user's action. A signed file (USB, messenger, nearby device) works with no network. There is no background service, polling or telemetry. The update logic exists as tested library code with a mock fetcher; the HTTP fetcher and the screens are not built. Plan for: power loss mid-update; rollback; wrong-platform package. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

What should owners check about “Package spec”, with a focus on dependencies added automatically?

Built (repo) C0239

A small JSON file written by the launcher that lists the chosen elements. A v1 schema and an example exist in the repo; the packaging engine validates and hashes it, and the launcher library has a spec writer whose output is checked against the engine's schema. There is no launcher screen yet. Plan for: dependencies added automatically; pinned versions; no identity data in the spec. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

What should I plan for with “Online sign-in”, with a focus on sign-in method not decided?

Designed C0240

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. Selling never requires sign-in. Plan for: sign-in method not decided; disclosure screen; offline-first fallback. It is designed in a document and no code exists.

Open this answer on its own page

How does Simca approach “Elements, not roles”, with a focus on menu entries only from included elements?

Designed C0241

ADR-0001 removed separate role builds. One product, many elements; unselected elements are not compiled in. Presets such as store, bodega or driver are only pre-ticked selections, and all of them are Standard class (ADR-0003). Plan for: menu entries only from included elements; same pricing for every preset; permissions inside the app are ordinary permission sets. It is designed in a document and no code exists.

Open this answer on its own page

Why does “Paired development” matter for a small business, thinking about thin manifests with no business logic?

Built (repo) C0242

ADR-0002: every element is built first in Simca Packaging (thin manifest, prebuilt artifact, dependency links) and then immediately in Simca or Simca Logistics. The rule is now enforced from both sides: an element may be marked built into an app only with a prebuilt artifact, and the app pins the exact artifact it was built against. Eight elements (seven in the Simca core and the Logistics root) pass it today. Plan for: thin manifests with no business logic; acyclic dependency links; registry drift from the catalog. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

Where does “Build delivery” fit in Simca, with a focus on cache integrity on every read?

Built (repo) C0243

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. A deterministic container, a content-addressed cache, build counters that show the cache saves work, and delta plans exist as code. Only eight elements have real prebuilt pieces; 3,423 still have stubs, so a package of most elements is not installable. Plan for: cache integrity on every read; no timestamps in manifests; stub pieces make a package not installable. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

Which edge cases come up around “Offline/Online toggle”, in particular regarding lost device key?

Designed C0244

ADR-0002 and ADR-0003: the launcher shows a plain-sight toggle that governs only the app's login mode. Offline uses a local device-bound key and PIN with no registration; online uses cloud credentials, and registration is required only for online use. The launcher itself has no account in either mode. Designed, with no screen. Plan for: lost device key; mode shown at all times; sign-in never blocks selling. It is designed in a document and no code exists.

Open this answer on its own page

What should I plan for with “Update notice”, with a focus on the request reveals the network address to whoever serves?

Designed C0245

ADR-0003 replaced the earlier rule that nothing is contacted until the user presses Check. Whenever the launcher is opened and connected it makes one disclosed update-manifest request (a plain GET of a signed static file, no account data) and shows any update in a visible, dismissible notice. There is no polling afterwards. A manual Check repeats the request. A setting to turn off even the opening request is implemented in the library as recommended and its default is for the owner to confirm. Plan for: the request reveals the network address to whoever serves the file; dismissed until a newer version is known; setting to disable the request. It is designed in a document and no code exists.

Open this answer on its own page

What goes wrong with “Free start and the profit threshold” in a shop, with a focus on selling never stops because of the fee?

Not decided C0246

Acquiring Simca is free. A flat fee, charged quarterly and the same for every business and product, would apply only after the business reaches a profit threshold. The threshold is tentative, its figure appears only on the quarterly cost page, and how a business shows it is above the threshold without any telemetry is open. The repository recommends a user-initiated, signed band attestation, a rolling three-month average, a grace period and a dispute path; none of it is built. Simca Logistics pays the same fee as everything else. Under the tentative ADR-0009 rules a lapse stops only paid features, updates and online extras, and never locks a business out of its own books. Plan for: selling never stops because of the fee; businesses with no net-profit books; which services are charged is open. It is not decided.

Open this answer on its own page

How does Simca approach “iOS launcher parity”, considering replacing app files?

Designed C0247

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. Plan for: replacing app files; loading code; per-feature exceptions. It is designed in a document and no code exists.

Open this answer on its own page

What goes wrong with “Offline guard tests” in a shop, thinking about new dependencies need an allowlist entry?

Built (repo) C0248

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. The workspaces' test suites passed when we ran them on 2026-10-04 (460 tests in total across packaging, core, Logistics and launcher). They guard the code in the repository, not a shipped app. Plan for: new dependencies need an allowlist entry; applies to the code, not a future ui; passing today says nothing about later commits. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

Where does “The launcher's one opening request” fit in Simca, in particular regarding network address visible to the host?

Designed C0249

ADR-0003: the launcher has no account. When it is opened and connected it makes a single plain GET of a signed static update manifest. The request carries no account data and no identifier, there are no timers or background services, and the notice that results is dismissible. Like any web request it reveals the network address and the time to whoever serves the file, so the source is configurable (including a community mirror or none). The library tests count requests: one when enabled, zero when disabled or before the disclosure is answered. Plan for: network address visible to the host; manifest source is configurable; setting to disable the request. It is designed in a document and no code exists.

Open this answer on its own page

Which edge cases come up around “The launcher has no account”, thinking about offline mode governs the app only?

Designed C0250

ADR-0003: the launcher is free to download and use and has no login, profile or cloud state, like a game-store launcher. The app has its own login modes (offline key and PIN, or online credentials), and the launcher only offers updates and element choices. Plan for: offline mode governs the app only; online sign-in only for the four online features; no vendor account in any build. It is designed in a document and no code exists.

Open this answer on its own page

Where does “Simca's own launcher, forked from an earlier private one” fit in Simca, especially around reuse terms of the source not confirmed?

Not decided C0251

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. A document lists what was kept and removed, and a guard test keeps those things out. The reuse terms of the source code and the shell technology (Electron with a Rust sidecar, or Flutter) are open. Plan for: reuse terms of the source not confirmed; shell technology open; no ui built. It is not decided.

Open this answer on its own page

Why does “What the app core can do today” matter for a small business, considering no user interface?

Built (repo) C0252

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). Only cash payment exists, quantities are whole units, and there is no printing, hardware, card payment, fiscal document, encryption at rest or permission logic yet. Plan for: no user interface; cash only; whole-unit quantities. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

Which edge cases come up around “What the Logistics core can do today”, considering reputation math is a draft?

Built (repo) C0253

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. It has no screen, no board distribution channel (local network, Bluetooth, QR, SMS code, relay), no GPS, no fleet or documents and no watchdog. Plan for: reputation math is a draft; board distribution not built; no screen. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

What should I plan for with “The quarterly cost model”, with a focus on no margin means no cushion for higher costs?

Built (repo) C0254

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. There is no opening multiple, no 10x limit and no margin on top. It starts high when few share it and falls as members join. There is no launch premium, no surplus and no per-member ceiling, and never a percentage of revenue. The calculator exists as library code with MOCK numbers (currency XXX); a mock model cannot become a price table. Plan for: no margin means no cushion for higher costs; the first members may pay a large share; grace and dispute lengths are drafts. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

What goes wrong with “Your bill has dropped X percent” in a shop, thinking about needs the starting quarter kept locally?

Built (repo) C0255

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. It sends nothing anywhere. It refuses an unsound history (missing signature, out-of-order quarters, expired or mixed mock and real documents). The calculation exists as library code; the launcher screen that would show it does not. Plan for: needs the starting quarter kept locally; rose is reported as rose; no screen yet. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

Where does “Two independent signatures on price documents” fit in Simca, in particular regarding ceremony not done?

Built (repo) C0256

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. This is enforced in code and tests with throwaway test keys. The key ceremony (who holds the keys, the second signer, offline custody) has not been done, so no real price can be published. ADR-0009 (tentative) sketches two independent custodians in separate legal entities with their own offline hardware keys; none exists. Plan for: ceremony not done; second signer not chosen; losing both keys of one side stops publishing. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

What should I plan for with “Entitlement per package”, in particular regarding host design open?

Built (repo) C0257

ADR-0006 and ADR-0007: a package is used offline under a signed entitlement file that names the package and its elements. Its licence kind is free; an updates-until date is a reserved mechanism that never ends the right to run the installed version or to reach one's data. Online features need short-lived signed grants from the company host; the host and key custody are not built. Plan for: host design open; device binding open; grant renewal fails soft. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

Why does “The customer app front end is a plan” matter for a small business, in particular regarding windows 7 and 8.1 support open?

Designed C0258

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. Nothing was scaffolded because Flutter could not be installed on the build machine. Old Windows 7 and 8.1 shops cannot run current Flutter, so the toolkit decision is tied to the hardware survey. Plan for: windows 7 and 8.1 support open; two toolchains per build; receipt printing not designed. It is designed in a document and no code exists.

Open this answer on its own page

What should I plan for with “No margin on the fee”, thinking about no cushion for cost shocks?

Not decided C0259

ADR-0009 (tentative): the fee is the plain cost split with nothing on top. The owner accepts running at cost, plans to compete on price and expects to earn later from adoption. The repository records the risk: there is no cushion, so a cost that turns out higher than published raises members' bills the next quarter or is carried by the owner. It recommends a quarterly review of every cost line before signing, and leaves open an optional published runway-reserve line and a limit on cost growth. Plan for: no cushion for cost shocks; a reserve line behaves like a margin if large; adoption may be slower than hoped. It is not decided.

Open this answer on its own page

What is the plan for “Owner pay and affiliated-company costs”, with a focus on the signing process cannot know who is affiliated?

Built (repo) C0260

ADR-0009 (tentative): the owner may pay himself and his other companies from the cost base. Every cost line carries a related-party flag that cannot be omitted; such lines are shown separately and labelled, with an optional documented basis (otherwise it says no basis documented), and they sit inside the split, never on top. The calculation and the public view exist as code with MOCK data. The flag is only as honest as the person who sets it. Plan for: the signing process cannot know who is affiliated; the second signer may be related to a line; a lawyer should say if more disclosure is needed. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

How risky is “Public and private donations” to get wrong, with a focus on tax and accounting treatment is open?

Built (repo) C0261

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). Private donations are never in signed or published data, so they do not change the fee. The cost page states that it lists the costs that make up the fee and that the company keeps its other finances private. The page is the company's own statement and not an audit. Plan for: tax and accounting treatment is open; donor identity only with consent; not an audit. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

Which edge cases come up around “Billing, notices and what a lapse stops”, especially around which services are charged is open?

Not decided C0262

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. Businesses approaching the profit threshold get two milestone notices with a non-binding estimate of next quarter's fee (the projected price plus a disclosed 15% buffer), only if they use the charged services. A lapse stops only paid features, updates and online extras; the software stays free and books, sales data and retained records are never locked, which the code tests. Grace and dispute lengths are drafts for a lawyer. Threshold detection is local and sends nothing. Plan for: which services are charged is open; milestone levels and the buffer are drafts; no payment flow exists. It is not decided.

Open this answer on its own page