MDX artifacts
Classify an artifact before choosing its path.
| Class | Location |
|---|---|
| Persistent research, review, or audit | ~/.mdx/research/ |
| Persistent architecture, design, specification, or plan | ~/.mdx/design/ |
| Persistent decision | ~/.mdx/decisions/ |
| Persistent session trail or handoff | ~/.mdx/sessions/ |
| Persistent project status or working knowledge | ~/.mdx/projects/ |
| Temporary worker or candidate material | ~/.mdx/TMP/pstack/<session>/ |
| Reproducible command output or transfer file | /tmp |
| Repository deliverable | A repository path only when the user asks or the repository already owns it |
Never keep the only copy of a genuine artifact in /tmp.
For persistent Markdown:
- Read
~/.mdx/_schema.mdbefore writing. - Use its category, frontmatter, filename, and versioning rules.
- Verify the final file exists and is readable.
- Refresh the Markdown index when the
md_indextool is available. - Return the absolute path.
For delegation, give each worker an exact artifact class and output path. Keep scratch separate from the final persistent artifact.