ContriveAtlas
neostory-schema-set/22snapshot a59c206cec9d
Open Observatory

Platform boundaries · Deployment business cases

Dedicated deployments and shared infrastructure

Two business cases share one management contract: customer control through a dedicated environment, and quicker creation and trimming through retained parent infrastructure. Their evidence levels differ.

Business · Partners · Engineering · Operations
DeclaredImplementedObservedPlanned
neostory-schema-set/22snapshot a59c206cec9d

Platform boundaries · Deployment business cases

Dedicated deployments and shared infrastructure

Two business cases share one management contract: customer control through a dedicated environment, and quicker creation and trimming through retained parent infrastructure. Their evidence levels differ.

Business · Partners · Engineering · Operations10 nodes · 12 directed relationships

What this view establishes

The architectural commitments

  1. Dedicated deployment serves customer control; shared infrastructure serves efficient environment creation and trimming.
  2. Shared-pool isolation is observed locally, including restart and sibling preservation; hosted shared-pool operation is not yet accepted.
  3. Multi-tenant here means isolated child resources on retained infrastructure, not unrestricted shared data or shared-table tenancy.
  4. Browser-driven create/duplicate/retire is implemented behind the same session-derived admin authority, a bound single role store and a hard capacity cap; hosted acceptance (Phase 4) is Astra's to run.

Layered platform stack

01
03

Dedicated customer control

dedicatedobserved

Dedicated environment

Separate application authority, database, object storage and credentials.

stagesdeclared

Development to production

Stage and domain identity stay separate from placement choice.

dedicated-proofobserved

Hosted pilot proof

Historical three-client journey; not a production availability claim.

02
03

Shared infrastructure efficiency

poolimplemented

Retained parent pool

Capacity reservation and placement bind a child to its parent.

childrenobserved

Isolated child environments

Separate database roles, object users and bucket policies.

trimobserved

Trim one child

Restart adoption and deletion preserve sibling data and the parent.

03
04

One management surface

adminimplemented

Authorized admin view

Projects, environments, release identity, status and admitted actions.

hosted-poolplanned

Hosted shared-pool service

Provider-specific operations, quotas and isolation acceptance remain.

recoveryplanned

Safe recovery

Unresolved effects refuse recovery until server reconciliation is proven.

browser-lifecycleimplemented

Browser-driven lifecycle

Create, duplicate and retire an environment from the admin panel: an admission-gated owner bootstrap, a session-derived actor re-checked on every action, one bound role store, and a hard global capacity cap (default 10 live environments) enforced in plan and again inside create's transaction. Duplicate copies a source's release and domain pins plus its stage/region/recipe/retention configuration into a fresh isolated child -- never its data. Retire reuses the existing bounded delete/trim, confirmed by exact target and generation match. Recovery stays refused. Hosted acceptance is pending -- Phase 4 is Astra's to run against a disposable hosted environment.

Connections and evidence

Open the 12-relationship source key

Numbers set an explanatory reading order. They do not measure runtime timing.

  1. 01

    Dedicated environmentHosted pilot proof

    hosted demonstration

    observed
  2. 02

    Development to productionAuthorized admin view

    project and stage identity

    implemented
  3. 03

    Retained parent poolIsolated child environments

    reserve and provision

    implemented
  4. 04

    Isolated child environmentsTrim one child

    child-only cleanup

    observed
  5. 05

    Authorized admin viewRetained parent pool

    manage local placement

    implemented
  6. 06

    Authorized admin viewDedicated environment

    inspect registered state

    implemented
  7. 07

    Retained parent poolHosted shared-pool service

    next provider acceptance

    planned
  8. 08

    Authorized admin viewSafe recovery

    unavailable today

    planned
  9. 09

    Authorized admin viewBrowser-driven lifecycle

    authorizes via session-derived actor

    implemented
  10. 10

    Browser-driven lifecycleIsolated child environments

    create/duplicate provisions a fresh isolated child

    implemented
  11. 11

    Browser-driven lifecycleTrim one child

    retire reuses the bounded delete/trim path

    implemented
  12. 12

    Browser-driven lifecycleHosted shared-pool service

    hosted acceptance pending (Phase 4)

    planned

Connections and evidence

12 directed, source-backed relationships

Numbers set an explanatory reading order. They do not measure runtime timing.

  1. 01

    Dedicated environmentHosted pilot proof

    hosted demonstration

    observed
  2. 02

    Development to productionAuthorized admin view

    project and stage identity

    implemented
  3. 03

    Retained parent poolIsolated child environments

    reserve and provision

    implemented
  4. 04

    Isolated child environmentsTrim one child

    child-only cleanup

    observed
  5. 05

    Authorized admin viewRetained parent pool

    manage local placement

    implemented
  6. 06

    Authorized admin viewDedicated environment

    inspect registered state

    implemented
  7. 07

    Retained parent poolHosted shared-pool service

    next provider acceptance

    planned
  8. 08

    Authorized admin viewSafe recovery

    unavailable today

    planned
  9. 09

    Authorized admin viewBrowser-driven lifecycle

    authorizes via session-derived actor

    implemented
  10. 10

    Browser-driven lifecycleIsolated child environments

    create/duplicate provisions a fresh isolated child

    implemented
  11. 11

    Browser-driven lifecycleTrim one child

    retire reuses the bounded delete/trim path

    implemented
  12. 12

    Browser-driven lifecycleHosted shared-pool service

    hosted acceptance pending (Phase 4)

    planned

What this view establishes

The architectural commitments

  1. Dedicated deployment serves customer control; shared infrastructure serves efficient environment creation and trimming.
  2. Shared-pool isolation is observed locally, including restart and sibling preservation; hosted shared-pool operation is not yet accepted.
  3. Multi-tenant here means isolated child resources on retained infrastructure, not unrestricted shared data or shared-table tenancy.
  4. Browser-driven create/duplicate/retire is implemented behind the same session-derived admin authority, a bound single role store and a hard capacity cap; hosted acceptance (Phase 4) is Astra's to run.

Follow the live system

The Atlas is static and source-backed. The Observatory shows authenticated environment state.

16 repository sources behind this view
  • docs/delegation/browser-driven-lifecycle-2026-09-12.md
  • docs/delegation/browser-driven-lifecycle-design-2026-09-12.md
  • docs/delegation/platform-groundwork-landing-2026-09-11.md
  • docs/platform-business-cases.md
  • docs/releases/evidence/records-v2-provider-readiness/hosted-three-client-receipt.json
  • docs/releases/evidence/shared-provider-repairs/probe-receipt.json
  • platform/contracts/deployment-control-v1.json
  • platform/control-plane/control_plane.py
  • platform/control-plane/field_notebook_shared_pool.py
  • platform/control-plane/hosted_lifecycle_service.py
  • platform/control-plane/records_v2_admin_lifecycle.py
  • platform/control-plane/records_v2_admin_projection.py
  • platform/control-plane/session_service.py
  • platform/control-plane/shared_pool.py
  • platform/control-plane/workspace_admission.py
  • platform/deployment-console/src/app.js