4.5 KiB
4.5 KiB
GameCult Access Instructions
Project Purpose
GameCult Access exists to hold the shared auth and access-control architecture for GameCult-hosted experiments without letting that shared layer metastasize into a giant mixed-data pit.
The planned reusable backbone is:
- provider OAuth and linking
- signed local sessions
- entitlement refresh
- capability evaluation
- app-facing access claims
The planned non-shared-by-default layer is:
- app-domain user data
- audience data
- creator data
- queue/job payloads
- product-specific state
Canonical State
- Treat
state/map.yamlas the canonical current project map. - Treat
state/scratch.mdas disposable working memory for one bounded subgoal. - Treat
state/evidence.jsonlas the distilled durable ledger of decisions, verified boundaries, and rejected paths. - Treat
state/branches.jsonas hypothesis tracking, not phase/status prose. - Treat
notes/fresh-workspace-handoff.mdas the compact re-entry packet. - Treat
docs/architecture.mdas the source-grounded shared architecture note. - Treat
docs/implementation-plan.mdas the forward plan. - Treat
docs/app-profiles/repixelizer.mdanddocs/app-profiles/streampixels.mdas thin app bindings, not the whole shared architecture.
Important Paths
- Project root:
E:\Projects\gamecult-access - Shared architecture:
E:\Projects\gamecult-access\docs\architecture.md - Implementation plan:
E:\Projects\gamecult-access\docs\implementation-plan.md - Repixelizer profile:
E:\Projects\gamecult-access\docs\app-profiles\repixelizer.md - StreamPixels profile:
E:\Projects\gamecult-access\docs\app-profiles\streampixels.md - Handoff summary:
E:\Projects\gamecult-access\notes\fresh-workspace-handoff.md - State CLI:
E:\Projects\gamecult-access\tools\gamecult_access_state.py - Pre-compaction helper:
E:\Projects\gamecult-access\tools\gamecult_access_prepare_compaction.py
Useful Commands
This repo does not carry a dedicated virtualenv yet. Use any working Python
3.11+ interpreter. On this workstation, E:\Projects\repixelizer\.venv\Scripts\python.exe
is known-good.
Preferred here:
E:\Projects\repixelizer\.venv\Scripts\python.exe .\tools\gamecult_access_state.py status
E:\Projects\repixelizer\.venv\Scripts\python.exe .\tools\gamecult_access_state.py add-evidence --type design --status accepted --note "..."
E:\Projects\repixelizer\.venv\Scripts\python.exe .\tools\gamecult_access_prepare_compaction.py
Fallback if a normal python command exists:
python .\tools\gamecult_access_state.py status
python .\tools\gamecult_access_state.py add-evidence --type design --status accepted --note "..."
python .\tools\gamecult_access_prepare_compaction.py
Session Bootstrap And Re-entry Protocol
On fresh session load:
- read:
state/map.yamlnotes/fresh-workspace-handoff.mddocs/architecture.mddocs/implementation-plan.md
- run:
python .\tools\gamecult_access_state.py statusgit status --short --branchgit log --oneline -5
- restate the current next action from persisted state before editing
After compaction or suspicious continuity loss:
- rerun
gamecult_access_state.py status - reread
state/map.yamlandnotes/fresh-workspace-handoff.md - treat the persisted next action as authoritative unless fresh evidence contradicts it
When the user says to prepare for imminent compaction:
- run
tools/gamecult_access_prepare_compaction.py - update only the state that actually changed
- rerun the helper
- commit the completed persistence pass unless the work is deliberately mid-surgery
Operating Discipline
- Before substantial edits, restate the current mechanism and intended change.
- Keep the shared backbone separate from app-domain data unless there is a very deliberate, source-grounded reason to share something.
- Prefer embedded shared-package mode before inventing a dedicated auth service.
- Do not let app profiles turn into duplicate copies of the shared architecture.
- If the diff grows while the boundary gets blurrier, stop and simplify.
- Before handoff or compaction, sync
state/map.yaml, refreshnotes/fresh-workspace-handoff.md, add distilled evidence when future belief changed, and make the next action explicit.
External Context
- For StreamPixels architecture/auth context, prefer the indexed
StreamPixelsrepo throughvoidbotbefore filesystem spelunking. - For GameCult deployment and host conventions, check
E:\Projects\gamecult-opsbefore improvising infra claims.