Skip to main content
A fingerprint template is the structured form (blank template) that Stratum’s fingerprint classification matches against. A Rule Package’s fingerprint detector references a registered form and classifies documents written on that form at the designated grade. Fingerprint classification is a high-confidence signal — “a document on this form is this grade” — but it only works once the blank form it matches against has been registered. This page covers that management flow: registering, revising, and re-viewing forms.

​
A project-owned asset

Blank forms are customer-specific, so fingerprint templates are owned by one project (tenant) and never shared with other projects. They aren’t platform-standard resources distributed to every tenant — they’re project-level assets like Taxonomies and Rule Packages, referenced by that project’s Rule Package.

​
Registration and retention — two separate layers

Registration follows Stratum’s principle of “nothing retained in the classification engine, retention on the audit plane”: What gets registered is a pre-fill form, not customer data, so retaining the original creates no personal-data exposure. This original is a reference asset retained for as long as the registration stands — distinct from request-trace originals, which are subject to retention-period disposal. This two-layer split is what makes both hold at once: “no originals in the engine” and “you can always see what was registered.”

​
Management tasks

Administrators can do the following with registered forms:
  • Review status and re-view originals — see the status of registered forms and re-open or download each form’s original from the audit plane.
  • Revise (register a new version) — when a form is revised, register it as a new version of the same form. Prior versions are preserved as history for audit and rollback.
  • Check references — trace backwards which Rule Packages reference a given form, to prevent an in-use form from being deleted out from under a working classification.

​
How it connects to the Rule Package

A Rule Package’s fingerprint detector points at a registered form and classifies documents written on it at the designated grade. When a form is revised, update the version the detector references; whether the reference is valid (the referenced form and version exist) is verified when the Rule Package is activated — a broken reference blocks activation.

​
Permissions and audit

Registering, revising, and deleting fingerprint templates requires the same administrative permission as policy editing (Project Admin or above), and as governance changes they’re recorded in the Audit Log. Because registering forms — file upload plus fingerprint retention — differs in character from editing text policies, it’s provided as a management flow separate from Taxonomy and Rule Package editing.