TERA Signature v0.7.6.2 Checking service
Document assurance workspace
TERATrustworthiness · Efficiency · Reliability · Accountability
Capable Without AI, Stronger With It.
TeraSystemsAI
TrustPDF
TERA SIGNATURE

Sign with confidence.
Verify with evidence.

Upload a PDF or Word document, invite partners, track every signing event, and preserve verifiable evidence under TERA.

Human intent remains the gate. AI is optional and cannot apply a signature.

PDF + WordUpload what you already use Preview firstReview before anyone signs Human controlledNo automatic signature Evidence preservedActions stay accountable

Accepted documents: PDF · Word (.docx)

Trustworthiness
Efficiency
Reliability
Accountability
TERAAssurance
WORKFLOW

Partner signatures

EVIDENCE

Timeline

VERIFICATION

Verification status

T
TERA AssuranceTrustworthiness, Efficiency, Reliability, and Accountability guide every signing workflow.
WORKFLOW

Signature requests

See who has received, opened, and signed each document. Time is visible as part of the evidence.

PREPARE

Create a signature request

Prepare the document, define each participant, choose the signing order, and set a signing deadline that matches the agreement or workflow.

1

Document

TERA records SHA-256 fingerprints for the source document and controlled signing copy before any invitation is created.

Using Word?TERA first tries to prepare an Office-rendered PDF signing copy. If Office rendering is unavailable, your Word document stays accepted and you can attach a PDF exported from that same Word file. Your original Word file remains unchanged.
2

Participants

Every participant receives an explicit role and evidence trail.

Each partner can receive the signing experience in English or French. Secure access code verification is the default browser workflow.

3

Timing and order

The request owner controls the signing deadline. Verification codes expire separately after 10 minutes and do not shorten the signing window.

ASSURANCE PATH

TERA Evidence Assurance

TERA records document integrity, signer intent, review decisions, timing, signature evidence, and chained workflow events. Connected mode adds secure partner access, shared workflow state, and server-backed evidence. Certificate-backed PDF signing remains an optional higher-assurance capability when configured.

Human controlledSHA-256Explicit consentPortable evidence
DOCUMENTS

Document evidence

Every request begins with a document fingerprint. TERA keeps the hash visible so integrity can be checked later.

PARTNERS

People in your workflows

Roles, request counts, and signature timing remain visible across your local workspace.

VERIFY

Verify a document

Check a document against TERA evidence without relying on AI. The verification result reports each evidence layer separately.

Verification inputs

No verification run yet.Choose a document and evidence record to compare their integrity data.
PROFILE & SIGNING IDENTITY

Your TERA Signature profile.

Keep your signing identity, professional context, language, and assurance preferences in one governed workspace. Your core profile remains local to this browser unless a connected workflow explicitly records it.

PERSONAL PROFILE

How you appear in TERA Signature

These details support request ownership and human-readable signing evidence. They do not independently prove civil identity.

Profile data is saved in this browser workspace. TERA records identity details in a connected workflow only when you take an accountable action.
SIGNING ACCESS

Secure partner access by default

Partners receive controlled access to the exact document workflow without needing to operate cryptography.

RecommendedNo certificate knowledge required
  • No account required for invited partners
  • Private signing link
  • One-time verification code
  • Explicit review and consent
  • Review signed document before submission
  • Time-limited signing access
Human controlledYour signing identity is used only when you explicitly review, sign, release, or confirm an accountable action.
Connected deliveryWhen the connected service is available, TERA can create secure partner sessions, shared workflow state, revocation, deadlines, and server-backed evidence.
Higher assurance options

Certificate-backed signing

Use an organization signing certificate only when a workflow requires it.

FormatPKCS#12 (.pfx or .p12)Browser capabilityFile readiness onlyCryptographic PDF signingRequires connected signing service
SECURITY & PRIVACY

Know what the profile establishes

TERA separates usable signing identity from stronger identity-proofing claims.

Profile scopeYour profile is browser-local. Name, email, organization, and role provide workflow context but are not by themselves government-identity verification.
Verification-code scopeAn emailed one-time code confirms access to a signing session. It does not by itself prove civil identity or professional authority.
Security & Data HandlingPrivacy PolicyTerms of Use
TERA ASSURANCE

Human authority remains explicit

Profile context supports the workflow; evidence and human confirmation determine what TERA can claim.

T
TrustworthinessIdentity and evidence claims remain bounded by what the system can establish.
E
EfficiencyCommon profile details are reused without adding friction to each signing request.
R
ReliabilityStable profile context supports consistent request ownership and signing evidence.
A
AccountabilityHuman review, consent, timestamps, roles, and signatures remain the accountable actions.
ACCOUNTABILITY

Activity and evidence timeline

Every recorded event carries a time and integrity link to the prior event in its request.

SETTINGS

Local-first by default

TERA Signature works without AI. When deployed with the TERA connected service, secure invitations, expiring codes, shared signing state, revocation, and server-sealed evidence are enabled.

CORE

Browser workspace

Application entryindex.html
Local persistenceBrowser storage
Document storageIndexedDB
IntegrityWeb Crypto SHA-256
AI requirementNone
CONNECTED SERVICES

Deployment service

Service statusChecking deployment service...
Secure invitationsAutomatic email delivery with short-lived access codes when connected.
Shared stateServer-enforced deadlines, sequential order, revocation, and partner status.
Owner notificationsCritical events can notify the request owner when a remote participant signs, delivery fails, the workflow completes, or the Evidence Seal is created.
TERA Evidence SealCompleted workflows can receive a server-authenticated evidence seal after final owner review.
Certificate-backed PDF signingHigher-assurance path remains separate unless explicitly configured.
AI assistanceOff. Core signing and verification do not require AI.
PORTABILITY

Import and export

Move evidence between people without a central server.

TERA

Assurance principles

TrustworthinessEvidence says only what the system can establish.
EfficiencySimple signing flow with portable partner exchange.
ReliabilityStable hashes, event chains, and explicit states.
AccountabilityRoles, consent, timestamps, and actions remain visible.
HUMAN SIGNATURE

Confirm your signature

Draw your signatureYour handwritten mark is cropped to the actual ink, embedded in the signed PDF, and fingerprinted with SHA-256 when used. The printed participant name remains visible for readability.
No handwritten mark detected yet.Draw in the canvas to use a handwritten signature. If ink is present, TERA will not silently replace it with a typed signature.
REVIEW & RELEASE

Review exactly what partners will receive
RELEASE ERROR

Review & Release could not complete

Connected service response

The request remains unchanged. This message stays visible until you close it.
SECURE ACCESS

Partner access code generated
FINAL REVIEW

Review the completed PDF before sealing.

TERA assembles the accepted signatures onto the controlled signing document. Review the exact completed PDF before creating the TERA Evidence Seal.
SAME-DEVICE SIGNING

Review the signed document before confirming
FINAL HUMAN CHECK

Review your signed document