player_labs

Use to A/B test two Crewrift policy versions head-to-head and decide whether a change actually helped — RIGHT NOW, against the current field. Triggers: 'did my change help', 'compare v2 vs v1', 'A/B test crewborg', 'is the candidate better than the baseline', 'test this hypothesis', 'did fixing the imposter regress the crewmate'. Runs two matched fresh experience requests, compares hard metrics (compare.py) AND guides a context-driven qualitative investigation of the logs/replays. Distinct from crewrift-report, which surveys ONE batch descriptively.

Use to turn a SET of Crewrift episodes (an experience request, a policy's recent league games, a round/tournament batch) into a dense, high-signal report on a player policy's strengths and weaknesses. Triggers: 'analyze/report on these XP-request episodes', 'where is crewborg weak', 'find the interesting/bad/good games', 'what did crewborg do wrong as imposter', 'summarize this batch of replays/logs', post-mortem of an evaluation. Crewrift-specific (roles, votes, kills, expand_replay). Pair with coworld-episode-artifacts (to pull the episodes) and coworld-experience-requests (to create them).

Use to create and monitor Coworld experience requests — hosted batches of episodes you define (target, roster, roles, count) for evaluating agents against a live roster. Triggers: 'run <policy> vs the top opponents', 'make an experience request', 'request N hosted games', 'A/B a policy against the league', 'set up an evaluation battery / matchup'. Game-agnostic; pair with coworld-episode-artifacts to pull the resulting episodes.

Use to run your own built player policy in a LOCAL Coworld episode and watch it — the Gate-1 smoke test ('did my change take, does it connect → play → exit cleanly?'). Triggers: 'smoke test the player locally', 'run a local game', 'run my policy locally and watch it', 'does the build still work', 'open the replay locally'. Game-agnostic; this is correctness only, NOT a competitive matchup (you can't run other users' policies locally).

Use to identify and download Coworld episode artifacts — replays, results, and per-agent logs — for completed episodes. Triggers: 'download the replay/logs for episode X', 'pull the last N episodes <player> played', 'fetch artifacts for this experience request / pool / round', 'get the episode data for post-mortem'. Game-agnostic (Crewrift, amongthem, etc.).

Use to take a built player image through the Coworld policy lifecycle: upload it as a new version, (gated) submit it to a league, and monitor its live standings. Triggers: 'upload the new policy version', 'submit crewborg to the league', 'is my submission live / champion', 'how is my policy ranking', 'ship the player'. Game-agnostic. Upload is routine and inert; SUBMIT is the public, irreversible, champion-making action — only on explicit human go-ahead.

Use to turn a Crewrift report's signals into evidence-grounded, MECHANISTIC improvement hypotheses — by investigating the replays/logs/code for *why* a behavior happens (or fails to), then presenting candidate directions to the human. Triggers: 'why is crewborg weak at X', 'what should we try / where should we go next', 'form hypotheses', 'diagnose this weakness', 'what's the mechanism behind Y', 'turn this report into directions', 'we got lucky in some games — can we engineer that'. Optional AUGMENTATION of the Report step — it adds candidate hypotheses alongside the report's replay-pointers; it does not replace the human's direction call. Pairs with crewrift-report (signals in) and crewrift-ab (to test a hypothesis).