Codebase archaeologist — reverse-engineering an unknown system
Architecture, dependency map and impact analysis from a foreign codebase — and it never presents inference as fact.
What is inside
Build a system that reverse-engineers unfamiliar codebases and reconstructs how the software ACTUALLY works. Input: repository - configuration - database schema - API definitions - logs - runtime traces. Output: architecture map - dependency graph - symbol graph - service map - database dependencies - API map - technical debt - risk map - change impact. Documentation is frequen…
- Input and output
- The central rule
- Roles
- Processing
- Error handling
- Security
- Performance
- Execution rule
The full content (1603 characters) becomes available after purchase.
Example
Reviews
No reviews yet.
Related products
Digital operating system — the top layerUnifies agents, skills, tools, memory, workflows, knowledge, policy, identity and evaluation.Agent marketplace — permissions before conveniencePublishing, validating, evaluating, installing, versioning and safely running agents and skills.Data engineering command centre — before the business noticesPipelines, schemas, lineage, quality and anomalies in one system — data failures are silent.Knowledge graph platform — graph and vectors togetherTemporal, provenance-aware knowledge: vector search alone cannot represent relationships.