Makion Start a free trial
Autonomous mode

A spec in, a result out

The orchestrator breaks a spec into steps and drives it to a result. Read-only, with a two-person gate.

Hand the orchestrator a task or a spec. It decomposes it and drives the agents step by step to a result. During the run the agent only reads SAP: no writes to the system. Every proposed change goes into a ship queue, with the object, the type (create / modify / activate), the requirement it closes, a rationale and the payload itself. You watch live progress and can hit Stop at any time. Because the run is read-only, your SAP is never left half-changed.

The gate

Two people before a write

The orchestrator proposes a change in read-only mode, a person approves the queue item, then separately confirms the apply, and only then does a write to SAP happen.

Two-person gate The orchestrator proposes a change in read-only mode, a person approves the queue item, then separately confirms the apply, and only then does a write to SAP happen. 1 · PROPOSE Orchestrator read-only, in SAP writes nothing 2 · APPROVE Step 1 approves the queue item doesn't touch SAP 3 · APPLY Step 2 a separate confirmation “this will write to live SAP” 4 · WRITE Your SAP lock → set source → syntax check → activate stops on any error The orchestrator never applies anything itself · break-glass: MAKION_AUTONOMOUS=0 kills autonomous mode for all projects

No write without a human in autonomous mode. A two-step human gate: a person approves, then separately confirms the apply.

Ship queue

What waits in the queue

Every proposed change goes into a ship queue with the object, the type (create / modify / activate), the requirement it closes, a rationale and the payload itself. Irreversible actions are queued for human approval. The queue can also be cleared from Telegram: the human gate in your pocket, nothing reaches SAP without it. Makion in Telegram →

Chat versus autonomous

Honestly: in an interactive chat a write-permission role (Development, Unit tests, ATC) makes the change during the dialogue you're running. There's no separate “Apply” button here, you steer step by step. The hard guarantees in chat: read-only roles can't write, and deletion is always disabled. If you need a hard button-gate on every write, use autonomous mode with the ship queue.

Specs feed the orchestrator directly: an ordered, versioned specification from the Specification role can be handed straight to it. How specs work →

Get started

Put Makion inside your SAP

Your SAP, your standards, your terms.

Start a free trial Contact us

Several developers or a client rollout? Teams & enterprise