repowiserepowise
Sign in
techygarg/lattice
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowisetechygarg/lattice
LA
LA

techygarg / lattice

markdownmaine5a5a7318.2K linessynced 1mo ago

Code health

10.0out of 10Excellent

This codebase scores 10.0 out of 10 on defect risk, which we rate excellent. It also scores maintainability 10.0 and static performance risk 10.0 out of 10. The three are scored separately and never blended into one number.

Full health report →
Lines of code
18.2K
Files
129
Symbols
0
Modules
74
Languages
5

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • Prefer collaborative-judgment over single-pass generationproposed
  • Use collaborative-judgment to prevent silent layer-placement assumptionsproposed
  • Session lifecycle for molecules includes shared context/learning stepsproposed
  • Standardization via refiners or direct editing of .lattice/standards/proposed
  • Language idioms precedence for pseudocode adaptationproposed
  • Use overlay as default customization modeproposed

Needs attention

52 open
  • medium severity. ProposedPrefer collaborative-judgment over single-pass generationAuto-proposed decision awaiting review
  • medium severity. ProposedUse collaborative-judgment to prevent silent layer-placement assumptionsAuto-proposed decision awaiting review
  • medium severity. ProposedSession lifecycle for molecules includes shared context/learning stepsAuto-proposed decision awaiting review
  • medium severity. ProposedStandardization via refiners or direct editing of `.lattice/standards/`Auto-proposed decision awaiting review
  • medium severity. ProposedLanguage idioms precedence for pseudocode adaptationAuto-proposed decision awaiting review

Composition

Open the graph →
markdown 89%json 5%yaml 4%shell 2%toml 1%

Explore this codebase

  • Docs0 pages across 74 modules→
  • ChatAsk this codebase a question and get an answer with its sources→
  • Files129 files with per-file docs, health and history→
  • ArchitectureDependency graph, layers, and 0 entry points→
  • Code healthPer-file scores, 0 open findings, coverage and refactoring targets→
  • Knowledge graphEntities, communities, and the paths between them→
  • Change couplingFiles that keep changing together, mined from commit history→
  • CommitsChange-risk ranked history with agent provenance→
  • ContributorsBus factor, per-file maintainers, and the human/agent split→
  • StatsSize class, origin, lifetime churn, rhythm and records→
  • CostsWhat indexing this snapshot cost, by model and by run→