> ## Documentation Index
> Fetch the complete documentation index at: https://zenofirm.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Plan, review, apply, reverse

> The governed loop every Zenofirm write follows.

Every write follows the same route whether it started in the interface, in the
Operator, or through an external MCP client.

## Plan

Zenofirm resolves the proposed work against the connected ledger, checks for
duplicates and closed periods, applies the client's confirmed rules, and
renders the result as a plan. Planning changes nothing in the ledger.

## Review

A reviewer sees each entry, its source, coding, warnings, and the result of
preflight checks. Approval and rejection are explicit verdicts recorded
against the exact digest of the plan that was reviewed.

## Apply

Only approved entries are sent to the ledger adapter. If the ledger changed
after planning, Zenofirm revalidates and stops rather than silently applying a
stale plan.

## Reverse

Each run keeps the provider identifiers and prior state needed to perform the
ledger's native reversal operation. Reversal is part of the operating model,
not a premium feature.

<Note>
  The safety path is the same on every plan: reads and review remain available,
  and no commercial entitlement disables access to reversal.
</Note>