Repository navigation
docs: sample Migration Verification Report from a real run (#59) - #216
Merged
Merged
Conversation
…on report (#59) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011T6Wqm1jLdq3ZEfuKdp9aM
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011T6Wqm1jLdq3ZEfuKdp9aM
Generated by scripts/sample_verification_run.py against a fresh PostgreSQL 16 database and the live API at code version 01602c1: 12 of 12 checks pass. The raw responses and database reads behind every figure are in docs/samples/verification-run-evidence.json. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011T6Wqm1jLdq3ZEfuKdp9aM
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A sample Migration Verification Report (
docs/samples/MIGRATION_VERIFICATION_REPORT_SAMPLE.md) produced by a real run, plus the script that produces it and the raw evidence behind it.Refs #59. Not
Closes: whether this meets "a Defence buyer could review" is the product owner's call, and the repo rule is that issues close on clean evidence.scripts/sample_verification_run.pydocs/samples/orgs_sample.csvdocs/samples/equipment_register.csvdocs/samples/verification-run-evidence.jsondocs/samples/MIGRATION_VERIFICATION_REPORT_SAMPLE.md"Every figure traceable to a real run"
Nothing in the report is typed by hand. The script renders it from the evidence it records. The run was against PostgreSQL 16.15, the live API (real sign-in, real tenant schema) and a fresh database, at code version
01602c1. Result: 12 of 12 checks pass (6 of 10 T&E rows loaded, 4 rejected exactly as designed; 8 of 8 dynamic rows loaded; duplicates refused; audit chain intact).The checks can fail
Re-running the script against the now-populated database exits 1 and writes "NOT RECONCILED" with 3 failed checks. I did that before committing, so a green report is not the only outcome the harness can produce.
What the report deliberately does not claim
Section 8 of the report says so in its own words: synthetic data only, development configuration (observed during the run: unauthenticated requests return 200, and the API connects as the audit table's owner), developer-run rather than independent, no ASDEFCON/DID claim (#159 is still open), and re-upload in T&E mode is unsafe (#215).
Found along the way
main.Reviewer notes
markdownlint-cli2reports 0 errors on the report.Generated by Claude Code