Collection as an ETL pipeline; runs_clean.csv from every source; Report a run
- collection/pipeline.yaml declares every source (extract kind, transform, privacy rules, load target, run source); `python -m collection update|build` - extract keeps data/raw/<source>/current + previous only (git-ignored); data/manifest.json records the current raw checksum and change date - transforms are pure; validate checks runs against data/dictionary.yaml before load; load writes byte-stable files only when they change - data/public/runs_clean.csv: every run from every source with a new `source` column (reddit spreadsheet, reddit thread, reported, bot, reddit pdf); the sheet's own row label moves to `entry`; run_id is text - bot importer ported to Python (same output as bot.js on the fixture); labels and crosswalk in collection/specs/bot.yaml, written into graph.js - Reddit through the official API (result links to add by hand); the 12 result pages move to collection/manual/reddit_results.yaml - "Report a run": a GitHub issue form generated from collection/specs/report_form.yaml, collected as source "reported", plus a site tab pointing to it, the community spreadsheet and the megathread - analysis and the route model read runs_clean.csv (sources in measures.yaml); stats.json and policy.json unchanged apart from the factor's new name - daily workflow runs the pipeline; the raw store is kept between runs in the Actions cache, encrypted with RAW_ARCHIVE_KEY Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
61bc50583c
commit
3b24a11f5a
+4
-3
@@ -6,8 +6,8 @@
|
||||
* or a terminal (BURNED, BONDED:<colour>). Chance shows up as one option leading to several scenes,
|
||||
* e.g. "head toward the centre" -> a Red OR a Brown first sighting.
|
||||
* 2. Decision-variable graph (all sources): the coarse variables the community form asks about
|
||||
* (company, direction, first sighting, ...). Bot trajectories are mapped onto it with CROSSWALK, so bot and
|
||||
* form runs can be counted side by side, per source.
|
||||
* (company, direction, first sighting, ...). trajectoryVariables() maps a bot trajectory onto it with CROSSWALK
|
||||
* (written from collection/specs/bot.yaml; the Python importer uses the same file), for the bot's advisor.
|
||||
*
|
||||
* Trajectories keep the full ordered history of each attempt, so history-dependent (non-Markov) models can be fitted
|
||||
* later without changing the data format.
|
||||
@@ -79,6 +79,7 @@
|
||||
|
||||
/* ---------- Crosswalk: bot option text -> community form variables ---------- */
|
||||
|
||||
// BEGIN CROSSWALK: written by `python -m collection build` from collection/specs/bot.yaml (edit that file)
|
||||
const CROSSWALK = [
|
||||
[/^enter the valley alone/, "company", "Alone"],
|
||||
[/^enter the valley with one of your squadmates/, "company", "1 Squadmate"],
|
||||
@@ -104,7 +105,6 @@
|
||||
[/^allow your squadmate to exact/, "resolution", "Squadmate's revenge"],
|
||||
[/^leave the bullies alive/, "resolution", "Left bullies to the dragons"],
|
||||
[/tourniquet/, "resolution", "Tourniquet"],
|
||||
// the wounded cadet's other two choices (the bot has not logged this screen yet, so these are kept loose)
|
||||
[/leave (them|him|her) to die/, "resolution", "Left injured cadet"],
|
||||
[/take (their|his|her) weapons?/, "resolution", "Took their weapons"],
|
||||
[/^walk toward the east/, "post_path", "East"],
|
||||
@@ -117,6 +117,7 @@
|
||||
[/^reds are too hot tempered/, "red", "Let it pass (two Greens)"],
|
||||
[/^jump (now|in a few seconds)/, "red", "Jump onto the Red"]
|
||||
];
|
||||
// END CROSSWALK
|
||||
|
||||
/** Map one bot trajectory onto the form's decision variables. Unmapped choices are listed, not guessed. */
|
||||
function trajectoryVariables(traj) {
|
||||
|
||||
Reference in New Issue
Block a user