# Akosile > Maintain one repository-scoped workspace shared across Git worktrees. Use for canonical owner-record/artifact paths, worktree-visible `.qp` aliases or migration, exact CAS publication, sparse settings, and generated index rendering. Exclude semantic record meaning/status, project knowledge, provider mutation, and global `~/.qp` storage. - Skill: `quantipixels/akosile` (Agent Skill, multi-file: 9 files) - Install (CLI): `npx skillmds@latest add quantipixels/akosile` - Raw SKILL.md: https://api.skillmd.com/api/skills/quantipixels/akosile/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: quantipixels (https://skillmd.com/u/quantipixels) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/quantipixels/akosile --- # 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: ```text safe-write.py expected candidate+target digests → exact compare-and-swap publication render-index.py canonical record frontmatter → Markdown on stdout ``` Read [workspace contract](references/workspace-contract.md) for paths/publication, [worktrees](references/worktrees.md) when aliases or legacy physical stores are material, and [settings](references/settings.md) only for settings work. ## Establish the canonical workspace Resolve the repository's exact Git common directory from Git metadata and make `/qp` the one physical workspace. Repository state is shared state, not property of whichever worktree happens to be the main worktree. Every registered non-bare worktree may expose a root `.qp` symlink to that canonical directory when a worktree-visible path is useful. The alias is derived state: repair/recreate it from Git metadata rather than treating its target/path as durable state. A bare repository with no worktree can still own canonical state; it simply has no worktree `.qp` alias. Initialize lazily. Create the canonical `qp` directory only when workspace state is first required; do not pre-create empty `settings.json`, `INDEX.md`, `records/`, or `artifacts/`. Keep worktree `.qp` aliases ignored without modifying tracked ignore policy merely for workspace setup. Prefer the repository's shared local exclude when suitable so the same rule applies across worktrees; verify the actual alias is ignored. A directory-only trailing-slash pattern is insufficient for a symlink. If symlinks are unavailable, canonical repository state remains valid, but a consumer requiring the worktree-relative `.qp/...` view has an alias capability gap. Do not create a second physical workspace as fallback. ## Resolve stable owner paths Canonical physical bundles live under `/qp`, while worktree-visible paths remain `.qp/...` when an alias exists: ```text /qp/ ├── records/// │ ├── record.md │ ├── index.html optional human projection │ ├── receipts/ optional │ └── evidence/ optional └── artifacts//index.html ``` Use exact ASCII skill name as owner and lowercase ASCII slug as subject. Do not add date prefixes or automatic collision suffixes. Allocate the exact subject atomically: reuse an existing matching resource, reconcile incomplete/ambiguous allocation, and require the semantic owner to choose a genuinely different subject for genuinely different work. Existing dated bundle paths remain valid legacy identities. ## Publish exact files safely The semantic owner builds and validates a complete candidate outside the canonical workspace. Pin SHA-256 identities for the exact candidate and current target using native host capability; use `absent` only when the target is absent. Publish through the retained kernel against the real canonical root, never through a worktree alias: ```bash python3 /scripts/safe-write.py \ --root /qp \ --target \ --candidate \ --expected-target \ --expected-candidate ``` The helper verifies candidate identity, locks/rechecks the target, atomically publishes already-verified bytes, and verifies readback. On `CANDIDATE_CHANGED`, rebuild/revalidate the candidate; on `STALE_TARGET`, re-read and reconcile semantic state. The helper does not discover paths, parse semantic content, retry, or choose recovery. ## Render navigation Generate an index candidate through the pure transform: ```bash python3 /scripts/render-index.py /qp > ``` The renderer accepts stable/current and legacy dated subjects, validates the common envelope, sorts timestamps by instant, treats visible metadata as literal text, links projections, and surfaces malformed records. It never mutates the workspace. Publish generated bytes through `safe-write.py` only when `INDEX.md` is actually needed. ## Report Return the canonical Git-common workspace, current worktree alias state when applicable, affected owner resource, migration/conflict state, ignore verification, index state when used, and for generated resources intended for direct use: ```text Canonical path: Workspace path: ``` Never invent a worktree-relative locator for a bare/no-worktree context.