managing-artifacts

You can keep generated reports and plans out of your code repository by using a centralized artifact storage workspace under ~/.local/spellbook, which applies project-encoded paths to organize documents while strictly forbidding writes to repository folders.

Centralized artifact storage is a dedicated directory structure outside of project repositories that organizes generated documents, audits, and reports using consistent project-encoded paths under ~/.local/spellbook to ensure quick retrieval and prevent artifact litter in source code.

You organize project audits and docs by applying a centralized directory structure with clear layout categories like docs, plans, audits, and reports under ~/.local/spellbook, using project-encoded path generation to uniquely identify artifacts per repository.

Yes, centralized artifact storage works for any software project requiring consistent paths and quick retrieval, applying a standardized directory structure that uniquely identifies artifacts per repository for easy onboarding, audits, and handoffs.

You should not write generated artifacts into project directories because it causes artifact litter, making repositories harder to navigate; centralizing them under a dedicated workspace ensures consistent paths, keeps repos clean, and enables quick retrieval during audits or handoffs.