Skip to content

SAGIO HQ

The company operating view: where we are going, what exists, who owns it, what is moving, and what happens next.

Browse engineering docs Open GitHub Project

What HQ answers

  • Where are we going? — The company vision, product thesis, strategic bets, and the boundaries we will not blur.
  • Who owns what? — Accountable owners, contributors, decision rights, and escalation paths by product surface.
  • What happens next? — Now / next / later priorities connected to issues, pull requests, acceptance conditions, and evidence.
  • Is it actually done? — Work closes only with an artifact, evidence, a state update, and a recorded next decision.

Vision

SAGIO gives merchants one coherent way to accept money, run the business around that money, and build durable customer relationships—without forcing them to become payments experts.

We are building a multi-rail merchant system across Terminal, Wallet, Merchant, API, and Landing. The separate x402 facilitator remains a related service with its own repository boundary.

Read the complete vision

Current company state

Area State Evidence Next
Merchant VIP memberships In progress Issue #357 · draft PR #359 Complete cross-app verification and review
Receipt settlement integrity In review draft PR #358 Complete required checks and contract review
Shopify integration Backlog Issue #352 Prove platform access and minimal lifecycle first

Open the full roadmap · See the generated GitHub pulse

What we have done

The GitHub Project currently records 104 items across the product history. Completed areas include core merchant analytics, wallet payments, product and order management, customer ordering, test infrastructure, merchant workflows, and delivery improvements.

Completion in HQ means more than a closed issue: every claim should attach to an artifact, evidence, a state update, and a next decision.

See the definition of done

Team

Person Observed contribution area Current open assignment
Lulzx Cross-product implementation, API, Dashboard, Wallet, Terminal, delivery, and repository operations VIP memberships · Shopify integration
Chris Kwon Cross-product contribution history, wallet/payment work, and Terminal operational verification None in current open issue snapshot
Priyanshi Dashboard and Wallet work, including product/order management and customer ordering None in current open issue snapshot

Team details

Ownership

Product surface Current accountable owner Ownership state
Company vision and sequencing Lulzx Current
Payments and integrations API Lulzx Inferred from active assignments; confirm formally
Terminal To confirm Contributors: Lulzx, Chris
Wallet To confirm Contributors: Lulzx, Chris, Priyanshi
Merchant Dashboard To confirm Contributors: Lulzx, Priyanshi
Landing To confirm Team contribution
x402 facilitator Confirm in facilitator repository Separate product/service boundary

Open the ownership map

Roadmap and timing

Horizon Outcome Owner Timing rule
Now Close VIP membership and receipt-integrity loops Lulzx Ship after acceptance evidence and required review
Next Validate Shopify platform access and lifecycle assumptions Lulzx No delivery date until external access and scope are proven
Later Sequence loyalty, intelligence, and additional integrations To assign Move forward only with an owner and tested premise

Dates are not invented from issue order. A delivery date is added only when scope, ownership, dependencies, and acceptance conditions are known.

Roadmap details

GitHub pulse

Signal Current snapshot
Open issues 2
Open pull requests 2 drafts
Active private project V1 Dashboard MVP
Project items 104

The detailed pulse is generated from the private repository at build time, so no GitHub token is exposed to the browser.

Issues and PRs · GitHub Project · Repository

How SAGIO works

SAGIO uses the Reality Loop: orient, choose, act, observe, verify, and update. Work is organized as verified iterations rather than unbounded tasks.

Read the manifesto · Decision log · Engineering docs