# WG Paid / MGTS — Global Project Plan

**Updated:** 2026-08-24  
**Purpose:** compact long-range project direction. Detailed current work belongs in `03_WG_PAID_MGTS_CURRENT_LOCAL_PLAN.md`.

## End goal

Build a production VPN service where:

- users can be invited/onboarded through a safe public browser flow;
- access grants/plans govern protocol/profile entitlement;
- WireGuard and later AmneziaWG profiles are provisioned durably;
- actual peers are managed on VM100;
- active users are distributed across healthy VM101 egress slots;
- VM101 recovers provider egress autonomously;
- credentials, SMTP secrets and backups stay outside public evidence;
- operations/release/publication remain reproducible through VM130;
- future subscriptions/payments/entitlements can sit above the same account/profile model.

## Closed foundation

- five-egress VM100/VM101 runtime and autonomous recovery;
- public WG Paid endpoint `wg-studio.secret-studio.ru:51830`;
- VM121 Domain V2 account/profile/credential/provisioning model;
- production credential keyring;
- invite/magic-link/session authentication;
- config/QR/revoke/reissue;
- external client/public path proof;
- production SMTP;
- GitHub-backed Machine Git for VM100/101/103/121/130;
- VM103 public TLS/browser/report ingress;
- fragment-based magic-link URL and real browser session proof;
- external onboarding enabled;
- trusted-pilot plan and private admin authorization;
- first trusted production user, active WG profile, credential, completed provisioning job and VM100 runtime peer;
- authenticated profile config delivery with `no-store`;
- VM130 bootstrap retention/post-PASS hardening.

## Current stabilization phase

1. simplify Project Sources and move history out of active context;
2. settle P27C documentary/procedural closure without repeating accepted production onboarding;
3. restore intended VM100 active-user selector allocation semantics with a minimal VM100-only change;
4. validate ordinary durable session/profile lifecycle and operational support paths proportionally.

## Next protocol phase — P28

Add AmneziaWG under the same ownership model:

```text
user -> grant -> ConnectionProfile -> credential revision -> provisioning job
```

Do not duplicate account/business state or selector logic. Protocol-specific implementation belongs behind the existing abstractions; VM100 remains peer/selector authority and VM101 remains egress authority.

## Later product phases

- subscription lifecycle / entitlements;
- payments;
- referrals;
- operational monitoring and alert transport;
- support/recovery workflows for failed onboarding/provisioning;
- user-facing product UX;
- analytics;
- additional protocols only where the existing ownership model can be reused.

## Planning rule

Global milestones describe **capabilities**, not every release attempt. R01/R02-style failure history is evidence/archive material and does not belong in this plan.