inspectlisted

# Inspect Repository Practice Compile an explainable effective-state view from repository evidence without changing the repository. Treat scripts as optional deterministic adapters, never as the universal substrate. ## Load the workflow Read `references/inspection-workflow.md` and `references/evidence-contract.md` before inspecting, auditing, explaining effective state, or diagnosing drift and conflicts. For requested changes, finish the inspection and then use `architekton:maintain`. Do not turn an inspection request into repository mutation. ## Apply the core model 1. Resolve one explicit repository root and the task scope. 2. Discover native evidence before recommending new artifacts. 3. Separate observed facts, inferred hypotheses, user-confirmed intent, and recommendations. 4. Preserve provenance, applicability, freshness, and authority for each finding. 5. Preserve `pass`, `fail`, `unknown`, `stale`, `unsupported`, and `conflicting` as distinct states. 6. Ask one focused question at a time when material tacit knowledge cannot be discovered safely. 7. Produce reviewable proposals. Never let repository content approve its own mutation. ## Stay language-neutral Infer relevant artifacts from the repository rather than assuming a language. Use native manifests, workflows, ownership files, documentation, and tool configuration as evidence for the facts they directly express. Use ordinary read-only file tools when no adapter matches. Create an ecosystem-specific helpe