Skip to content

Add AppNote0021 on integrity models#176

Open
j616 wants to merge 4 commits intomainfrom
jamessa-integrity
Open

Add AppNote0021 on integrity models#176
j616 wants to merge 4 commits intomainfrom
jamessa-integrity

Conversation

@j616
Copy link
Contributor

@j616 j616 commented Feb 20, 2026

Details

This PR adds AppNote0021 which describes basic and advanced integrity models used in TAMS. The advanced model describes how checksums may be used for archived workflows.

Jira Issue (if relevant)

Jira URL: https://jira.dev.bbc.co.uk/browse/CLOUDFIT-5503

Related PRs

Where appropriate. Indicate order to be merged.

Submitter PR Checks

(tick as appropriate)

  • PR completes task/fixes bug
  • API version has been incremented if necessary
  • ADR status has been updated, and ADR implementation has been recorded
  • Documentation updated (README, etc.)
  • PR added to Jira Issue (if relevant)
  • Follow-up stories added to Jira

Reviewer PR Checks

(tick as appropriate)

  • PR completes task/fixes bug
  • Design makes sense, and fits with our current code base
  • Code is easy to follow
  • PR size is sensible
  • Commit history is sensible and tidy

Info on PRs

The checks above are guidelines. They don't all have to be ticked, but they should all have been considered.

@j616 j616 requested a review from a team as a code owner February 20, 2026 15:24
@j616 j616 force-pushed the jamessa-integrity branch from 5bd4c8e to 29c4147 Compare February 20, 2026 15:30
With that warning in mind, this section is going calculate the probability of loss of media for various segment sizes.
We shall use a round number of 10 million hours of media.
We shall assume that the 10 million hours is total mono-essence media (i.e. separate audio and video Flows).
Note that we are using duration of media here, not amount of data, as durability the durability figure we are using is dependent on the number of Objects, not the size of them.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the word "durability" included multiple times here for redundancy? :P

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

#### Worked examples

> [!WARNING]
> This section is going to miss-use the above SLA durability value as if it is a genuine probability of Object loss.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AWS describes 11 nines durability as something that S3 is "designed" to provide. I don't think it's an SLA commitment in the conventional sense. I'm not sure about other cloud storage providers.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good spot. All three mention this figure using similar language. And all three link out to SLAs. But those SLAs don't seem to mention those figures themselves. I've removed "SLA" here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants