# Sovereign Deployment and Developer Platform

Canonical URL: https://babadook.tech/modules/maxacor-sovereign-platform
Entity: modules
Content hash: 917e67b074ce69ac6625c3bdbc1243f4548170e5a833b962629b5ec7f1e24709

Run the same accountable physical-operations contract from air-gapped facilities to multi-site estates.

A regulated plant runs locally through a control-plane outage, imports a signed update offline and exposes the same typed operation through GUI, CLI and SDK. CRTL owns runtime admission and Haephestus owns artifact provenance; MAXACOR owns how its physical capabilities behave in each profile.

## When it matters

A regulated plant runs locally through a control-plane outage, imports a signed update offline and exposes the same typed operation through GUI, CLI and SDK.

### data Viz

### data View

section: module-scene

### Section 1

col Title: Deployment Profiles

col Cont: An air-gapped site starts, operates, updates and exports evidence without internet reachability. Deployment limits are visible before a capability is used.

### Section 2

col Title: Security and Governance

col Cont: A supplier reviewer can inspect one approved evidence package without seeing another tenant or gaining control access. Collaboration does not weaken operational boundaries.

### Section 3

col Title: API, SDK and Event Parity

col Cont: An engineer tests an operation in the CLI and receives the same denial code and evidence through the SDK and GUI. Automation behaves consistently across every supported surface.

## Sovereign Deployment and Developer Platform

data View: maxacor-sovereign-platform:submodules

### Deployment Profiles

desc: Declare what remains available, local and exportable in each deployment class.

link: /sub-modules/maxacor-deployment-profiles

### Security and Governance

desc: Apply tenant, site, identity, policy, override and evidence controls to physical operations.

link: /sub-modules/maxacor-security-governance

### API, SDK and Event Parity

desc: Carry the same operation and failure meaning through protobuf, REST, SDK, CLI and streams.

link: /sub-modules/maxacor-api-sdk-events

## Deployment Profiles

action: Declare what remains available, local and exportable in each deployment class.

mechanism: An air-gapped site starts, operates, updates and exports evidence without internet reachability.

workflow role: An air-gapped site starts, operates, updates and exports evidence without internet reachability.

operational outcome: Deployment limits are visible before a capability is used.

maturity: specified

evidence: MAXACOR Part 12, §§4–15; Part13.

### Section 1

Operations team

### Section 2

Engineering team

### Section 1

Qualified physical state

### Section 2

Current work context

### Section 1

Evidence-bearing operational disposition

### Section 1

A healthy process is not proof of a valid profile.

## Security and Governance

action: Apply tenant, site, identity, policy, override and evidence controls to physical operations.

mechanism: A supplier reviewer can inspect one approved evidence package without seeing another tenant or gaining control access.

workflow role: A supplier reviewer can inspect one approved evidence package without seeing another tenant or gaining control access.

operational outcome: Collaboration does not weaken operational boundaries.

maturity: specified

evidence: MAXACOR Part 12, §§4–15; Part13.

### Section 1

Operations team

### Section 2

Engineering team

### Section 1

Qualified physical state

### Section 2

Current work context

### Section 1

Evidence-bearing operational disposition

### Section 1

Authorization remains with ARGUS and governing owners.

## API, SDK and Event Parity

action: Carry the same operation and failure meaning through protobuf, REST, SDK, CLI and streams.

mechanism: An engineer tests an operation in the CLI and receives the same denial code and evidence through the SDK and GUI.

workflow role: An engineer tests an operation in the CLI and receives the same denial code and evidence through the SDK and GUI.

operational outcome: Automation behaves consistently across every supported surface.

maturity: specified

evidence: MAXACOR Part 12, §§4–15; Part13.

### Section 1

Operations team

### Section 2

Engineering team

### Section 1

Qualified physical state

### Section 2

Current work context

### Section 1

Evidence-bearing operational disposition

### Section 1

Public surfaces cannot invent a second lifecycle.

## Relationships

### products

- MAXACOR — https://babadook.tech/products/maxacor

### sub modules

- Deployment Profiles — https://babadook.tech/sub-modules/maxacor-deployment-profiles
- Security and Governance — https://babadook.tech/sub-modules/maxacor-security-governance
- API, SDK and Event Parity — https://babadook.tech/sub-modules/maxacor-api-sdk-events