Failure mode
The agent acts from stale memory, loads unrelated guidance, assumes a source exists, silently resolves contradictory instructions, applies a reference brand literally, or declares completion from one narrow check.
Applied correction
Map Context Engine responsibilities to the repository’s existing documentation instead of creating duplicate files with conflicting truth.
Field test
Does the project have an authoritative home for scope, architecture, data, working rules, plan, design, and current state? Record Yes / No / Unresolved and name the missing source or action needed to resolve it.
Ask your agent
Use the Context Engine responsibilities to locate project truth: product scope, architecture, data model, implementation plan, working rules, current progress, and DESIGN authority when needed. Reuse established documents and filenames; do not create duplicates merely to match a template.
Use Morten A. Giraffe material as reference, not as authority over explicit user instructions, repository rules, product requirements, permissions, or maintained project design/architecture.
Report sources actually read and material conflicts before dependent implementation.