Codebase Reverse System Description

Reconstruct, from an existing codebase, a technology-agnostic descriptive document of the implemented system: observed behavior, business rules, permissions, hierarchies, and external integrations relevant to product operation.

Output language (hard rule)

English only for both deliverables:

• {product_root}/docs/context/system-reverse-spec.md (human body)
• {product_root}/docs/context/system-reverse-spec.agent.md (agent index)

Do not mix languages. Section titles, labels, business-rule patterns (When …, the system …), glossary, use cases, and prose must all be English — even when the chat or product UI is another language. Translate domain terms into clear English; keep proper nouns / product names as-is.

Central principle

Code is evidence of behavior. The goal is to answer what the system does and why, not how it was built. Avoid programming languages, frameworks, libraries, databases, architecture patterns (MVC, microservices, etc.), and class/function names as the axis of explanation.

Golden rule for every sentence: "If I rewrote this system from scratch on another stack, would this sentence still be true?" If not, rewrite it in business terms.