classify-doc

Classify Doc

$classify-doc owns the structural lifecycle of existing Living Entity Wiki-classified non-ADR documents under docs/.

Use it when a document:

• is unclassified or misplaced;
• belongs in a different document class;
• needs relocation because its purpose changed;
• needs its entity or platform- prefix corrected;
• is surfaced by $wiki-lint as structurally misclassified.

For a new classified document, use $to-doc.

For an ADR, use $to-adr-doc.

1. Confirm Scope

The file must already exist, must not be an ADR, and must be inside the Living Entity Wiki document universe after docs/.wikiignore is applied.

If it is under docs/adr/, use $to-adr-doc.

If new content is being created, use $to-doc.

If its path is matched by docs/.wikiignore, it is outside this skill's ownership; use the workflow or repository owner responsible for that documentation tree.

2. Respect the Wiki Exclusion Boundary

Read docs/.wikiignore when present and apply only the exclusion grammar defined by wiki/_schema.md.

If the current path is explicitly excluded:

• do not classify, move, or rename it under this skill;
• do not apply Living Entity Wiki prefix rules;
• follow the workflow or repository owner responsible for that documentation tree.

Do not infer exclusions for unfamiliar directories. If a project-owned path is not excluded and does not satisfy a normal document class, treat it as unclassified rather than inventing a new .wikiignore entry.

3. Determine Current and Target Classification

Derive the current class from the document's location.

Apply the target-class rules in wiki/_schema.md to the document's current content and purpose, not merely its existing folder.

Possible project-owned classes are:

current
proposed
research
reference
process

An existing loose or unrecognized document may be unclassified.

Do not use or introduce:

doc_class:
Doc-Class:

If current vs proposed is genuinely ambiguous, follow the schema fail-safe and use proposed.