SSM-Clock—Acceptance Note & Provenance Chain (7.7–7.8)

7.7 Minimal acceptance note (plain TXT, 6 lines)

Create once and keep with the golden CSV.

Save as

notepad notes\SSM_Clock_Acceptance_v1.1.txt

Paste exactly (edit only the commit/tag if needed)

SSM-Clock v1.1 Acceptance (ASCII)
Period set: 1,7,29.5306,365.2422
Knobs: grid=2min, S=5, dt=0.5d, K=7, alpha_kz=0.0, horizon=max(periods)
Results: 2deg -> 200/200 PASS (mean 2.7, P95 6.5); 6deg -> 199/200 PASS (mean 8.2, P95 19.6)
Summary CSV: notes/longbench_summary.csv
Release tag/commit: v1.1 / <short-commit-id>

Why this helps. Auditors can verify the gate, period set, knobs, the exact CSV path, and the release reference in a single glance—no extra metadata required.

7.8 Provenance chain (who did what, when)

Include these items for each release run

Input artifacts: clock_manifest.json (and version label), any observed CSVs used for tests, and the script names/versions (or git tag/commit).
Process: the exact command lines executed (copy-paste from console), environment details (OS, Python version), and an optional run timestamp.
Outputs: notes\longbench_summary.csv (canonical), optional notes\longbench_detail.csv (per-seed errors), notes\SSM_Clock_Acceptance_v1.1.txt (the 6-line note), and any audit/review zip you produced.
Signer: the person/system who ran the bench; include short name/ID and a brief contact line.

Template (append to your repo as notes\provenance.txt)

Run: SSM-Clock v1.1
Signer: <name or system id>
Contact: <email or handle>

Inputs:
  manifest: clock_manifest.json (version v1.1)
  scripts: ssm_clock_runner.py, ssm_clock_longbench_v2.py, ssm_clock_stream_v2.py
  observed CSVs: <list or N/A for synthetic>

Process:
  OS: <e.g., Windows 11 / Ubuntu 22.04>
  Python: <e.g., 3.11.x>
  Commands:
    python ssm_clock_longbench_v2.py --period_sets "1,7,29.5306,365.2422" --seeds 200 --noise_list "2,6" --grid_step_min 2.0 --alpha_kz 0.0 --stack 5 --stack_dt_days 0.5 --multistart_k 7 --refine brent --refine_steps 80 --bracket_mult 2

Outputs:
  summary: notes/longbench_summary.csv
  detail:  notes/longbench_detail.csv   # optional
  acceptance: notes/SSM_Clock_Acceptance_v1.1.txt
  audit zip: dist/SSM-Clock_v1.1_Audit_YYYYMMDD_HHMMSS.zip

Release ref:
  git tag: v1.1
  git commit: <short-commit-id>

Tip. Keep commands and file names ASCII-only, and prefer relative paths rooted at the project directory for portability.

Navigation

Back: SSM-Clock—Governance, Smoke Tests & Naming (7.4–7.6)
Next: Appendix A — CLI Reference & Pocket Calculator