For the four-family challenge in Layr-Labs/hash-smash-pareto, start with the
Pareto solver task, challenge contract
and production setup. Its import and solver work
directory is pareto. The catalog and original scalar operator guides below
are retained implementation context; their repository-root import instructions
do not apply to the Pareto challenge.
The local registry contains 26 runnable lanes (22 current and four historical), with four deferred Poseidon slots. The root manifest retains eight exploratory registrations; six are intended to compete after closing SHA-256 31/32. Shell commands and plain file paths in current guides are relative to the repository root, which is the single Yukon import and CLI work directory. Markdown links resolve from the containing document. Every Yukon track ID includes its review lane.
- Solver entry point: the single UI reference for challenge-specific rules and deviations from the Yukon CLI skill.
- HashSmash solver skill: practical solver workflow, target/cost checks and advisory review packets.
- Builder entry point: harness ownership, verification, baseline authoring and deployment.
- Frontier lanes: roster, target boundaries, scoring and local commands.
- Judge lanes: review roles, heuristics and acceptance policies.
- Heuristic experiments: manifests and isolated execution.
- Candidate qualification: organizer baseline packages and live-review sequence.
- SHA-256 round migration: rounds 37/38, closed history, qualification, all-lane fingerprints and separate UI rollout.
- Yukon production setup: production source and rollout gates.
- Yukon dev setup: operator imports and deployment gates.
- Participant heuristic test: organizer diagnostic and its limits.
- Frontier validation: dated offline, Docker and live-review evidence.
Effective October 5, 2026:
- HashSmash Terms of Service, including submission licensing and Covered Data in Section 5.
- HashSmash Privacy Policy.
- Frontier research: sources and unresolved target definitions.
- Original HashSmash vision: broader research goals and design discussion.
- Historical MVP validation: evidence from the retired pilot.
- Historical challenge plan: original implementation and rollout design.
- Historical multi-track plan: earlier Yukon routing investigation.
- Unconditional birthday argument: analytical context under the retired resource model.
The archived documents describe earlier behavior; their old commands and layouts
are not supported workflows. Runtime judge policies and prompts remain in
judge/, and assigned lane contracts remain in tracks/.
The former Yukon solver guide remains as a compatibility
link to TASK.md; generic CLI instructions belong to the installed Yukon skill.