TSAP Cryptographic Signing and Verification Policy

Cryptographic signing in The Sunil Abraham Project (TSAP) is used to ensure the authenticity, integrity, and long-term verifiability of selected institutional documents. It provides a mechanism to confirm that a document was explicitly approved at a specific point in time and that a particular version of the document was signed by the stated signatory.

Unlike routine communication or day-to-day edits, cryptographic signatures are reserved for materials that carry archival, constitutional, or official significance within TSAP. This ensures that verification remains meaningful, lightweight, and focused only on content where authenticity matters.

Purpose

This document defines the cryptographic signing and verification practices used within TSAP. It explains how OpenPGP is used to ensure authenticity, integrity, and long-term verifiability of selected TSAP documents.

TSAP does not sign all content. Signing is reserved for documents where authenticity and integrity are important.

Scope of Signing

TSAP applies cryptographic signing selectively to ensure that only documents requiring long-term authenticity and integrity guarantees are covered. Signed documents include foundational or constitutional materials that define the structure and identity of the project, official announcements or declarations issued on behalf of TSAP, archival snapshots intended to preserve a stable version of the project at a given point in time, datasets or structured releases distributed for public or research use, and other records considered institutionally significant.

Routine communication, including emails and messages, is not signed under this system. Similarly, minor edits or routine updates to existing content, day-to-day operational communication, and non-critical articles or drafts are excluded from cryptographic signing. This ensures that signing remains focused, meaningful, and limited to materials where verifiable authenticity is important rather than being applied to all content indiscriminately.

Cryptographic Identity Scope

TSAP maintains a cryptographic identity system for ensuring authenticity of selected documents and future institutional processes.

At present, TSAP uses OpenPGP (PGP) as its primary cryptographic signing method. This is used to create verifiable signatures for documents of constitutional, archival, or official significance.

TSAP also reserves the possibility of introducing a dedicated institutional digital signature system in the future. This may include:

At present, all signatures are issued using a personal OpenPGP key acting on behalf of TSAP. Transition to an institutional key or system, if adopted, will be documented transparently and will not invalidate previously signed records.

Signed Documents

The following TSAP documents have been cryptographically signed using the TSAP OpenPGP key:

Public Key

The public OpenPGP key currently used for TSAP document signing is publicly available.

The current signing key is a personal OpenPGP key used by Tito Dutta while acting on behalf of TSAP.

Verification

To verify a TSAP-signed document:

gpg --import tito-openpgp-public.asc
gpg --verify document.md.asc document.md

Verification confirms:

Revisions to Signed Documents

Cryptographic signatures apply to specific versions of documents. Minor editorial corrections, formatting changes, and routine maintenance updates do not normally require a new signature. However, substantial revisions to a signed document may result in a new signature being issued for the revised version.

📄 This page was created on 10 June 2026. You can view its history on GitHub, preview the fileTip: Press Alt+Shift+G, or inspect the . Last updated on 4 July 2026.