PhysKit

Home / How it works

How PhysKit works

What the plugin contains, the five skills to know by name, and who does what inside a closed-loop research campaign.

What's inside

Five skills to know by name

frame-problemstart any physics problem here — before modeling, simulating, or deriving
verifycheck a result, number, or derivation before relying on it
reportwrite it up — every number labeled by provenance, every citation verified
new-campaignstand up a closed-loop research campaign
campaign-statushealth-check or checkpoint a running campaign

Inside a campaign

Inside a campaign, as a grid of who does what (rows) in each stage (columns: setup, one loop unit, report). Researcher: describe the problem and approve the spec; optionally check in, steer, or resolve an escalation; decide next steps. Interactive agent: interview and frame, run a setup audit, act as concierge during the loop (launch, monitor, relay; it runs no experiments), and present the report. Driver, deterministic code: validate and preflight, spawn each worker with a brief, watch its heartbeat, score and run gates, assign the check each result is owed, and spawn the capstone. Workers, a fresh context each unit: propose, implement, run, evaluate, verify, record; the next unit reads the journal. Checks, by trigger and preset: unit tests and self-check every unit (minimal and up); self-verify for an implausible score (minimal, light); a surviving new best gets a peer check by the next worker (light) or a fresh verifier (heavy); every result gets a blinded verifier (intensive); the claim audit at the end of the campaign (minimal and up). Records on disk: frozen goal and metric, baseline experiment 000, journal, code snapshot with config and data, logbook and scoreboard, verdicts, the hook-guarded best result, and the verified report.
Inside a campaign: who does what at each stage, which checks each verification preset adds, and what is kept on disk. Colours match the stages of the campaign loop on the home page. Click to enlarge.