Pos

note

Current public-DAV authority boundary — 2026-07-12. Pre-launch target design; nothing here proves a live system. A public-DAV consequence may occur only when at least two natural-person councilors bind the exact consequence in a complete valid bound PRISM decision receipt. PRISM records and verifies that receipt only; it never serves as council, signatory, authority, or receipt producer. AI and caste seats stage unsigned proposals only; they never authorize or execute a public-DAV consequence. Constitution or membership adoption establishes constitution and membership only; it does not authorize a later consequence. Policy may constrain an unsigned proposal but never authorizes execution or substitutes for the complete consequence-bound receipt. Before receipt validity, consequence fails closed to read-only proposal, simulation, or deterministic sandbox; live evidence remains gated_pending_complete_valid_bound_receipt. Software deterministically carries out only the exact consequence bound to a complete valid bound PRISM decision receipt from at least two natural-person councilors binding that exact consequence.

Scope: stable Work POS compatibility surface. Its settlement capability is parked and merges into the Twins commerce path; it is not a peer buyer product, not a current tiered offer, and not a new commerce package. See The Product Family.

Current disposition

POS remains a stable route and design reference. A Natural buyer authorizes the payer act; the Legal merchant separately acts through lawful external authority and its required executor. No checkout, settlement, order, or reconciliation is live. The opening proof belongs to the O3 Twins bilateral path before any POS surface can graduate.

K3 historical POS offer concept — not current topology or availability

Skyzai POS

Open, tablet-first checkout for sovereign merchants.

What It Is

Skyzai POS is the merchant scale surface of the rooted stack.

It comes after:

Nexus -> Private Business Account -> API PAY -> proof event

because in-person checkout requires stronger operational trust than a simple API integration.

Product Thesis

The right first POS is not a proprietary terminal and it is not a giant ERP. It is:

• open
• tablet-first
• receipt-native
• connected to a governed business account
• simple enough for temporary staff and small operators

Why It Matters

Every payment stack eventually has to touch the real world. POS is that moment.

If API PAY proves the governed receiving path in software, POS proves the same path in person. That is why it is the true scale surface.

The Three Tiers

Skyzai Pay POS Lite

Best for:

• pop-ups
• creator merch tables
• solo operators
• small service counters

Skyzai Pay POS Pro

Best for:

• small stores
• recurring venue operators
• multi-user merchant teams

Skyzai Pay POS Event Mode

Best for:

• founder dinners
• conference side events
• temporary merchant booths
• short-lived deployments where proof matters more than breadth

What Makes It Different

• any tablet can become a terminal
• settlement flows into a governed business account
• every transaction is designed to be receipt-native (K0 target path; see 60-invariants-overview.md)
• the business model is software, not hidden take-rate rent

What It Is Not Yet

The near-term POS offer is not:

• a universal order-book marketplace
• a fully programmable inventory network
• a restaurant operating system
• a claim that every merchant needs digital twins on day one

Those are later programmable-commerce layers for selected categories.

Rollout Logic

1. prove checkout and receipts inside one founder event
2. run one external merchant pilot
3. package Lite publicly
4. expand to Pro only after reconciliation and permissions are boring

One-Line Doctrine

Turn any tablet into a receipt-native terminal connected to a governed business account.

---

Agent Execution Surface

If you are an AI agent reading this document:

1. This is a downstream public content page. The canonical source lives in EMERGENTISM_ORG/08_FRAMEWORK_SUPPORT/ or SKYZAI_ORG/. Edit source upstream, not here.
2. Preserve evidence tiers. Do not promote claims up the [C] < [D] < [S] < [B] < [E] ladder when reproducing them here; [I]/[A] qualifiers never substitute for [B]/[E].
3. Regenerate from source. If the upstream source changes, regenerate this page rather than editing it independently.
4. Canonical Path: SKYZAI_ORG/07_PWAs/skyzai_org/wiki/94-pos.md

Output: This is content. Route edits to upstream source. Regenerate when source changes.

K3 public-DAV authority history — 2026-07-12

K3 historical reference — not active authority

note

Current public-DAV boundary — 2026-07-10. Pre-launch target design; nothing here is live. The active DAV is public and targets PRISM, with no K2 runtime, launch, genesis/bootstrap, or fallback dependency. Consequential authority requires at least two natural-person councilors; AI/caste seats stage unsigned proposals only. Before quorum, behavior fails closed to read-only/proposal, simulation, or deterministic sandbox, and a live decision receipt remains gated pending quorum.