# Overview

This section documents the products developed by Sign.

These products are standalone offerings. They share core primitives and are often used together in sovereign and regulated deployments, but they are not defined as "subsystems of S.I.G.N.". S.I.G.N. is the sovereign system architecture for national deployments across money, identity, and capital.

If you are looking for system narrative and operating model, start with the S.I.G.N. section:

* [S.I.G.N. Overview](https://docs.sign.global/s.i.g.n./sign)
* [Reference Architecture](https://docs.sign.global/s.i.g.n./reference-architecture)
* [Security & Privacy](https://docs.sign.global/s.i.g.n./security-privacy)
* [Governance & Operations](https://docs.sign.global/s.i.g.n./governance-ops)

***

## How to use this section

Use the product pages when you need to answer:

* What does this product do and what does it not do?
* What evidence does it produce and how is it verified?
* What are the integration boundaries and operating assumptions?
* How does it typically integrate into sovereign and institutional workflows?

Deep technical documentation remains under the developer sections.

* Developer entrypoint: [For Builders](https://docs.sign.global/for-builders/getting-started)
* Quickstart: [For Hackers](https://docs.sign.global/for-hackers/getting-started)

***

## Product map

The Sign ecosystem includes three primary products:

| Product                                                                         | Scope                                              | Primary outputs                                                                    | Typical consumers                                          |
| ------------------------------------------------------------------------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| [Sign Protocol](https://docs.sign.global/products-sign-ecosystem/sign-protocol) | Evidence, attestation, and verification primitives | Schemas, attestations, verification references, audit anchors                      | Platform teams, regulated operators, auditors, integrators |
| [TokenTable](https://docs.sign.global/products-sign-ecosystem/tokentable)       | Allocation and distribution workflows              | Allocation manifests, vesting schedules, execution outcomes, distribution evidence | Program operators, treasury teams, distributors, auditors  |
| [EthSign](https://docs.sign.global/products-sign-ecosystem/ethsign)             | Agreements and signature workflows                 | Signed agreements, execution proofs, signature verification evidence               | Procurement, legal, compliance, institutional operators    |

A useful mental model is:

* **Sign Protocol** defines how actions are expressed as verifiable records and how those records are verified later.
* **TokenTable** determines who receives what, when, and under which rules, then produces deterministic distribution outputs.
* **EthSign** captures agreements and approvals as verifiable proof of execution.

***

## How products relate to S.I.G.N.

S.I.G.N. groups national deployments into three system domains. Products do not replace these systems. They are deployed to implement specific capabilities inside them where appropriate.

| National system                                                                    | What it needs                                                                                            | Products commonly used                                                                                 |
| ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| [New Money System](https://docs.sign.global/national-systems/new-money-system)     | policy-controlled payment execution, supervisory visibility, settlement references                       | Sign Protocol for evidence, plus settlement rails and operators                                        |
| [New ID System](https://docs.sign.global/national-systems/new-id-system)           | credential issuance and verification, trust registries, status and revocation, privacy-preserving proofs | Sign Protocol for anchoring accreditation and verification evidence, plus issuer and verifier services |
| [New Capital System](https://docs.sign.global/national-systems/new-capital-system) | eligibility-gated allocation, schedules, reconciliation, inspection-ready reporting                      | TokenTable for allocation and execution, Sign Protocol for evidence and audits                         |

A deployment may use Sign Protocol without TokenTable or EthSign. TokenTable and EthSign can also be deployed independently, depending on workflow requirements and operating constraints.

***

## Composition patterns

### Pattern A: Evidence-first deployments

Use when the primary requirement is standardizing verification and auditability across applications and operators.

Typical uses:

* accreditation and authorization records
* verification evidence and inspection packages
* compliance approvals and ruleset version anchoring
* registry state transitions and dispute trails

Start with:

* [Sign Protocol](https://docs.sign.global/products-sign-ecosystem/sign-protocol)
* [Writing Data](https://docs.sign.global/for-builders/index-1)
* [Querying Data](https://docs.sign.global/for-builders/index)

### Pattern B: Programmatic distribution deployments

Use when value must be distributed at scale under deterministic rules, with reconciliation and inspection-ready reporting.

Typical uses:

* benefits and subsidy distribution
* grants and incentives
* budget-constrained programs with reconciliation requirements
* vesting and unlock schedules with controlled claiming

Start with:

* [TokenTable](https://docs.sign.global/products-sign-ecosystem/tokentable)
* [New Capital System](https://docs.sign.global/national-systems/new-capital-system)
* [Sign Protocol](https://docs.sign.global/products-sign-ecosystem/sign-protocol)

### Pattern C: Agreement and approval workflows

Use when agreements, acknowledgements, and approvals must be cryptographically verifiable and linked to downstream execution evidence.

Typical uses:

* procurement agreements and operator onboarding
* compliance acknowledgements and policy acceptance
* governed approvals for high-impact actions
* institutional signature workflows tied to audit evidence

Start with:

* [EthSign](https://docs.sign.global/products-sign-ecosystem/ethsign)
* [Sign Protocol](https://docs.sign.global/products-sign-ecosystem/sign-protocol)

***

## Integration boundaries

These products are designed to integrate with existing sovereign and regulated infrastructure.

### Identity systems

S.I.G.N. deployments often use W3C Verifiable Credentials and DID-based identity primitives. Products integrate with issuer, wallet, and verifier components rather than imposing a single identity stack.

* Identity blueprint: [New ID System](https://docs.sign.global/national-systems/new-id-system)

### Money rails

The ecosystem does not assume a single settlement rail. Deployments may use private CBDC rails, regulated stablecoins on public rails, or hybrid architectures.

* Money blueprint: [New Money System](https://docs.sign.global/national-systems/new-money-system)

### Governance and operations

Institutional deployments must make control explicit: keys, upgrades, emergency actions, access policies, and evidence retention. Governance is treated as part of the system, not a post-deployment add-on.

* Operational model: [Governance & Operations](https://docs.sign.global/s.i.g.n./governance-ops)
* Controls posture: [Security & Privacy](https://docs.sign.global/s.i.g.n./security-privacy)

***

## Product selection guide

Choose based on the requirement you are trying to satisfy.

If you need to:

* standardize verifiable records, approvals, and audit trails across systems\
  Start with [Sign Protocol](https://docs.sign.global/products-sign-ecosystem/sign-protocol).
* allocate and distribute value at scale with deterministic schedules and reconciliation\
  Start with [TokenTable](https://docs.sign.global/products-sign-ecosystem/tokentable), and pair it with [Sign Protocol](https://docs.sign.global/products-sign-ecosystem/sign-protocol) for evidence.
* capture agreements and signatures in institutional workflows and prove execution later\
  Start with [EthSign](https://docs.sign.global/products-sign-ecosystem/ethsign), and pair it with [Sign Protocol](https://docs.sign.global/products-sign-ecosystem/sign-protocol) for verification and audit references.

If you are unsure, start from the system domain and work downward:

* [New Money System](https://docs.sign.global/national-systems/new-money-system)
* [New ID System](https://docs.sign.global/national-systems/new-id-system)
* [New Capital System](https://docs.sign.global/national-systems/new-capital-system)

***

## Where to go next

* Read product docs:
  * [Sign Protocol](https://docs.sign.global/products-sign-ecosystem/sign-protocol)
  * [TokenTable](https://docs.sign.global/products-sign-ecosystem/tokentable)
  * [EthSign](https://docs.sign.global/products-sign-ecosystem/ethsign)
* Build and integrate:
  * [For Builders](https://docs.sign.global/for-builders/getting-started)
  * [Supported Networks](https://docs.sign.global/for-builders/address-book)
  * [Writing Data](https://docs.sign.global/for-builders/index-1)
  * [Querying Data](https://docs.sign.global/for-builders/index)
* Clarifications:
  * [FAQ](https://docs.sign.global/faq)