prospect

Do computational research that survives review — the agent-era methodology for going from a vague area to published results, for fields where you run experiments to publish (machine learning, combinatorial optimization, operations research, systems, scheduling). A pipeline of gated lenses for six research steps: prospect (find and prove a defensible gap — mine-don't-read, seven seams run in parallel, survive an adversarial 'prove it's already done' attack), crucible (design the method — race death-cause-orthogonal variants to death against pre-committed kills, measure the ceiling with an oracle ladder first, trap the agent's infeasible-solution bugs with an independent feasibility checker), ledger (design the experiments — write down what counts as evidence before you look, firewall exploration from confirmation, freeze the protocol before the run), forge (run the experiments — harden the method into production experiment code, run it idempotently with the agent as a read-only operator, regenerate every table and figure with one command), reckoning (analyze the results — audit before you read, prove WHY with mechanism probes, defend against the garden of forking paths, settle every claim to a verdict), and envoy (write, submit, and defend — string the already-built argument into a manuscript, choose the venue by fit, hold the agent to its red lines so every number traces to a run id, defend through rebuttal, and persist up the resubmission ladder). Across all six the agent is the means (parallel miner, prototyper, experiment operator, adversarial reviewer, manuscript polisher), never the oracle — you keep taste, spec, judgment, and the signature on the claims. Note: the gates are enforced by the `checklist` CLI, which installs separately — see the repository README.