Observed and asserted
How every field in a record is labeled as observed by Esign Comply, asserted by you or supplied by you later, and what Esign Comply will say about each.
Every fact Esign Comply holds carries a label that says where it came from. The labels are the same in the API, the dashboard, the evidence report, the certificate and the verification page. They are never merged, because the value of an independent record depends on a reader being able to tell what the record keeper saw from what it was told.
The three labels
| Label | Meaning | Example |
|---|---|---|
observed |
Seen by Esign Comply directly from the signer's device, or generated by Esign Comply | The server receipt time of each event; the checkbox's initial state as the SDK measured it; the verified email address; the record hash |
asserted |
Supplied by you. Not verified by Esign Comply. | The signer's name, external ID and state; context.facts; metadata; every field of a server_only or deferred record |
customer_supplied |
Supplied by you after or outside the ceremony as a supplement. Received and sealed by Esign Comply, not verified. | A notice.sent report with the reminder email attached |
Each event in a record has a tag of observed or asserted. Supplements carry provenance: "customer_supplied".
Observed does not mean true in every sense. It means Esign Comply received it on the direct channel and recorded it at the server time shown. A customer that scripts a fake browser can still send events. L2 verification and the signer receipt exist to make that harder to do unnoticed. See Evidence.
Which fields are which
| Category | Fields | Label |
|---|---|---|
| Parties | Your organization's legal name; the registered domain, verified at seal time | Asserted at signup; observed |
| Signer identity | signer.external_id, name, email, phone, class, country, region |
Asserted |
| Signer verification | signer.verified_email, signer.verified_phone, method, time, attempts; passkey credential ID |
Observed |
| What the signer entered | signer.typed_name, drawn strokes where captured |
Observed |
| Content | Document title, version label, language, content hash, render hash, render-match result | Observed |
| Presentation | Mode, link metrics, link opened, viewport, notice snapshot | Observed where captured live; a registered artifact otherwise |
| Disclosures and consent | Disclosure version and hash, access demonstration, consent act, control states | Observed |
| Intent | Control type, label text, button text, trusted-event flag, initial control state | Observed |
| Time | Esign Comply server time for every event; the external timestamp | Observed |
| Time | Client clock time reported by the browser (client_time) |
Reported by the browser, not verified |
| Network and device | IP address, user agent, accept-language, origin, page URL (omitted under EU minimal capture) | Observed |
| Jurisdictions | Packs applied, versions, reasons, rules fired | Observed |
| Jurisdictions | signer.region, governing_law, the facts rules read |
Asserted |
| Context | context.url, context.purpose, context.facts, context.notes, context.extra, metadata |
Asserted |
| Integrity | Record hash, seal, key ID, timestamp token, ledger sequence, previous-entry hash, checkpoint, inclusion proof | Observed |
| Conformance | Rule set version and result per rule | Advisory. Stored beside the record, outside the sealed hash. The underlying measurements are sealed inside events[]. |
| Later facts | Dispute, consent withdrawal, paper-copy request in the signer view, legal hold | Observed (annotations) |
| Later material | Supplements | Customer-supplied |
Two details are easy to get wrong:
- Times.
signed_atis the server receipt time of the final event. It is not an independently verified act time and it is not the timestamp authority's time. The external timestamp bounds when the record hash existed, not when the person acted. - Location. Esign Comply does not choose law from an IP address. The signer's country and state are what you sent.
How capture mode changes the labels
capture_mode |
Ceremony events |
|---|---|
direct |
Observed, except statements such as signer.age_attested and billing.confirm, which are asserted |
server_only |
Asserted: your server reported them |
deferred |
Asserted: you reported the act after it occurred |
imported (Planned) |
Asserted |
Planned.
importedrecords come fromPOST /v1/records/import, which is not part of the current API.
For deferred and imported records Esign Comply does not say the record was made at or near the time of the act. It says when it received your report. See The ceremony.
Three parts, never merged
Evidence reports, evidence packages and certificates are laid out in three parts:
| Part | Heading | Contains |
|---|---|---|
| A | Esign Comply's record | Everything Esign Comply observed or checked: events, times, hashes, verification, delivery, integrity, rules applied |
| B | Asserted by {customer} at signing | Signer fields, context.facts, context.notes, context.extra and metadata |
| C | Supplied by {customer} after signing | A list of supplements: type, the time you say the thing happened, the time Esign Comply received it, and the hash |
Part C sits under the sentence "Esign Comply received this material at the times shown and did not verify its contents." It is a list only: the content is in the evidence package under customer_supplied/. The report generated at sealing has an empty Part C. A report downloaded later lists what has arrived since. Parts A and B do not change.
The same separation holds in the API. The record object returns supplements[] and certificates[] outside the sealed hash, and each supplement has its own seal and ledger entry. See Supplements.
Rule classes
Jurisdiction rules mix three different things: what Esign Comply records, what the law requires you to do, and what Esign Comply only suggests. Every rule is split into parts, and each part has exactly one class. The class decides who does the work, who holds the record, and what Esign Comply may say about it later.
| Class | Label in the catalogue | Who acts | What Esign Comply holds | What a report or certificate may say |
|---|---|---|---|---|
| Esign Comply record | service |
Esign Comply | Its own record, tagged observed | "Esign Comply recorded this." |
| Record condition | record_condition with level block or warn |
Esign Comply checks its own record. Your interface must satisfy the check. | The check and its result, inside its own record | "Rule checked: met" or "not met" |
| Customer obligation | obligation |
You | Nothing, unless you send a report | Nothing about whether you performed it |
| Recommendation | recommendation |
You, if you choose | Nothing, unless you send a report | Nothing |
| Customer report | report |
You send. Esign Comply receives. | Customer-supplied material: content hash and receipt time | "The customer reported this. Esign Comply received the report at the time shown and did not verify it." |
A few consequences:
- A record condition exists only for something Esign Comply can observe in the ceremony. Where the law also requires something it cannot observe, that remainder is a separate obligation part.
- An obligation or a recommendation never blocks a session, never adds a required step and never produces an API error. Only record conditions do, and only once your profile has adopted them.
- An obligation is listed only where a cited source places the duty on a party in your position. Where the law only shifts risk, the part is a recommendation.
- Obligation text names the duty holder and the source. Recommendations appear under the words "Esign Comply recommends" and never use the word "must".
- The lists are not exhaustive and are not legal advice. You remain responsible for every obligation that applies to you, whether or not Esign Comply listed it.
The pack pages group each rule's parts under these headings: "Esign Comply records or checks", "Your obligations", "Recommendations" and "What you can send us". The generated prompt uses the matching four headings. Browse them in the pack catalogue.
What Esign Comply will and will not say
| Subject | It will say | It will not say |
|---|---|---|
| An observed event | That its server received the event at the time shown, with the measurements shown | That the person named is who acted, or that they read the document |
| An asserted field | That you supplied it, and when | That it is accurate |
| A verified email or phone | That a person controlling that address or number took part in the ceremony | That the person is the named signer in law |
| A record condition | Whether the measurable check was met | That the flow is lawful or that an agreement is valid |
| Your obligations | Which obligations its rule packs identify for your selections | That you performed any of them |
| A supplement | That it received these exact bytes at the time shown | That the content is true, or that a duty was performed |
| The seal and timestamp | That the stored record matches the sealed hash, and that the hash existed no later than the timestamp | When the person actually acted |
| Conformance findings | Measurable design facts and suggested fixes | That a flow meets any law |
Conformance findings are advisory. Pass or fail judgments are not printed on evidence reports or certificates. Record conditions that were in advise appear under "Rules applied" as evaluated and not enforced for that record.
Notes your team keeps
In the dashboard, a team member may mark an obligation or a recommendation "handled", "not applicable" or "open", with a note. These marks are your own working notes. They are logged with user and time, they are not evidence that the obligation was performed, and they never appear on an evidence report, a certificate or the signer's view.
Related
- Evidence for how records are sealed.
- Guidance and adoption for how obligations and recommendations reach you.
- Conformance for the checks behind record conditions.