Moves only; no behaviour changes. Every file now lives under the part of the project it belongs to, each section has a README, and docs/PRIVACY.md collects the rules all parts follow. core/ engine.js, graph.js, solver.js, python/clean.py collection/ sources/ (form, register, PDF check, daily update), bot/ (importer) analysis/ stats/ (Python statistics), network/ (build-graph.js), reports/ (POLICY.md) planner/ build-policy.js, policy-report.js site/ atlas/ (the page), build.js, qa/ tests/ core/ (unit), parity/ (JS vs Python), fixtures/ Checked against the previous layout: tests pass; coded runs, test outputs, graph.json and policy.json are byte-identical; the built site differs only in comments that name file paths. The published file names Ken's bot downloads (solver.js, graph.js, data/policy.json) are unchanged. Also removes the undefined/ folder of QA screenshots committed by mistake (the QA scripts now default to a temp folder) and test.txt, and drops the unused npm workspaces. Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
1.7 KiB
1.7 KiB
Privacy and licences
Rules every part of the project follows. If a change would break one, stop and ask first.
What may be published
- Code is MIT (
LICENSE). Data this project produces is CC BY 4.0 (DATA_LICENSE.md). Third-party sources keep their own terms. - Community form responses: published as exported, with email addresses in free-text answers redacted by
the coding rules (
core/engine.js,core/python/clean.py). - Dragon Register: only
data/public/register.json. The raw export has rider names and stays local (data/raw/register/is git-ignored). - The community route PDF: never committed or redistributed. Only a fingerprint
(
data/derived/pdf_fingerprint.json) so we can tell when it changes, and a link to the original. - Bot data: only scene fingerprints, short labels, choice text and outcomes. Never game prose, never account
names. The importer (
collection/bot/bot.js) refuses to write anything that looks like either.
The bot
- Ken's bot repository stays private. Only the anonymised import comes here.
- Account ids are salted and hashed. The salt (
DK_ACCOUNT_SALT) lives in the environment and is never committed. - The bot's browser profiles,
.envand credential files are never committed or shared.
Sources we do not scrape
- Discord: not without the server admins' consent; never with a personal account token.
- Reddit: not collected yet. When it is, it should go through Reddit's official API with an app key, not page scraping.
Secrets
ATLAS_BOT_TOKEN(repository secret) lets the daily data update open and auto-merge its pull request (docs/REPO_SETTINGS.md). Tokens go in secrets only: never in a file, issue, chat or commit.