FTB-C000736 / Implementation concept

WORM storage

WORM storage constrains overwriting or deleting protected data under a defined write-once-read-many retention policy.

Also known aswrite-once-read-many storage

Advanced 2 linked topicsEvidence-reviewed

Definitions

In plain terms

A retained version can remain protected even while a system creates a different newer version.

Technical

D30 checks consistency of a supplied synthetic retention receipt with a named version and policy; its local model does not authenticate a provider or query live retention.

Scope

Retention mode, holds and privileged permissions matter; WORM does not prove the stored statement is true.

Examples

  • A synthetic anchor receipt names one protected object version rather than just a reusable object key.

Common misconceptions

  • A new version under the same key does not mean the protected prior version was overwritten.

Concept relationships

Related

Where this concept is used

Evidence and governance

  1. Locking objects with Object Lock Amazon Web Services · official platform documentation

    Supports: preferred label, short definition, variant distinction

    Limits: Retention modes and permissions differ; protection does not prevent new versions or prove payload truth.

  2. D30 glossary teaching-profile scope, Batch 013 The Fintech Builder · internal governed contract

    Supports: technical definition

    Limits: No independent regulatory mandate, real-bank dataset, service execution, external witness or production assurance is claimed.

Reviewed by
fintech-builder-batch-013
Last reviewed
2026-10-27
Next review
2027-10-27
Record status
evidence reviewed

This record is evidence-reviewed and readable, but not yet promoted to published — it is served noindex,follow and excluded from the sitemap.

Written by

Fintech engineer building market-data and financial systems, and the author of every article, glossary record, and reference implementation on The Fintech Builder.