system-scribe

Generate documentation for Super Cartola business rules by consulting the repository source code via gemini_audit.py or Read/Grep fallbacks, producing structured didactic explanations with rules, exceptions, examples, and related files.

The best way to explain internal calculations and financial flows is to ground explanations directly in repository source code, generating structured documentation that covers rules, exceptions, and practical examples for onboarding.

Yes, the documentation workflow works without gemini_audit.py by falling back to standard Read and Grep tools to search and consult the repository source code for accurate feature explanations.

Yes, you can document feature logic for any repository module by asking for explanations of specific system parts, which triggers a code-grounded search to produce structured wiki-style documentation of internal behavior.

Code-grounded analysis prevents hallucinations by reading actual repository source code to verify ranking rules, ensuring your documentation reflects real implementation logic including specific exceptions and calculations.

Using read and grep fallbacks for wiki generation limits deep automated analysis compared to a dedicated audit script, requiring manual search pattern construction to accurately trace complex module dependencies and business rules.