⌁Code ArchaeologistIntelligence Console
● DEMO MODENemotron routing online
Repository intelligence · Token Factory aware

Excavate the story inside your codebase.

Move from a flat scan to an explainable map of what to preserve, what has fossilized, and what needs a careful rebuild.

1 Tree-sitter parse→2 Nano triage→3 Ultra reasoning
Who is this for?New engineersTech leadsLegacy-code teams

Bring a codebase to the dig site

Fixture: test_project · credential-free
Files
2
parsed
Lines
193
of source
Artifacts
4
preserve these
Strata
5
architecture layers
Fossils / Ruins
15 / 3
risk signals
Health score
67
medium risk

Fast health assessment

Nano · 842ms · 1,284 tokens
67/ 100
  • God class: UserService
  • Unused public methods
  • No automated tests
  • Service layer has 78% of business logic
Critical 1High 5Medium 9Low 4

Smart routing log

Smart routing vs Ultra-only$0.42 saved

Stratigraphy cross-section

The signature dig-site view: depth maps to architectural responsibility, stability, and coupling.

Actions

Ultra ready
README health badge
[![Code Archaeologist Health](https://img.shields.io/badge/health-67%2F100-medium-yellow)]

Artifacts worth preserving

Patterns, idioms, and conventions the team should not accidentally delete.

Architecture strata

Super · 1.8s · 4,620 tokens

How to read the site

Deeper layers are closer to the foundation. A high coupling score signals that a change here will ripple through the site; a high cohesion score means the layer has a clear responsibility.

  • Green edge: stable foundation
  • Amber edge: core business logic
  • Red edge: feature pressure
  • Blue edge: integration boundary
Cross-section insight
Presentation currently reaches directly into Core. Introduce an application service seam before the next feature cycle.

Fossils

Dead code and stale interfaces with an estimated age.

Ruins

Technical debt that threatens stability or slows delivery.

Architecture forecast

Ultra · 4.6s · 8,910 tokens

Next best moves

  • Extract UserRepository from UserService
  • Put contract tests around the API boundary
  • Delete or quarantine legacy_function
  • Introduce dependency inversion for integrations

The site is ready to explain any finding in Ultra mode.

Excavating repository…

Parsing with tree-sitter
Nano scan
Ultra reasoning