Classification System

akm recognizes files through bundle adapters. Each adapter owns a bundle format and exposes a recognize() primitive that inspects a single file (path + frontmatter + content) and returns an IndexDocument — the item's subdir-qualified conceptId, type, renderer, and metadata — or null if the adapter does not claim the file. There is no longer a global matcher registry; the per-format adapter is the unit of recognition.

Built-in adapters

The registry is a static frozen list (BUILTIN_ADAPTERS in src/core/adapter/adapters/index.ts, exposed through src/core/adapter/registry.ts) — always populated at module load, no registration call required. Eleven built-ins, in probe order:

looksLikeRoot probes run most-specific-first in the list order above; the first match wins and the winner is recorded per component. A root matching no probe falls back to akm (see FALLBACK_ADAPTER_ID in src/indexer/installations.ts). generic-files never participates in probing.

Configured adapter ownership wins over probing. akm add records the detected adapter so later indexing does not reinterpret a bundle. The broad OKF probe also recognizes index-less typed Markdown, but strong AKM layout evidence runs first because AKM Markdown is an OKF-compatible superset.

See Bundle Types for the user-facing detail per adapter — conceptId/ref shape, what's indexed, validate() checks, and read/write status in 0.9.0.

Item types

type is an open descriptive string. The core accepts every non-empty value; the owning adapter decides whether a value receives specialized behavior. The akm adapter emits its fourteen defined native types (script, skill, command, agent, knowledge, instruction, workflow, memory, lesson, env, secret, fact, task, session) — see Bundle Types for the full purpose / agent-output table per type.

wiki is no longer an item type. Multi-page wikis are a bundle format owned by the llm-wiki adapter, not a per-file type stamped by the classifier.

Reserved structural files

index.md and log.md are reserved structural files for the akm, okf, and llm-wiki adapters. OKF defines their meaning in OKF bundles; AKM and LLM Wiki reserve the same names under their own format contracts. Other adapters own their reserved-name rules.

Adapter-owned filtering (AKM sensitive/infra abstention)

Each adapter decides which walked files it claims and which it abstains on — the core always excludes VCS internals and symlink escapes. An OKF walk includes ordinary dot directories and bin/ because those paths can identify conformant concepts; AKM keeps its existing cache/dot-directory hygiene. The akm adapter's recognize abstains (returns null) on its own bundle's non-content files, using path/stat checks only so the bytes of sensitive files are never read to make the decision:

• an env/… .env file that has a sibling .sensitive marker;
• anything under the frozen legacy vaults/ directory (the vault type was removed in 0.9.0);
• a secrets/ .sensitive/.lock marker, or a secret with a sibling <name>.sensitive marker;
• a wikis/<name>/ root-level infrastructure file (schema.md/index.md/log.md).

This policy previously lived in the indexer's shouldIndexStashFile pre-filter; it now lives in the adapter (akmStashAbstains in src/core/adapter/adapters/akm-adapter.ts), so each adapter owns its own bundle's filtering (owner ruling 2026-07-21).

The akm adapter's recognition signals

Inside the akm adapter, recognition picks a winner by specificity descending, ties broken by registration order (later wins). The signals:

Directory signals

• scripts/ → script
• skills/ → skill
• commands/ → command
• agents/ → agent
• knowledge/ → knowledge
• workflows/ → workflow
• memories/ → memory
• lessons/ → lesson
• env/ → env
• secrets/ → secret
• tasks/ → task

Markdown signals

Asset quality values

The quality field marks how an item was produced. Four values are well-known:

Unknown string values warn once at runtime and remain searchable.

Examples