atlasberg-verify

atlasberg-verify

The binary links only the standard library, the audit domain and the read half of the adapter. It runs on a copy of the files and never takes the trail's writer lock. Verification is independent by design.

Where to get it

For the audit report: Record the version printed by -version next to the verdict. A binary built by hand prints dev.

• npm: npm install -g @atlasberg/verify, or run it without installing with npx @atlasberg/verify. The package holds a small launcher and installs the binary for your platform (Linux x64 and arm64, macOS Intel and Apple Silicon, Windows x64) as an optional dependency; nothing is downloaded at install time.
• In the appliance image, at /app/atlasberg-verify, and in the signed distribution bundle. This is the copy for air-gapped rooms.
• From source, with go build ./cmd/atlasberg-verify, for whoever wants to compile the verifier themselves.

npm install -g @atlasberg/verify
atlasberg-verify -version
# atlasberg-verify 0.2.1

Usage

• -from and -from-hash: an external checkpoint. A checkpoint read from the very file under analysis is refused.
• -anchor: starts at the most recent signed anchor.
• -quiet: suppresses only the summary. It never reduces what is verified.
• -version: prints the tool version and exits.

atlasberg-verify -dir /app/data
atlasberg-verify -events trilha.log -anchors ancoras.log -key chave.pub
atlasberg-verify -export relatorio.txt -key chave.pub
atlasberg-verify -license arquivo.cert [-root <chave b64url>]
atlasberg-verify -usage relatorio.json -key chave.pub

Exit codes

• Code: 0 | Meaning: Intact and fully witnessed.
• Code: 1 | Meaning: Divergence (includes an unreadable line in the middle of the file).
• Code: 2 | Meaning: The tool could not run.
• Code: 3 | Meaning: Intact, but with a tail no anchor witnesses.

The stdout contract

The verdicts are ASCII without accents, exactly as the code prints them. This is a contract for automation.

• The verification scope is always printed, even with -quiet.
• A warning is printed when the public key came from the deployment's own secrets file instead of the auditor.

INTEGRO ate a seq %d (head %s), com testemunha assinada ate o fim
DIVERGENCIA na seq %d: %s
INTEGRO MAS SEM TESTEMUNHA ate a seq %d (head %s)
INTEGRO MAS COM CAUDA INCOMPLETA ate a seq %d (head %s)
trilha vazia: nenhum evento para verificar
ANCORA INVALIDA %s (%d..%d): %v
SEQUENCIA DE ANCORAS QUEBRADA: %v
CAUDA INCOMPLETA: ...
EXPORT VALIDO: tipo %s, emitido em %s, chave %s
EXPORT INVALIDO: %v
LICENCA VALIDA (assinatura confere com a %s)
LICENCA INVALIDA: %v
RELATORIO DE USO VALIDO (assinado pela chave do deployment %s)
RELATORIO DE USO INVALIDO: %v

What it verifies

• The trail: chain integrity and signed anchors (-dir or -events plus -anchors).
• Signed exports (-export): compliance reports and trail exports.
• Licenses (-license): the signature against the embedded root keys, or a root passed with -root.
• Usage reports (-usage): signed with the deployment key and chained by the previous report hash.

About Atlasberg Platform

Atlasberg Platform is the control layer between a company and every AI model: each request is authenticated with a virtual key, filtered by policy and DLP, routed to the right provider and written to a hash-chained audit trail. It exposes an OpenAI-compatible API, so applications only swap the base URL.

The same artifact runs in Atlasberg Cloud, in your VPC, on-premises or fully air-gapped, and is priced by capacity and modules, never per seat.

This page is part of the official documentation. To talk to the engineering team, write to [email protected] or use https://atlasberg.com/contato. Answers come within one business day.