# Countersign

> An agreement-aware payment controller for crypto teams. Connect approved terms, acceptance, invoice checks, bounded Safe authority, and destination settlement.

## Availability and authority

The public demo is synthetic and cannot move funds. Production persistence, workers, deployed contracts, payment integrations, and funded protection require separate activation. Consult release status before making live capability claims. Model output is untrusted input, never payment authorization. Application membership is not Safe ownership. Never retry an uncertain transfer under a new identity.

## Reading this documentation

- [Release status](https://www.usecountersign.xyz/docs/raw/release-status): Current documented availability and activation gates.
- [Agent guidance](https://www.usecountersign.xyz/docs/raw/agents): Retrieval, examples, and authority boundaries.
- [Complete documentation](https://www.usecountersign.xyz/llms-full.txt): All public handbook pages as Markdown.

## Start here

- [Review Countersign](https://www.usecountersign.xyz/docs/raw/reviewer-guide): A reproducible product walkthrough, source map and exact evidence boundaries.
- [Getting started](https://www.usecountersign.xyz/docs/raw/getting-started): Understand Countersign, explore the demo, and choose an adoption path.
- [Release status](https://www.usecountersign.xyz/docs/raw/release-status): What is implemented, what is public, and what still requires activation.
- [Concepts & glossary](https://www.usecountersign.xyz/docs/raw/glossary): The language of obligations, decisions, authority, and settlement.

## Product guides

- [Vendors & destinations](https://www.usecountersign.xyz/docs/raw/vendors): Vendor identity, approved destinations, and changes that need a fresh review.
- [Agreements & acceptance](https://www.usecountersign.xyz/docs/raw/agreements): Versioned obligations, approved terms, and authorized acceptance.
- [Invoices & exceptions](https://www.usecountersign.xyz/docs/raw/invoices): Document intake, duplicate checks, evidence, and vendor corrections.
- [Deterministic verification](https://www.usecountersign.xyz/docs/raw/verification): How invoices become eligible, held, or in need of clarification.
- [Cash & payment planning](https://www.usecountersign.xyz/docs/raw/planning): Confirmed cash, commitments, and shared-Safe scheduling.
- [Payments & reconciliation](https://www.usecountersign.xyz/docs/raw/payments): Stable payment identities, uncertain outcomes, and destination settlement.
- [Standing automation](https://www.usecountersign.xyz/docs/raw/automation): Observation history, bounded automation, durable work, and notifications.
- [Accounting & exports](https://www.usecountersign.xyz/docs/raw/accounting): The subledger, CSV exports, and evidence for bookkeeping.
- [Payment operations desk](https://www.usecountersign.xyz/docs/raw/operations-desk): Due dates, exception ownership, reminder preferences and accounting period packs.
- [Receipts & verifier](https://www.usecountersign.xyz/docs/raw/receipts): Portable receipts, redaction, integrity verification, and offline limits.

## Trust & control

- [Security & permissions](https://www.usecountersign.xyz/docs/raw/security): Observe, Prepare, Delegate, wallet identity, and exact constrained authority.
- [Reserved protection](https://www.usecountersign.xyz/docs/raw/protection): Capped, fully reserved protection and its separate activation requirements.
- [Recovery playbook](https://www.usecountersign.xyz/docs/raw/recovery): Independent pause, revocation, uncertain operations, and safe recovery.
- [Security review notes](https://www.usecountersign.xyz/docs/raw/security-review): Local review scope, findings, and independent review requirements.

## Build & operate

- [Integrations](https://www.usecountersign.xyz/docs/raw/integrations): Circle, Safe, CCTP, model extraction, and optional notices.
- [API reference](https://www.usecountersign.xyz/docs/raw/api): Authenticated endpoints, request examples, and error handling.
- [For AI agents](https://www.usecountersign.xyz/docs/raw/agents): Machine-readable docs, retrieval guidance, and agent authority boundaries.
- [Deploy & operate](https://www.usecountersign.xyz/docs/raw/deployment): Persistence, encryption, migration, workers, and operational readiness.
- [Activate a real workspace](https://www.usecountersign.xyz/docs/raw/activation): Redacted configuration diagnostics, read-only probes and exact external activation steps.
- [Domain reference](https://www.usecountersign.xyz/docs/raw/domain): Core types, exact amounts, verification outcomes, and state machines.
- [Contract controls](https://www.usecountersign.xyz/docs/raw/contracts): Safe module constraints, route restrictions, and protection reserves.
- [Cross-chain relay](https://www.usecountersign.xyz/docs/raw/relay): Durable destination submission and independently verified finality.
- [Operations reference](https://www.usecountersign.xyz/docs/raw/operations): Observation, scoped overrides, and accounting operations.
- [Evidence & evaluation](https://www.usecountersign.xyz/docs/raw/evaluation): Compare workflows without mixing synthetic and independent evidence.

## Field notes

- [Why Countersign?](https://www.usecountersign.xyz/docs/raw/why-countersign): When agreement-aware payment review is useful—and when it is not.
- [Start with read-only](https://www.usecountersign.xyz/docs/raw/start-read-only): A practical route from visibility to justified, bounded automation.
- [Beyond the invoice](https://www.usecountersign.xyz/docs/raw/agreement-aware-payments): Why terms, delivery, acceptance, and history belong in one decision.
- [Settlement is not a hash](https://www.usecountersign.xyz/docs/raw/settlement-is-not-a-hash): Why a submitted transfer needs independent destination confirmation.