# Seed-role clarification and search limitation

The registered search used case-sensitive PLAN.json / CASES.json / PROTOCOL.md /
COMMAND.json globs and found no matches across 171 files. A supplementary,
case-insensitive search after registration found 96171 and 96173 in earlier
student-run names. Inspecting the actual plan and all 16 matching native commands
resolves their roles: 96171/96173 were optimizer seeds; the physical execution
seed was 96161. The exact command arguments and hashes are recorded in
SEED_ACCESS_SUPPLEMENT.json. Other broad search hits are numeric substrings.

No prior exact native execution seed 96171 or 96173 was found in the inspected
command records. They are new execution seeds for this clearance series, while
the same integers have historical training uses. This does not establish a
globally untouched dataset, new motion source, or independent scene family.

An intermediate progress note described these as previously used seeds before
resolving optimizer versus execution roles. The distinction above supersedes
that broad interpretation. The registered tasks, order, motor and outcomes are
unchanged; there is no post-result seed swap or additional physical execution.