bearing-northstarslisted

# North-stars — the project's semantic anchor ## Two files, one discipline - **`.bearing/northstars.md`** — what **this project** is. Yours; bearing never overwrites it. - **`.bearing/gold-practices.md`** — how the work is done. Two halves: bearing's `GP-#` block, which refreshes on update and must not be edited, and **below the END marker, this project's own `PP-#` practices**, which bearing never touches. Put a practice you learned here, not in the north-stars: north-stars say what the project IS, a practice says how work is done. Cite both the same way. **On conflict the `NS-#` wins**, because a project's own invariant is more specific than a general rule — say which one and why rather than averaging them. ## The problem this solves Code drift is caught by tests. **Semantic drift is not.** You read a stale doc, quietly redefine a load-bearing term, and everything downstream — research, conclusions, which ideas you champion and which you discard — forks in the wrong direction while reading perfectly fluent and confident. Long sessions make it worse: whatever anchored you at session start is diluted by 100k tokens of context. Mature repos make this *certain*, not merely possible: docs accumulate, contradict each other, and go stale, while the code moves on. Without a declared fixed point, "what this project is" becomes whichever document you happened to read last. **The north-stars are that fixed point.** `.bearing/northstars.md` — short, numbered, falsifiable p