Skip to content

Add AppNote0021 on integrity models#176

Merged
j616 merged 6 commits into
mainfrom
jamessa-integrity
May 15, 2026
Merged

Add AppNote0021 on integrity models#176
j616 merged 6 commits into
mainfrom
jamessa-integrity

Conversation

@j616
Copy link
Copy Markdown
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
Comment thread docs/appnotes/0021-media-integrity.md Outdated
Comment thread docs/appnotes/0021-media-integrity.md Outdated
@j616 j616 force-pushed the jamessa-integrity branch from b546201 to 295d5f2 Compare March 30, 2026 10:55
@samdbmg samdbmg linked an issue Apr 29, 2026 that may be closed by this pull request
Copy link
Copy Markdown
Member

@samdbmg samdbmg left a comment

Choose a reason for hiding this comment

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

LGTM overall. Couple of suggestions and some nits inlined

Comment thread docs/adr/0048-media-integrity.md

This option may be brittle.
Media in TAMS is commonly stored in a chunk form for flexibility and performance.
The process of chunking and re-combining media can be non-deterministic for many formats.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Nit: Strictly is this process deterministic but chaotic? The same input will produce the same output (there's no noise in the process), but even an insignificant change to the ffmpeg (or similar) version will change it?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

If I'm not mistaken, I think encoding processes can use random data as part of their process. But I might be crossing a few wires in my memory there.

Comment thread docs/appnotes/0021-media-integrity.md Outdated
Comment thread docs/appnotes/0021-media-integrity.md
Comment thread docs/appnotes/0021-media-integrity.md Outdated
Comment thread docs/README.md
@j616 j616 force-pushed the jamessa-integrity branch from 494d197 to 11b5c0f Compare May 13, 2026 15:44
@j616 j616 force-pushed the jamessa-integrity branch from 11b5c0f to 9890402 Compare May 13, 2026 15:56
@j616 j616 merged commit 65f1ff3 into main May 15, 2026
8 checks passed
@j616 j616 deleted the jamessa-integrity branch May 15, 2026 16:16
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.

Document integrity and checksum models in TAMS

3 participants