Wiki 🔍 Search
QIIUB · System status

POS v1 end-to-end — partner to merchant to device to sale

Where the platform stands against the declared milestone. Every figure on this page is read from the module scorecards, the capability registry, and the POS spec corpus — this page stores no facts of its own.

Milestone declared by mgandia on 2026-07-28 — the destination is a business decision, not a measurement.

6 of 31 modules
Merchant modules measured
Counted over the 31 merchant modules in the registry — not over code folders, and not over capability coverage; those are different universes with different totals. An unmeasured module is 0% measured, not 0% built. The 12 platform/admin modules are a separate universe and none is analyzed yet.
55
Known gaps
Across the 6 measured modules only — the universe is not yet swept. 43 carry a stable feature ID; 12 are un-IDed bundles. A further 2 rows are struck through in the scorecard — counted as resolved, not as open work.
6
Journey stages
Owner-declared order. A stage's state is a human's reading of the artifacts, except where it is derived from the spec corpus.

The journey to this milestone

Board a partner complete
CAP-03 · Shipped
Partner boards a merchant complete
CAP-03 · ShippedCAP-04 · Shipped

Greenfield boarding. Migrating an existing merchant off a reference system is NOT on the path to this milestone (CAP-19, spec'd with no code) and is deliberately not a stage here.

Merchant sets itself up complete
CAP-05 · ShippedCAP-08 · Shipped
Device pairs with the platform blocked
CAP-14 · In-Progress

Activation API shipped (ADR-0115); the POS client still uses LocalActivationProvider and FakeBootstrapClient. Gated on #531; QA path blocked by #810.

Device receives its configuration not started
No capability in the registry covers this stage — a gap in the capability list, not an omission here.

No config-down path exists — runBootstrap carries identity only. Not represented in CAPABILITIES.md; candidate missing CAP row.

Sell within the v1 ceiling derived from specs
CAP-07 · ShippedCAP-11 · Shipped

BUILD-blocker POS-PRINT-001 — print sale receipt, priority must, offline full. Its own Overview calls it THE v1 blocker to ship, and src has no QuestPDF or IDocumentTemplate (corroborated by CAP-18, Spec'd). Not a scope-blocker: the v1 scope-lock required only that its spec exist, and it does.

100 v1 specs79 must · 16 should · 5 could
status: 100 proposed
Every spec still sits at proposed. The status field does carry build states, so this is an unused axis rather than a missing one — which means build state is unrecorded here and this page will not guess a built/unbuilt split.
Derived from docs/design/pos at render.

Areas

fully measured   partly measured   not measured — these lights show MEASUREMENT coverage, not health. A green area has been looked at, which is not the same as an area that works.

Inventory & Supply Chain 6/9 measured
Catalog 0/5 measured
Sales & POS 0/5 measured
Customers & Accounts 0/3 measured
Workforce 0/1 measured
Reporting 0/1 measured
Locations & Configuration 0/7 measured
Feature-detail pages exist for 1 of the 6 measured modules; the rest link straight to their scorecard, and each module page says which.