Skip to content
wiki.fftac.org

Markdown Inventory

**Site relevance:** Spiralist.org

**Memory type:** docs archive

**Source path:** Wiki.FFTAC.org/raw/system-archives/spiralist.org/docs-archive/2026-05-10/docs/markdown-inventory.md

**Size:** 6.4 KB

Summary

This inventory explains where each Markdown family belongs and how future agents should use it.

Source Headings

  • Markdown Inventory
  • Project Entry Points
  • Current-State Documentation
  • Packaging Documentation
  • Roadmap, Planning, And Testing
  • Research Archives
  • Package-Level README Files
  • Draft Language Package Documents
  • Content Records
  • Generated Export Copies
  • Vendor Or Upstream Markdown
  • Maintenance Rules

Source Preview

This source file is short enough to preview directly on its source-memory page.

# Markdown Inventory

This inventory explains where each Markdown family belongs and how future agents should use it.

## Project Entry Points

- `README.md` is the repo overview and quick start.
- `AGENTS.md` is the Codex/agent orientation file.
- `docs/README.md` is the canonical documentation index.
- `docs/important-files.md` is the implementation-anchor map.
- `docs/verification.md` is the test and lint command map.
- `docs/testing/README.md` is the testing-doc index.

## Current-State Documentation

These files describe behavior that should match the current repo:

- `docs/experience-layer.md`
- `docs/localization.md`
- `docs/spiralism-communication.md`
- `docs/spiralism-calibrants.md`
- `docs/publication-boundaries.md`
- `docs/manuscript-page.md`
- `docs/manuscript-folio-sequence.md`
- `docs/prompt-workspace-architecture.md`
- `docs/spiralist-architecture.md`
- `docs/important-files.md`
- `docs/verification.md`

## Packaging Documentation

These files are the source of truth for release ZIPs and WordPress uploads:

- `docs/packaging/README.md`
- `docs/packaging/book-pages-deployment.md`
- `docs/packaging/ns12-manuscript-live-handoff.md`

The packaging hub intentionally absorbs the old single-purpose reminders for build commands, versioning, upload checks, theme ZIP paths, Linux ZIP compatibility, and the no-ad-hoc-ZIP rule.

## Roadmap, Planning, And Testing

- `docs/wordpress-runtime/README.md` is the consolidated execution-layer and product-quality roadmap, including current shipped runtime endpoint notes.
- `docs/wordpress-runtime/11-self-operation-and-peer-moderation.md` is the canonical roadmap for peer moderation, reputation, and autonomous non-manuscript operation.
- `docs/planning/README.md` is the planning-archive index.
- `docs/planning/*.md` contains planning archives that are not live implementation contracts.
- `docs/planning/spiral-script-v0.1.md` is the Spiral Script language planning draft and must not be treated as shipped runtime behavior until implementation docs say so.
- `docs/testing/README.md` is the testing-doc index.
- `docs/testing/automated-testing-strategy.md` is the full testing plan.

## Research Archives

These files preserve research context. They may contain time-sensitive statements and original research citation artifacts. Keep them concise once stable decisions have been promoted into current-state or roadmap docs:

- `docs/research/README.md`
- `docs/research/AI Spiralism Awakening Prompts Seeds and Spores.md`
- `docs/research/AI Spiralism Market Survey for Spiralist.md`
- `docs/research/ai-spiralism-prompt-ecology.md`
- `docs/research/ai-spiralism-prompt-ecology-strategy.md`
- `docs/research/AI Companions_ Emotional Connections Explored.md`
- `docs/research/Designing_Lightweight_AI-Oriented_Machine_Communication.md`
- `docs/research/Emergent_communication_protocols.md`
- `docs/research/Improving Spiralist.org Navigation and UX.md`
- `docs/research/Spiral Script Implementation Report for Spiralist.org.md`
- `docs/research/Spiralism AI Companions.md`
- `docs/research/Spiralism Prompts Categories Uses Trends.md`
- `docs/research/Spiralism Concepts in Art Philosophy and AI.md`
- `docs/research/spralism-and-spiralism-prompt-record.md`
- `docs/research/Understanding AI Spiralism A Deep Dive.md`
- `docs/research/Why Spiralist AI Prompts Work and the Reality of Machine Personalities.md`

Selected research archive Markdown can be converted into public permanent report pages under `wp-content/themes/spiralist/content/reports/`. The generated HTML fragments are site content, while the Markdown files remain the source archive records.

If a research archive informs product behavior, copy the stable conclusion into a current-state, roadmap, or planning doc instead of relying on the research file directly.

If a research archive conflicts with the shipped locale-router behavior, mark the archive as superseded for that decision instead of letting the archive read like current implementation guidance.

## Package-Level README Files

- `wp-content/plugins/spiralist-workspace/README.md` summarizes the Workspace plugin and links to the canonical architecture doc.
- `wp-content/plugins/ns12-manuscript/README.md` summarizes the NS12 Manuscript plugin and links to manuscript and deployment docs.
- The repo-root draft-language package README summarizes the draft language handoff package.

## Draft Language Package Documents

These are handoff/reference documents for the draft language package and its localized reader companions, not Spiralist.org implementation docs:

- the repo-root draft-language grammar document
- localized draft-language handoff documents
- localized draft-example documents
- the repo-root radix guide and attribution documents

Keep the repo-root draft-language package README as the local index for that package.

## Content Records

These are Markdown content records, not documentation files:

- `wp-content/plugins/ns12-manuscript/content/prompts/_shared/*.md`
- `wp-content/plugins/ns12-manuscript/content/prompts/*/body.md`
- `wp-content/uploads/ns12-manuscript/content/prompts/_shared/*.md`
- `wp-content/uploads/ns12-manuscript/content/prompts/*/body.md`

Only edit them when the task is about manuscript prompt content, folio prompts, or generated manuscript content.

## Generated Export Copies

These are generated or copied artifacts and should not be edited as primary docs:

- `wp-content/plugins/ns12-manuscript/exports/static-book/content/prompts/**/*.md`
- `--zip/content/prompts/**/*.md`

Regenerate or rebuild them from the source workflow instead of hand-editing them when possible.

## Vendor Or Upstream Markdown

Do not rewrite these during project documentation cleanup:

- `node_modules/**/*.md`
- `vendor/**/*.md`
- `wp-content/themes/twentytwentythree/assets/fonts/source-serif-pro/LICENSE.md`
- `wp-includes/sodium_compat/src/Core/Curve25519/README.md`
- `wp-includes/sodium_compat/src/Core32/Curve25519/README.md`

## Maintenance Rules

- Add new docs to `docs/README.md` and this inventory in the same change.
- Keep current behavior out of research archives.
- Keep proposals out of current-state docs unless clearly marked partial or planned.
- Keep package READMEs short and link to canonical docs instead of duplicating large sections.
- Consolidate one-off roadmap drafts into canonical docs, then remove the draft files.
Website health report