Source code as a source of truth directs developers and agents to inspect the current repository rather than relying on detached summaries of what the system supposedly does. Code, schemas, tests, build configuration, and version history provide direct evidence of the implemented state.
Source code does not explain every intention, so concise documentation remains useful for policy, architecture, and requirements that cannot be inferred safely. The goal is to avoid duplicating rapidly changing implementation details in a separate memory store that can drift without detection.
Acronyms and aliases
code as ground truth synonymsource code ground truth variant
Related terms
Frequently asked questions
Does source code contain every project requirement?
No. Product intent, safety rules, permissions, and future requirements may need documentation, but implementation claims should be checked against current code.
Why should a coding agent inspect source code directly?
Direct inspection reflects the current implementation and reduces the risk of acting on an outdated summary or remembered plan.
