e317952c3f
Created comprehensive guide for creating scoped Gitea token for Pokerole project: - Step-by-step token creation in Gitea UI - Proper scope selection (repo read/write only) - Vaultwarden storage procedure - Testing procedures (verify access/no-access) - Session prompt update instructions - Security benefits comparison - Troubleshooting common issues - Rollback plan Implements Iron Wall principle: enforce boundaries technically, not through honor system. Isolates Pokerole project from Firefrost infrastructure. Task: Scoped Gitea Token (Tier 1) FFG-STD-002 compliant
Scoped Gitea Token for Pokerole Project
Status: Ready
Priority: Tier 1 - Security
Time: 15 minutes
Depends: Vaultwarden operational
Last Updated: 2026-02-16
Overview
Create scoped Gitea API token limited to Pokerole repos only. Replace master token with defense-in-depth boundary enforcement.
Problem
Pokerole project currently uses master Gitea token with "honor system" scoping. Iron Wall principle: enforce technically, not socially.
Actions
- Create new Gitea token scoped to 4 Pokerole repos only
- Store in Vaultwarden
- Update
pokerole-project/misc-docs/SESSION-START-PROMPT.md - Test Claudius access (Pokerole repos ONLY)
- Remove master token reference
Success Criteria
- ✅ Scoped token created and stored
- ✅ Claudius isolated from Firefrost infrastructure
- ✅ Defense in depth enforced
Fire + Frost + Foundation 💙🔥❄️