STRICT-APT/strict-score-record

STRICT score record (strict_score_record_v4)

Per-node, per-member score files behind every table of "Where the Numbers Come From: Auditing Evaluation in Provenance-Based Intrusion Detection". Each file is a PIDSMaker evaluation output (scores_model_epoch_<k>.pkl, written by torch.save despite the extension, with pred_scores, y_preds, y_truth, nodes, node2attacks) at its original relative path, so every manifest verifies unchanged from this directory:

sha256sum -c manifests/MANIFEST_final.sha256

manifests/MANIFEST_<rule>.sha256 bind the frozen member record under the three checkpoint rules (final epoch, minimum validation loss, best ADP); manifests/*_SOURCE_INPUTS.sha256 bind the eight earlier records of the preregistered confirmations; manifests/VALIDATION_INPUTS.sha256 binds the numeric validation losses of the four headline configurations, which the replay of their checkpoint and threshold choices reads. record/ holds the frozen member record: roster_<rule>.csv (configuration, dataset, system, member count), source_audit_<rule>.csv (member, epoch, score file), replacements.csv (retrained members with the replaced and replacing files), nested.csv (same-flag configurations absorbed by a larger one). loader.py prints the contents of one file. Files: 5315 distinct paths.

manifests/VALIDATION_ALL.sha256 binds the numeric validation losses of every member and rule-selected epoch of the frozen record (artifacts/triage/validation-all-20260927/validation/<configuration>_<member>_<epoch>.npz, key losses), together with epochs.csv (every evaluated epoch's test ADP and logged validation loss), selected.csv (the declared epoch beside the epoch the declared selector chooses from epochs.csv) and consistency.csv (whether the saved alerts equal the test scores above the maximum validation loss, where that rule applies); manifests/VALIDATION_ALL_INPUTS.sha256 names the score files those arrays belong to. manifests/W2V_PAIRS.sha256 binds the identical-input word2vec reindexer pairs: artifacts/triage/w2v-identical-20260927/<host>_s<seed>/<attempt>/<released or corrected>/final_scores.pt holds the same keys as a score file, beside the receipts result.json, started.json (environment and bound inputs), final_replay.json, execution.json and initial_equality.json. Attempt directories are attempt0 (realized dropout 0.0, seeds 0 to 9), dropout03_attempt0 (realized dropout 0.3, seeds 0 to 4) and repeat0 (the released member retrained on identical inputs and initial state). record/w2v_identical_pairs/ holds their summary tables. The prepared inputs and the raw edge losses are not published.

The Zenodo record (DOI 10.5281/zenodo.22930594, all versions) archives this README, the manifests, the member record, the loader and the headline validation arrays as strict_record_metadata.tar.zst in numbered parts, joined with cat strict_record_metadata.tar.zst.part* > strict_record_metadata.tar.zst. The score files, the validation arrays of every configuration and the pair files are published here, and the manifests in either copy verify them.