01
Context-transfer problem
A new model context can begin with little or no working knowledge of a large repository. Reconstructing file structure, routes, dependencies, tests, configuration, Git state, and related project information repeatedly consumes reasoning capacity before the actual software problem can be addressed.
02
What Snapshot transfers
Snapshot v10 can package Git state, file inventory and hashes, routes, imports and dependencies, tests, parse results, environment and configuration structure, documentation summaries, CI/CD information, and other repository context into a structured artifact. Sensitive values are redacted rather than intentionally transferred.
03
What it does not replace
Snapshot does not prove model understanding, replace direct repository inspection, or itself encode architectural ownership and invariants. Its role is narrower: increase the amount of real project state available when work begins so less of that state has to be rediscovered from zero.
Evidence boundary
What this entry supports
The public site presents a real Snapshot v10 execution against Ajenda and a reviewed public-safe excerpt of structured output. The design objective is comprehensive project context; full cognitive understanding is not asserted as a measured outcome.
Related material