Reference
Glossary
| Term | Meaning |
|---|---|
| Action | An event recording something done in the world: name, target, when, result. |
| Adverse | An outcome that went against the subject. Triggers notice duties. |
| Agent | The software that made or carried out a decision. |
| Approval | An event recording whether a person was asked, who answered, with what authority, and what they decided. |
| Artifact | The original bytes behind a fingerprint, stored in custody under that fingerprint. |
| Assurance | How events were captured: observed, attested or enforced. Never upgraded by Stratl. |
| Bundle | A zip with one record, its key, its originals, its checkpoint and a manifest. Verifies offline. |
| Canonical form | RFC 8785 serialisation of a record without its integrity block. What is hashed and signed. |
| Chain | Each record’s link to the previous record’s hash and its position in the workspace stream. |
| Checkpoint | A signed, timestamped Merkle root over every record since the last one. Proof of completeness and time. |
| Connector | A pull source that fetches from a provider on a schedule: Langfuse, Anthropic Compliance API. |
| Custody | Who holds the storage and the signing key: stratl (managed) or customer. |
| Decision | One unit of AI-influenced work affecting one subject. One record. |
| Decision id | DEC- and a ULID. Stratl’s own records use DEC-WF-, DEC-RC-, DEC-KEY-, DEC-CT-. |
| Event | One observable fact within a decision. Eight types. |
| Fingerprint | sha256: and 64 hex characters identifying exact bytes. Records carry fingerprints, never content. |
| Framework pack | A YAML mapping of a regulation’s controls to record fields. Reports coverage, never compliance. |
| Ingest key | A write-only API key for agents and collectors. |
| Integrity | The block the custodian adds: hash, chain position, signature, key id. |
| Key id | The RFC 7638 thumbprint of a public key. |
| Key-usage record | A DEC-KEY-… record sealing every use of the signing key since the last one. |
| Legal hold | A flag on a decision or a subject that blocks deletion whatever the retention policy says. |
| Lineage | The portal’s timeline of a record’s events. |
| Managed custody | Stratl holds the key and storage, one key per workspace, in the chosen region. |
| Notice | A plain-language letter to a person affected by an adverse decision. |
| Observed | Assurance level: a tracer or SDK saw the events happen. |
| Outcome | How the decision ended for the subject. |
| Period pack | A signed report over a date range against one framework. |
| Provenance | Where a record came from: source, source ids, connector version, ingest time. |
| Reconsideration | A recorded human review of a decision. DEC-RC-…. |
| Record hash | SHA-256 of the canonical form. |
| Retention policy | How long a workspace keeps records before they may be deleted. |
| Retrieval | An event recording documents looked up, as fingerprints. |
| Role | Owner, admin, engineer or auditor. |
| SRF | The Stratl Record Format, the open specification for a decision record. |
| Subject | The person or thing a decision was about. |
| Subject pack | Every bundle about one subject, their notices and holds, with a signed manifest. |
| Timestamp authority | An RFC 3161 service that dates checkpoints. Independent of both parties. |
| Transfer record | A DEC-CT-… record written when custody moves to the customer’s cloud. |
| Workflow record | A record of Stratl’s own action on your evidence. DEC-WF-…. |
| Workspace | A company’s private space: key, chain, records, members, settings. |