coworking-concept-collisionlisted

# Coworking Concept Collision — Defer, Measure, Integrate ## Symptom Two live sessions on one brain tree. Session A is editing a skill (shows `M` in `git status`). Session B (you) authors a NEW skill that claims to "name a primitive for the first time" — and that primitive is exactly what session A is codifying. File-level isolation (worktrees, pathspec commits) does not catch this: the collision is **semantic**, not textual. Shipping both as-is creates two homes for one primitive (accretion) and at least one false claim in the public history. ## Root cause Session isolation protects the *index*, not the *concept space*. `git` will happily merge two skills that contradict each other. The 4D gates check files you touch, not concepts you claim. Nothing fires when two dimensions converge on the same idea unless you read the other dimension's in-flight surface before asserting ownership. ## Fix 1. **Read before claiming.** Before committing any skill that names/owns a concept, check whether a file covering that concept is `M` by another live session (`git status` + `octo-dim list`). If yes, read its CURRENT content (the in-flight version, not HEAD). 2. **Defer to whoever is ahead.** If the other session already codifies the concept, it is the OWNER. Rewrite your claim: your artifact becomes a complementary layer (e.g. measurement vs definition, method vs rationale) that cross-links, never a second home. Two skills, one primitive, no fork ([[harmonization-over-accretion]]).