Declare what should be true.

A worked file

This file is valid against the v0.1 loader. The account is the public SEP-23 test vector, not a real treasury.

# The only version this release accepts.
version = 1

# Required. mainnet, testnet or a full network passphrase.
network = "testnet"

# Exactly one endpoint is read at v0.1.
endpoints = ["https://horizon-testnet.stellar.org"]

[[account]]
# Canonical G address. M and C addresses are rejected.
id = "GA7QYNF7SOWQ3GLR2BGMZEHXAVIRZA4KVWLTJJFC7MGXUA74P7UJVSGZ"
name = "treasury"
role = "treasury"

expected_signers = [
  { key = "GA7QYNF7SOWQ3GLR2BGMZEHXAVIRZA4KVWLTJJFC7MGXUA74P7UJVSGZ", weight = 1 },
]
expected_thresholds = { low = 1, medium = 2, high = 2 }
expected_flags = { auth_required = false, auth_revocable = false, auth_immutable = false, clawback = false }
home_domain = "example.com"
expect_locked = false

# Only the owner adds accept entries, and always with a reason.
# [[accept]]
# rule = "flag-drift"
# account = "GA7QYNF7SOWQ3GLR2BGMZEHXAVIRZA4KVWLTJJFC7MGXUA74P7UJVSGZ"
# reason = "Observed change is scheduled for the November rotation."
# expires = "2027-04-27"

The file is read from --config for audit. The check command takes the same facts as flags and has no policy file.

Top-level keys

Account keys

Omitted is not false

The loader keeps every expectation as a pointer, so it can tell "not declared" apart from a declared zero, empty or false value. That distinction decides whether a rule runs at all.

An empty expected_signers = [] declares that the account should have no signers. It is not the same as leaving the key out, which declares nothing.

Accepting a known risk

An acceptance marks one finding as known without hiding it. The report keeps the finding, labels it accepted, and leaves it out of the exit-code decision.

Three rules can never be accepted, because accepting them would silence a structural failure rather than a judgement call:

The loader is strict

A policy that cannot be parsed exactly is rejected before any network call, and the run exits 2. The rules are deliberate:

• At most 1 MiB is read. A larger file is rejected, not truncated.
• Unknown keys are errors. A typo cannot silently drop an expectation.
• A duplicate account ID or duplicate rule-and-account acceptance is an error.
• Every token in the raw file is scanned for a valid S seed, including comments and keys the schema does not define. A match is rejected and the seed is never printed.
• Errors name a field path such as account[2].expected_thresholds.high, never a value from the file.
• Endpoints are checked with the same rule the HTTP client uses, so a file cannot name an endpoint the client would refuse.

A secret seed in a policy file is a key-handling incident. Remove it, rotate the key and check the file's history. The message says to rotate for that reason.

Endpoint rules

One endpoint per run. HTTPS is required, with plain HTTP allowed only for localhost and loopback addresses, which exist for local tests. The URL may not carry credentials, a query string or a fragment. Redirects are not followed, so a URL that answers with a redirect is a source failure, not a silent hop to another host.

See Mechanics for the network check and the request limits, or Guides for a runnable policy and CI wiring.

The boundary

A policy says what you expected. The report says what the chain shows. Neither is a guarantee that the account cannot be compromised. Gauge documentation

The policy file is an input to a comparison. It is not enforced on-chain, it cannot prevent a signing operation, and it has no authority if someone else controls the keys or the CI job that runs it.