Skip to guide content
Morten A. Giraffe
Agent Activation Guide

03 / Load the right authority

Inspect the Product Before Applying the Guide

The Journal explains principles and working patterns; the repository reveals the actual stack, routes, components, tokens, constraints, tests, and working behavior that must be preserved.

Technical diagram for Inspect the Product Before Applying the Guide.

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

Read only the files that establish the active surface and its dependencies before recommending a redesign or architectural change.

Field test

Has the agent inspected the relevant repository instructions, implementation, design authority, tests, and current state? Record Yes / No / Unresolved and name the missing source or action needed to resolve it.

Ask your agent

Begin read-only. Inspect applicable instruction files, package/runtime configuration, routes, current components, data flow, DESIGN/design.md, tests, and recent state before proposing changes. Name what you actually read.

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.

Verification