Detwin modules

AGVM Core stays open. Advanced capability ships as signed modules.

Clone, Grow and Maintain are activated by the Detwin account. In cloud they are enabled by workspace entitlement; locally they require a signed lease and module runtime receipts.

Pro

Clone App

Focused clone chat and teaching surface for one selected AGVM brain.

Cloud
Cloud-ready
Local
Signed lease and install receipt required
Source
private module image
Start Pro
Pro

Grow Studio

Source intake and memory growth workflows packaged as a private module.

Cloud
Cloud-ready
Local
Signed lease and install receipt required
Source
private module image
Start Pro
Pro

Maintain Studio

Maintenance, consolidation and review workflows packaged as a private module.

Cloud
Cloud-ready
Local
Signed lease and install receipt required
Source
private module image
Start Pro
Pro Plus

Auto Memory

Scheduled health review, sleep/evolve previews and proactive teach questions for Pro Plus workspaces.

Cloud
Planned automation
Local
Signed lease and install receipt required
Source
private module image
Start Pro Plus
How module delivery works

One plan, two runtimes, one account.

Cloud and local AGVM read the same account policy. The difference is delivery: cloud can enable modules immediately inside the hosted runtime; local AGVM must prove a signed lease and install/update status.

1

The user signs in and chooses Pro or Pro Plus.

2

The payment provider confirms the subscription through server-side entitlement.

3

Cloud AGVM enables modules for the workspace automatically.

4

Local AGVM downloads private module images through signed install plans and reports receipts.

Not bypassed by UI state

Buttons can be hidden for clarity, but the real gate is account entitlement plus signed lease/token checks.

Future registry target

Private module images should be published to an authenticated registry such as AWS ECR and requested through Detwin install tokens.