Skip to content

Quality Evidence Storage

Store verification artifacts in this folder using stable STR-style paths and a two-lane model.

Evidence lanes

  • Formal (tracked, commit-intended):
  • Docs/Quality/Evidence/Formal/
  • Algo formal path: Docs/Quality/Evidence/Formal/STR-ALG-001/
  • Automated freeze path: Docs/Quality/Evidence/Formal/STR-AUTO-001/
  • Security freeze path: Docs/Quality/Evidence/Formal/STR-SEC-001/
  • Working (non-formal development runs, git-ignored):
  • Docs/Quality/Evidence/Working/
  • Algo working path: Docs/Quality/Evidence/Working/STR-ALG-001/

Policy: - Only runs explicitly classified as formal belong under Formal. - Routine/iterative runs belong under Working. - Older non-formal artifacts are expected to be cleaned up regularly and are not submission evidence.

Path convention

  • Formal STR path:
  • Docs/Quality/Evidence/Formal/STR-<ID>/YYYY-MM-DD-<short-scenario>/
  • Legacy STR path (kept for existing non-Algorithm evidence already in repo):
  • Docs/Quality/Evidence/STR-<ID>/YYYY-MM-DD-<short-scenario>/
  • Working (ignored) path:
  • Docs/Quality/Evidence/Working/STR-<ID>/YYYY-MM-DD-<short-scenario>/

Examples: - Docs/Quality/Evidence/Formal/STR-ALG-001/2026-02-18-tv-alg-013-verification/ - Docs/Quality/Evidence/Formal/STR-AUTO-001/2026-04-XX-ide-freeze-auto-baseline/ - Docs/Quality/Evidence/Formal/STR-SEC-001/2026-04-XX-ide-freeze-tv-sec-001/ - Docs/Quality/Evidence/Working/STR-ALG-001/2026-02-18-dev-rerun/ - Docs/Quality/Evidence/Formal/STR-SIM-001/2026-02-19-tv-sim-baseline/ - Docs/Quality/Evidence/Working/STR-SIM-001/2026-02-19-h5-smoke/ - Docs/Quality/Evidence/STR-BUG-001/2026-02-11-relaunch-meal/ - Docs/Quality/Evidence/STR-UI-003/2026-02-12-cgm-cancel-flow/ - Docs/Quality/Evidence/STR-UI-AUTO-001/2026-02-12-f5-ui-smoke/

What to place in each evidence folder

  • Screenshots (.png/.jpg) used for verification.
  • Log excerpts (.txt) with timestamps and relevant runtime lines.
  • Optional test command output snippets (.txt).
  • A short README.md summarizing:
  • test context
  • exact steps
  • pass/fail result against acceptance criteria

For new formal freeze bundles, prefer the shared authoring shell:

Naming guidance

  • Keep file names sortable and explicit:
  • 01-home-before.png
  • 02-meal-composer-open.png
  • 03-post-delivery-home.png
  • 04-recent-steps.png
  • logs-relaunch-meal.txt