Map Staleness Check

Operation

Verify the selected invariant through bounded scenarios in an authorized environment. Do not turn verification into unrelated implementation. Return passed, failed or blocked, with actual evidence and any missing required scenario.

Goal

Determine whether repository maps are stale after a patch, branch delta, migration, documentation sync, or requested scope change. Return the smallest required map-refresh contour without changing product code, tests, configs, generated artifacts, docs, or map files.

Patch or scope input

Use an explicit diff, PR/commit range, changed-file list, or user-supplied scope. If no target is visible, inspect the current working tree. If there is no changed surface or requested map boundary, return a blocked/no-op verdict.

Map family contour

Map changed files to map families:

• Product/docs/requirements/capabilities/journeys/analytics/copy → Product Requirements Map, Product Capability Map, Product Journey Map, Product Metrics Events Map, Traceability Map, Risk & Release Map.
• Web/SaaS routes/layouts/forms/tables/navigation/UI states → SaaS Navigation Map, Product Journey Map, Auth Entitlements Map, Test Coverage Map.
• Bot commands/handlers/FSM states/keyboards/deep links/proactive messages → Bot Navigation Map, Runtime Flow Map, Auth Entitlements Map, Test Coverage Map.
• Routes/API/schemas/webhooks/generated clients → API Navigation Map, Integration Map, Traceability Map, Test Coverage Map.
• AI prompts/model calls/tool schemas/RAG/OCR/ML/evals/provider config → AI Navigation Map, Integration Map, Runtime Flow Map, Test Coverage Map.
• Entities/migrations/ORM/indexes/retention/PII → Domain Data Map, Ownership & Invariant Map, Test Coverage Map.
• Auth/RBAC/ABAC/tenancy/plans/quotas/feature gates → Auth Entitlements Map, RBAC ABAC Policy Map, Ownership & Invariant Map, Traceability Map.
• Workers/events/queues/workflows/realtime/cache/search → Runtime Flow Map, relevant domain maps, Test Coverage Map.
• External providers/SDKs/webhooks/credentials/rate limits → Integration Map, Runtime Flow Map, Risk & Release Map.
• Config/deploy/flags/migrations/runbooks → Risk & Release Map and relevant runtime/integration maps.

Check rules

• Do not force maps into repositories that do not use them.
• Do not edit files. This prompt is verification-only.
• Treat maps as evidence indexes, not authority. A stale map is a follow-up gate, not proof of implementation correctness.
• Verify risky or contradictory map claims against current owner evidence before declaring a map clean.
• Preserve role boundaries: do not perform a new domain audit, do not generate implementation tasks, and do not review the whole repository outside the changed contour.
• When map staleness is clear, name the exact map-skill or Map Refresh Polish path that should update it.
• If current evidence is insufficient, return blocked with the missing evidence or required owner decision.