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
@@ -3,10 +3,10 @@
|
||||
Data flows both ways:
|
||||
|
||||
```
|
||||
community form, register, PDF ──┐
|
||||
community sources, reports ─────┐
|
||||
├─► threshing-atlas ──► policy.json + solver.js ──► bot (advice per screen)
|
||||
bot runs (anonymised) ──────────┘ ▲ │
|
||||
└──────────── import-bot + pull request ◄──┘
|
||||
└──────────── collection --source bot + PR ◄┘
|
||||
```
|
||||
|
||||
## 1. From the atlas to the bot
|
||||
@@ -129,7 +129,7 @@ Current headline (from `analysis/reports/POLICY.md`): Black about 1.7% per attem
|
||||
|
||||
## 2. From the bot to the atlas
|
||||
|
||||
Already in place: `npm run import-bot -- --bot /path/to/DragonKind` in the atlas repo converts the bot's
|
||||
Already in place: `DRAGONKIND_BOT_DIR=/path/to/DragonKind python -m collection update --source bot` in the atlas repo converts the bot's
|
||||
`knowledge.json`, `runs.jsonl` and `logs/encounters.jsonl` into anonymised files under `data/bot/`, and refuses to
|
||||
write prose or account names. Commit them by pull request; CI rebuilds the graph and checks everything.
|
||||
|
||||
@@ -147,4 +147,4 @@ What would make the bot's data far more useful (details in `docs/BOT_DATA_PROTOC
|
||||
- The model learns how much history matters from the data. Today it finds that the meadow colour does not depend on
|
||||
earlier choices at all, and the shadow only weakly. The bot's randomised runs are what can confirm or overturn that.
|
||||
- The policy is only as good as the crosswalk between the bot's screen text and the form's variables. If the game
|
||||
changes its wording, `OPTION_PATTERNS` in `solver.js` and `CROSSWALK` in `graph.js` need updating.
|
||||
changes its wording, `OPTION_PATTERNS` in `solver.js` and the crosswalk in `collection/specs/bot.yaml` (written into `graph.js` by `python -m collection build`) need updating.
|
||||
|
||||
Reference in New Issue
Block a user