title	description	section	sectionOrder	order
signature.digital platform	Prepare PDFs, create scoped signing invitations, collect simple electronic signatures, and export inspectable application evidence.	Overview	10	1

signature.digital platform

signature.digital is an open-source PDF signing workflow. The v0.1.1 application lets one configured workspace owner upload a PDF, place signer fields, create one-time signing links, collect explicit consent and field values, and produce a flattened completed PDF with a JSON evidence export.

Issue Reporting and Security

For reporting bugs, issues, or security vulnerabilities, please visit community.foss.global/. This is the central community hub for all issue reporting. Developers who sign and comply with our contribution agreement and go through identification can also get a code.foss.global/ account to submit Pull Requests directly.

Alpha boundary

Alpha v0.1.1. The current application is a single-instance, single-workspace deployment. The owner authenticates with a configured bootstrap secret. It does not provide general user accounts, team membership, or an external identity-provider integration.

Sending a document creates invitation links and returns them to the owner. The application does not deliver those links by email. Delivery is an external operator or integration responsibility.

The evidence is factual application evidence for a simple electronic signature workflow. It is not a qualified or advanced electronic signature, an independent trusted timestamp, an identity-provider assertion, or a legal conclusion. Legal effect depends on the process and jurisdiction in which the workflow is used.

Implemented workflow

Step	Current behavior
Authenticate	Exchange the deployment bootstrap secret for an expiring owner session
Prepare	Upload one validated PDF, define signer/copy metadata, and place signature, initials, date, text, or checkbox fields for signers
Send	Freeze a revision and create one-time invitation links for signers; the owner handles external delivery
Sign	Exchange a link for a scoped signer session, accept the declared consent text, and complete assigned fields
Complete	Flatten field values into a PDF, append a signature summary page, and store the completed artifact
Verify	Export artifact and chain-head summaries as JSON evidence; retrieve and verify the full event list separately through the owner audit API

Recipient order is currently presentation metadata, not an enforced signing sequence. Copy recipients receive no invitation or built-in delivery and do not block document completion.

Package boundaries

Package	Documented version	Responsibility
`@signature.digital/app`	0.1.1	Current owner and signer workflow, server, UI, MongoDB state, and S3 artifacts
`@signature.digital/interfaces`	1.3.0	Broader portable-contract model and factory defaults
`@signature.digital/catalog`	1.9.0	Reusable signing and workspace web components
`@signature.digital/tools`	1.4.1	Convenience re-export of the portable interfaces

The portable-contract package models substantially more than the v0.1.1 application currently executes. Its legal-proof, collaboration, lifecycle, identity-verification, and document-bundle structures are shared data contracts, not claims that any corresponding provider or workflow is live in the application. The implemented TypedRequest DTOs are app-local and are not presently published as a stable external SDK.

Start here

License and Legal Information

This repository contains open-source code licensed under the MIT License. A copy of the license can be found in the repository license file.

Please note: The MIT License does not grant permission to use the trade names, trademarks, service marks, or product names of the project, except as required for reasonable and customary use in describing the origin of the work and reproducing the content of the NOTICE file.

Trademarks

This project is owned and maintained by Task Venture Capital GmbH. The names and logos associated with Task Venture Capital GmbH and any related products or services are trademarks of Task Venture Capital GmbH or third parties, and are not included within the scope of the MIT license granted herein.

Use of these trademarks must comply with Task Venture Capital GmbH's Trademark Guidelines or the guidelines of the respective third-party owners, and any usage must be approved in writing. Third-party trademarks used herein are the property of their respective owners and used only in a descriptive manner, e.g. for an implementation of an API or similar.

readme.md