Sixteen checks. Seven shipped.

A requested account returned 404. The endpoint answered, so this is a statement about the account, not about the network. The account may never have been created, or it may have been merged into another account. The run continues and reports the other accounts.

Evidence

endpoint URL returned not found

Acceptable

No. An acceptance cannot hide a missing account.

Exit effect

HIGH fails the default --fail-on high and produces exit 1.

The endpoint's network passphrase differs from the network the run requested. No account is fetched from that endpoint at all, because an account ID can exist on more than one network and the report would describe the wrong chain. Each requested account is listed as skipped with this finding.

Evidence

expected Test SDF Network ; September 2015, endpoint reports Public Global Stellar Network ; September 2015

Acceptable

No.

Exit effect

HIGH fails the default threshold and produces exit 1. The run did not read an account, but it did complete and name the disagreement.

A flag the policy declares disagrees with the chain. Only declared flags are compared, so an omitted flag can never drift. The comparison runs in a fixed order: auth_required, auth_revocable, auth_immutable, clawback. The evidence lists each disagreement.

Example

auth_required declared false, observed true

Acceptable

Yes, with a reason and an optional expiry. The owner adds accept entries.

Exit effect

WARN is below the default --fail-on high. It produces exit 1 only under --fail-on warn.

Clawback is enabled and the policy says nothing about clawback. A declared value, true or false, suppresses this rule: declared true is a declaration, and declared false that disagrees with the chain is flag-drift instead.

Evidence

clawback observed true, and no clawback expectation is declared

Acceptable

Yes, with a reason and an optional expiry.

Exit effect

WARN. Exit 1 only under --fail-on warn.

The policy declares a home_domain and the account publishes none on chain. The trigger is the declaration, not the role: the role table that would decide which accounts are expected to publish one is task 3.4, and rules may not hardcode a role set. A check run declares nothing, so it cannot raise this rule.

Evidence

home_domain declared "example.org", observed none

Acceptable

Yes, with a reason and an optional expiry.

Exit effect

WARN. Exit 1 only under --fail-on warn.

The account publishes a home domain and its stellar.toml could not be fetched or parsed under the guard. It fires the same way when a domain was observed and never fetched at all: an identity Gauge could not verify is a warning, never a pass. The evidence names the step that failed, so a domain that resolves to a blocked address is distinguishable from one that serves an oversized or unreadable document. Nothing from the document is quoted; the detail phrase is one this repository wrote. A fetcher that cannot be built at all is a run that did not complete: exit 3, no report.

Evidence

step guard; detail the host name resolves to a private address, which Gauge will not dial; status 0

Acceptable

Yes, with a reason and an optional expiry.

Exit effect

WARN. Exit 1 only under --fail-on warn.

A readable stellar.toml does not name this account in ACCOUNTS. The rule only speaks about a document it could read, so an unreachable domain raises one finding rather than two. Entries that are not account addresses are counted and never echoed, which keeps a malformed or hostile list out of the report. The document's NETWORK_PASSPHRASE is carried in the result but compared by no rule today.

Evidence

home domain example.org lists 2 accounts; this account is not among them

Acceptable

Yes, with a reason and an optional expiry.

Exit effect

WARN. Exit 1 only under --fail-on warn.