Skip to content
HOwFar logo
HSuper-App Operating System
Get Started
HOwFar logo
HSuper-App Operating System
Get Started
Home/Status
HOWFAR PUBLIC PAGE

Status

Operational status and incident communications.

Last updated: 4/30/2026, 10:59:19 PM
GUIDED DISCOVERY
Readable, inspectable, and linked to action.

Every public HOWFAR page should feel like part of the same living system: clear hierarchy, visible trust cues, and direct routes to support, contact, and product.

Current status

All systems operational.

Operational readiness is currently 100/100, with 16/16 evidence-backed checks passing across architecture, implementation, foundation, and operational categories.

Evidence-backed readiness score

  • Architecture: 100/100 (4/4 checks passing)
  • Implementation: 100/100 (4/4 checks passing)
  • Foundation: 100/100 (4/4 checks passing)
  • Operational: 100/100 (4/4 checks passing)

Machine-readable proof is available at /api/proof/scorecard.

Public verification routes

  • Readiness scorecard API — Machine-readable category scores derived from repo evidence and verification scripts.
  • Trust center API — Summary of public proof links, buyer-ready routes, and known open gaps.
  • Feature matrix API — Detailed capability-by-capability reality check showing which features are LIVE, PARTIAL, or PLANNED.
  • Marketplace inventory proof — Public proof artifact covering stock deduction, sold-out transitions, seller publishing guards, and oversell prevention.
  • Developer platform proof — Public proof artifact covering developer app registration, one-time key issuance, bearer verification, per-key limits, and docs/OpenAPI sync.

Current focus

  • Feature activation is still broader than the current live surface: The detailed feature matrix still includes PARTIAL and PLANNED capabilities, so the repo now tracks honest completion through a strict activation manifest instead of flipping everything to LIVE by declaration.
  • Public load and failover artifacts are still pending: The k6 harness is in-repo and the Windows Docker path handling was hardened, but smoke/stress artifacts still need to be generated and published before stronger resilience claims are fair.
  • Browser E2E artifacts for commerce are still pending: Marketplace and subscription critical paths are now integration-tested, but public browser E2E artifacts for seller onboarding, checkout, and self-serve billing are not yet published.

How we communicate incidents

  • We post updates on this page during incidents.
  • We publish a short post-incident summary when applicable.

Need help now?

If you’re experiencing an issue, visit Support or Contact.

Need help? Visit Support or Contact.

Dock