Akọsílẹ̀

Use this workspace only when shared repository state or protected concurrent publication is actually needed and selected. Ordinary plans, reviews, and artifacts can stay in the conversation or an existing project destination. Do not create .qp merely because another skill contributes to the task.

Own one repository's workspace contract. Semantic owners supply record/artifact kind, stable subject, and semantic content. Akọsílẹ̀ owns canonical repository state, stable paths, reconstructible worktree aliases, safe publication, sparse settings mechanics, and generated navigation.

Use native Git/filesystem capability for ordinary discovery, allocation, symlinks, inspection, hashing, and Git excludes. Keep bundled code only for two deterministic kernels:

safe-write.py   expected candidate+target digests → exact compare-and-swap publication
render-index.py canonical record frontmatter → Markdown on stdout

Read workspace contract for paths/publication, worktrees when aliases or legacy physical stores are material, and settings only for settings work.

Establish the canonical workspace

Resolve the repository's exact Git common directory from Git metadata and make <git-common-dir>/qp the one physical workspace. Repository state is shared state, not property of whichever worktree happens to be the main worktree.