okhp3-project-compass

Topics in the source

• okhp3-project-compass
• Scope
• Related skills
• Phase 0: detection, always first
• Mode A: GitHub-backed
• Mode B: plain folder
• One data model, both modes
• Operating contract

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Compass answers two questions about a folder. First time: what is this project for, and what is it trying to achieve. Every time after: what moved, what stalled, what changed shape, and what quietly died. Before either, it answers a third: where does the tracking actually live. A GitHub clone already has milestones, issues, and releases, so Compass uses them rather than building a parallel tracker. A plain folder has none of that, so the file layer carries everything. -- | In scope | Out of scope | |---|---| | Detecting whether a folder is GitHub-backed and branching accordingly | Guessing at ambiguous evidence; ambiguity resolves to the safe local mode | | Inferring purpose, vision, mission, goals, non-goals, success criteria from evidence | Inventing intent the evidence does not support | | Reading and planning GitHub milestones, issues, sub-issues, labels, releases through gh | Destructive or unauthorized GitHub writes, deletions, or scheduled pushes | | A committed file layer that works offline in both modes | Duplicating full issue bodies into the repository | | Reassessing status against commits, files, docs, issues, and

This is an excerpt. Refer to the complete source and its current requirements.