Skip to main content
Human-readable text is structured content, not an unrelated PDF attachment. It can reference roles and parameter values so the document a signer reads is generated from the same contract object the client signs.

​
Language selection

Provide one HumanReadableText document per supported language. Clients select an exact language match and otherwise fall back to the first available document. Put the primary/legal fallback first.

​
Bind values into text

Use the contract human-readable element model for:
  • paragraphs and sections;
  • lists and tables;
  • emphasis and links;
  • parameter values;
  • role names and role-reference values;
  • conditional content supported by the schema.
Do not paste calculated values as fixed prose. A parameter reference ensures the rendered value follows the signed instance.

​
Rendering

The .NET contract model can render selected text to:
Render with the contract library so parameter formatting, language choice, and supported elements are consistent.

​
Approval checklist

Before proposing a template:
  1. Render every language.
  2. Substitute boundary values for every parameter.
  3. Confirm required roles, counts, dates, fees, units, and termination rules agree with the machine section.
  4. Confirm links and attachments are durable and authorized.
  5. Confirm no unsupported language silently falls back to misleading text.
  6. Have the Trust Provider review both sections together.
A translation can change legal meaning. Machine translation is a drafting aid; each production language version requires appropriate review.