ATOMIK
FORGE / CONTROL PLANE
PHASE 1OBSERVE + PLAN
READ-ONLY CONTROL

Forge can observe and plan. Deployment authority is absent.

NO DEPLOY AUTHORITY
IDENTITY GATE

Authenticate as a Forge operator

A verified Supabase session and an assigned Forge role are required. Authentication never grants cloud deployment permissions.

01 / ACTIVE PRODUCTION

Release planning workspace

UNAVAILABLE
PROD

Production snapshot

Revision — NOT OBSERVED
Source SHA
—
Image digest
—
Deployed at
—
Service
—
Release planning is blocked until Production provenance is verified.
02

Available changesets

—

Real changes normalized from the source provider relative to active Production.

∅ No verified changesets loaded

Sign in with an assigned role to read source metadata.

03

Release plan

BLOCKED
ACTIVE PROD — VERIFIED BASE
+
SELECTED 0 CHANGESETS
→
CANDIDATE PLAN NOT BUILT NO ARTIFACT ID
DEPENDENCY UNKNOWN

Unknown dependency evidence blocks planning.

Creates a persisted plan only. It cannot build or deploy.

04

Future lifecycle

PHASE 1 LOCKED
  1. 01
    PLANAVAILABLE IN PHASE 1
  2. 02
    BUILD CANDIDATENOT AVAILABLE IN PHASE 1
  3. 03
    DEPLOY TO STAGINGNOT AVAILABLE IN PHASE 1
  4. 04
    PROMOTE TO PRODUCTIONNOT AVAILABLE IN PHASE 1
  5. 05
    ROLLBACKNOT AVAILABLE IN PHASE 1
RI-001Chronology is not authority

Merge order and PR numbers cannot determine release order.

RI-002Production is the basis

The plan starts from the verified active Production state.

RM-001Selective release preserved

Unselected mainline changes remain explicitly excluded.

AUTHApplication role ≠ cloud IAM

Even Forge Admin has no deployment permission.