Docs

Document signing and timestamps

Document signing in Roost runs as one flow: people approve, the platform hashes, the quorum signs, and the signature and time are embedded in the file.

Flow

POST /v1/documents/sign
{ "key": "contract-signing", "document": "", "approval": "" }

-> { "signature": "...", "timestamp": "...", "receipt": "IRON3:..." }

PDF

Signatures are embedded in PDF signature fields (PAdES), so any PDF reader shows the signer, the time and whether the document changed afterwards. Other formats receive a detached signature and the receipt.

Trusted time

Roost issues timestamps itself (RFC 3161) from its own clock, which is checked against authenticated time servers under the time policy. A signature made while the clock is outside policy is refused, not stamped with a doubtful time.

Verification by a third party

Anyone with the public key verifies the document signature; the receipt and the audit record show which approvals the signature carried.