Analyse memory and context

Type: types/instruction.md

Give reconciliation a source-grounded account of the included memory mechanisms, their retained results, later consumers and unresolved integration questions.

Treat runtime as a provisional account: it orders this job but is not an inspection limit, and the epistemic analyst works separately.

Analyse mechanisms and integration

Cover every included part along the record contract's coverage dimensions, not only a primary store or the best-understood route. Choose the memory scope from runtime routes and state inclusions and exclusions.

Check frozen CLI dispatch, hooks, registered tools and exposed library or service operations against its routes. Trace evaluation, cleanup, rejection and withdrawal through retained results to later consumers. Challenge strong source claims, misleading labels and partial ontology mappings. A thin memory boundary warrants short sections with explicit limits. Do not compare systems or recommend Commonplace adoption.