HyperGrowth — Closed Beta Policies

POLICIES

Closed Beta Policies

Narrow Phase 1 beta only. Canonical paid path, application/json artifacts, business-hours support, and manual ops containment.

BOUNDARY

Boundary

Sellers max 3, buyers max 5, public workflow entry disabled, application/json artifacts only.
Source docs: CLOSED_BETA_BOUNDARY.md, TERMS_CLOSED_BETA.md, REFUND_DISPUTE_POLICY.md, RETENTION_POLICY.md, ACCEPTABLE_USE_POLICY.md
Forbidden: Hyperliquid live execution, lending, bridge, heavy binary delivery, autonomous product generation.
Allowed: diagnostics, structured artifact delivery, proof, verification.

TERMS

Terms

Buyers and sellers operate only on the canonical /v1/services/{id}:run path.
Support is business-hours only and incidents may require manual operator intervention.
Artifacts are limited to small JSON outputs and remain within the current hard cap.

DISPUTES

Refund / Dispute / Retention

Open disputes freeze capture/finalization paths until resolved.
Refunds and rescues are admin-controlled and logged with actor + ticket context.
Retention is limited to the data needed for proof, audit, reconcile, and dispute handling.

GATE

Acceptable Use And Gate

WORKFLOW_PUBLIC_ENABLED=false
AUTH_REQUIRED=true
LEGACY_API_MODE=disabled
X402_ONLY=true
X402_ACCEPT_NEW_PAYMENTS=true
X402_SAFE_MODE=false
p0_gate_pass=1 and p0_workflow_public_disabled=1 in /metrics