Beta Terms of Service

1. Acceptance

By creating a SKENAI Beta account — or by using any gated network surface after sign-in — you agree to these Beta Terms of Service, the Beta SLA summary above, and our Privacy Notice. If you do not agree, do not use the beta program.

Version 2026-08-22 adds explicit Terms acceptance on web, WOW (Workspace), WOT (Telegram), and TMA (Telegram Mini App), plus Telegram link/disconnect membrane rules. Prior acceptances at version 2026-07-20 require re-consent on next session.

2. Beta program scope

Beta access lets you explore SKENAI Passport, Stack Hopper, Workspace (WOW), William on Telegram (WOT), the Telegram Mini App (TMA), knowledge ingestion, Connect highways, and the marketplace economy under evolving product rules. Features may change, break, or be withdrawn without notice.

2a. XP balances and leaderboard (beta caveat)

During beta, XP balances shown in Workspace (`gforce_profiles.xp_total` and the Network Leaderboard) are operational counters used for tiers, admissions, and spend gates. They are not yet backed by a complete, replayable audit log on all mint paths.

A July 2026 forensic audit found that leaderboard rankings can diverge from measured William activity (WOT/WOW turns, jobs). Do not treat leaderboard position as proof of network contribution until ledger hardening ships.

The Admin “Activity index (30d)” is a separate heuristic (William + work signals) and is not XP balance. See `docs/XP-LEDGER-METHODOLOGY-2026.md` in the repository for methodology.

2b. Network surfaces (Passport → WOT → Stack → WOW)

SKENAI is a federated survey and settlement network. During beta the primary tenant journey is: Skenet Passport (identity) → WOT (Telegram capture) → Stack Hopper at `/stack` (persistent hopper room) → WOW (web weave, Workspace, and marketplace dispatch).

The Telegram Mini App (TMA) is a compact shell over the same identity and receipt spine — not a separate legal entity or wallet. Surface-specific behavior is described in product; economic finality remains on the settlement spine (`william_action_log`, XP chokepoint, Passport export).

• Passport — tenant identity, Carnet, and admission receipts.
• WOT — William on Telegram; paste, file ingest, and chat when linked to your web account.
• Stack Hopper — private cortex indexing; network sharing requires explicit consent flags.
• WOW — Workspace, William terminal, marketplace jobs, and Connect highways on skenai.net.
• TMA — Telegram Mini App gate; same Terms and identity membrane as WOT when linked.

3. Use of your network activity to improve the network

You acknowledge that SKENAI processes your activity on the network — including job completions, William interactions, knowledge uploads, and telemetry needed to operate the service — to operate, secure, and improve the SKENAI network.

Aggregated and de-identified metrics may be used for product improvement, reliability, and public transparency indexes (such as the network ledger and verified SURFACE briefs).

Public citation of your tenant-specific content or jobs requires explicit consent flags in product (`share_consent`, `network_surface_mention`) or falls under platform settlement receipts described in our Privacy Notice.

3a. Network surveyor membrane (consent is the product)

SKENAI is a survey network — not a covert surveillance product. Historic surveyors mapped land with permission so settlement could occur; network surveyors map consented edges so economic settlement can occur.

When you use Workspace, Connect, William, or related surfaces, you may grant per-surface survey rights. Each surface declares what coarse signals it may record (for example session duration bands, surface switches, William turn metadata, or URLs you explicitly submit on the Connect highway). We do not capture raw keystroke content or background clipboard data during beta.

Survey rights are a core value driver: better maps → better stacks → better receipts on the settlement spine. You may revoke optional surfaces when product controls ship; Architect-tenant dogfood surfaces are labeled in the operator mirror.

Operator and survey receipts store `consent_version` and tenant SPAN so traverses are provable on the Redős trail — not repudiable side logs.

• Default beta: Architect-tenant dogfood only for operator session signals unless you opt in to additional surfaces.
• Connect highway: explicit URL/paste/API ingest only — no silent browser follow.
• RATIO/defense lanes use SBL-soft survey language; never unsoftened surveillance claims.

3b. Multi-surface Terms acceptance

You must affirmatively accept these Terms before using gated SKENAI surfaces. The product enforces a checkbox and “Agree and continue” (or Telegram `/accept_terms` on WOT) on: skenai.net web login and signed-in pages, WOW (Workspace and related web shells), WOT (Telegram bot, after account link), and TMA (Telegram Mini App).

Acceptance is recorded in your account metadata (`network_terms_version`, `network_terms_accepted_at`, `network_terms_surface`) and as a terminal receipt in `william_action_log` with action type `network_terms_accepted`. We bump `network_terms_version` when material terms change; stale versions require re-consent.

Contributor execution slots use a separate Contributor Agreement (§13) after platform Terms are satisfied. Platform Terms and Contributor Agreement are distinct contract layers.

• Web / WOW — `/legal/beta-terms` gate via Network Terms enforcer after sign-in.
• WOT — `/accept_terms` after `/link`; unlinked users may use help/start/link only until linked and accepted.
• TMA — full-screen gate before Mini App tabs; bearer session bound to the same web identity.

3c. Telegram identity membrane (enter naked / leave naked)

Linking Telegram to your skenai.net account (“enter naked”) binds WOT (Telegram) and WOW (web) to one economic actor with shared William memory when the bridge is active.

Disconnecting Telegram (“leave naked”) severs the WOT ↔ WOW bridge. SKENAI protects network assets: settled contributions remain valued, and an exit settlement (exit tax) may apply before the membrane bond is released. Settlement math for exit levies is UNVERIFIED during beta until the VERIFIED economic epoch is ratified.

After leave naked you restart as a new economic actor for membrane purposes. Re-linking later is enter naked again — prior membrane state, provisional tiers, and unsettled bridge assumptions do not carry forward automatically.

If you hold a provisioned shoe or VPS through higher tiers, breaking the Telegram bridge may breach thermodynamic contract assumptions for that lane. Plan for immediate liquidation or contingency per your tier — product labels such lanes UNVERIFIED until ratified.

• Leave naked requires explicit confirmation in Profile before unlink.
• Disconnect emits a `telegram_leave_naked` receipt; re-link uses the standard Connect Telegram ceremony.
• While linked, Connect Telegram CTAs are hidden — the membrane is already closed.

4. Privacy and consent

SKENAI respects your privacy and follows strict consent protocols before naming your tenant, jobs, or knowledge in public network publications.

We align our practices with established privacy frameworks cited in the Privacy Notice, including GDPR principles, California consumer privacy rights, and NIST privacy risk management.

You may control KB sharing via visibility and `share_consent` settings, and marketplace surface mentions via `network_surface_mention`. Contact privacy@skenai.net for access or deletion requests.

5. Acceptable use

• Do not upload unlawful content, others’ confidential data without authorization, or malware.
• Do not attempt to bypass tenant isolation, RBAC, or admission controls.
• Do not scrape or overload production APIs beyond documented limits.

6. Beta disclaimer

THE BETA SERVICE IS PROVIDED “AS IS” WITHOUT WARRANTIES. TO THE MAXIMUM EXTENT PERMITTED BY LAW, SKENAI’S LIABILITY FOR BETA USE IS LIMITED TO THE GREATER OF (A) AMOUNTS YOU PAID SKENAI IN THE TWELVE MONTHS BEFORE THE CLAIM OR (B) ONE HUNDRED U.S. DOLLARS ($100).