Context Cabinet

The foundational Dotabase holding every captured file and document — raw, searchable, and the default destination for anything with no better home. Rows are CTX-N; it is usually just called "the Cabinet".

The Cabinet exists so capture never blocks on a routing decision. When the DIIICER router cannot resolve a specific destination for an incoming item, the Cabinet is the declared fallback — material lands somewhere searchable rather than being dropped or held.

Usage examples

• "Every file and document — raw, searchable, and the default home for …" (the Dotabase's own description)
• "Route resolution order is: explicit target → create-new → pinned rule → auto-route by fit → Cabinet fallback."
• "dots cabinet list / dots cabinet detail CTX-3"

Source

SPEC-142 (DS_Context-Cabinet); the fallback role at SPEC-249 § 1.1; the live Dotabase description (slug context-cabinet) and the dots cabinet command family.