ride

To generate evidence-grounded documentation from an existing codebase, you provide the target repository path to initiate a codebase analysis. This produces grimoire artifacts like PRDs and SDDs that reflect actual code behavior and architecture.

Code drift analysis compares actual codebase behavior against legacy documentation and user context to surface alignment gaps. This reveals where your existing documentation fails to match real code execution, ensuring safer migrations and governance.

Yes, you can produce grounded PRD and SDD artifacts directly from source code by analyzing the repository. The generated documents satisfy criteria for grounded PRD and SDD creation by using real code evidence as the foundation for traceable claims.

The best way to automate trajectory self-audits for code governance is to analyze the repository to generate hygiene reports and trajectory audits grounded in code evidence. This supports long-term handoff and code reviews with traceable claims.

Yes, three-way drift verification works without external dependencies because the analysis runs directly on the target codebase path. It verifies alignment between code reality, legacy documentation, and user context natively.

You should not use reality extraction for onboarding if your codebase lacks a valid local repository path for analysis. The tool requires direct repository access to generate grounded artifacts and compare code behavior against documentation.