Caching & freshness · Verify

Cache Coherency Check

Verify one cache coherency invariant through bounded write/read/invalidation/permission scenarios without broadening into performance tuning or unrelated refactors.

Vibe Coding 1.3.0 · vibe-cache · English technical instructions

← Back to search

Use this workflow

Use this workflow in Codex or Claude Code with the free Vibe Coding plugin. Choose your assistant and prompt language, then add your task details after the prompt.

Prompt

Use $vibe-cache, workflow “Cache Coherency Check” (ID: cache-coherency-check). Follow this workflow for the task below. Report the result in English.

Install the plugin

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

Verify one cache coherency invariant through bounded write/read/invalidation/permission scenarios without broadening into performance tuning or unrelated refactors.

Required input

Provide selected data/resource, expected freshness and authorization behavior, implementation summary or patch boundary, safe environment, fixtures, and repository-native commands.

Scenarios

Populate cache, update authoritative data, and verify invalidation or TTL behavior.
Exercise stale read and recovery behavior.
Verify tenant/identity/role/plan/locale cache key separation where relevant.
Exercise concurrent writes, optimistic updates, rollback, or background refresh only when part of the selected boundary.

Workflow ID: cache-coherency-check · View the versioned source · Shared workflow and authority rules