wiki

Rendered from markdown source. Open raw source on GitHub.

Work Vault Index

This wiki is the structured index behind the public Attractor Gateway.

Use the front page to enter by meaning. Use this page to enter by route, project, concept, queue, or source layer.

Current status: the vault now contains substantive work artifacts, archived snapshots, standard-named source copies, and lineage pages. Use the wiki to track intake, duplicate collapse, source naming, and branch splits without inventing extra meaning.

Main Entrances

• Attractor Gateways
• Projects
• Concepts
• External Published / Shimmery Memory Essays
• AI Entry Surface
• Start Here for AI
• Search
• Graph
• Reader Paths
• AI Answer Contracts
• Status Vocabulary
• Artifacts
• Project Cross-Index
• Source Roles
• Artifact Types
• Maintenance Hub
• Timelines
• Unresolved
• Duplicate Review
• Missing Files
• Incoming Review

Corpus Orientation

• AI Context
• Search
• Graph
• Reader Paths
• AI Answer Contracts
• Status Vocabulary
• Canon Map
• Attractor Map
• Glossary
• Changelog

Intake Notes

• Add new source material under artifacts/incoming/, preserve inbound originals in artifacts/intake-archive/, and prefer artifacts/standard-named/ links when available.
• Use the review pages to track intake, duplicate collapse, source naming, and archival work.
• Use the generated source-role and artifact-type indexes when you want a cleaner cross-cut than the full artifact tree.
• Use the project cross-index when you want to move from family names into attractors, concepts, and essays quickly.
• Use the AI entry surface when you need a machine-facing order of operations or source-precedence summary.
• Use the search surface when you want a fast metadata-first route into the corpus.
• Use the maintenance hub when you want the current queue pressure in one place before drilling into individual review pages.
• Split out evidence-backed subpages with lineage labels when a branch stabilizes.
• Keep .zip companions auxiliary unless a page explicitly promotes them.
• Treat DOCX and PDF as witness/reference files and use Markdown wiki pages as the working semantic layer for extraction, linking, and later cleanup passes.