Resolved Execution Target
Before Prepare, resolve the source system, document identity, immutable revision marker such as version/eTag, execution content hash and resolution time. A changed source revision requires a new target.
SIGNUMERAVERIFIED SIGNINGSecond-generation architecture
Before execution, SignumEra resolves an Execution Target from the source system, document identity, immutable revision marker and content hash, then freezes the target and ceremony rules into a manifest. The envelope becomes a transport detail—not the security boundary.
Key controls
A defensible execution begins before the first signature: identify the authoritative source revision, hash it, freeze the participant and ceremony rules, and reject material drift.
Before Prepare, resolve the source system, document identity, immutable revision marker such as version/eTag, execution content hash and resolution time. A changed source revision requires a new target.
Freeze the Execution Target, participants and roles, order, ceremony mode, witness rules and finalizer. Material changes require a new revision and manifest.
Preparation freezes the intended agreement revision before signatures are accepted.
Prepared/downloaded bytes are verified against the execution hash, the viewer exposes only the frozen target, and finalized output remains bound to the ceremony integrity chain.
Order, witnesses, verification requirements, evidence requirements and finalization conditions are enforced server-side.
Presence changes and material actions are recorded as append-only server events with timestamps and reason codes where applicable.
Finalized documents and configured evidence return to the explicitly selected system of record. Identity, Teams or Zoom context does not create an additional storage destination.
Minimize unnecessary long-term document custody and keep the public signing layer focused on controlled execution.
Built in Gibraltar
Minimize unnecessary long-term document custody and keep the public signing layer focused on controlled execution. Finalized documents and configured evidence return to the explicitly selected system of record. Identity, Teams or Zoom context does not create an additional storage destination.

Low-friction adoption