repowiserepowise
Sign in
d-o-hub/chaotic_semantic_memory
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowised-o-hub/chaotic_semantic_memory
CH
CH

d-o-hub / chaotic_semantic_memory

markdownmain87d6ca4101.1K linessynced 13h ago

Code health

8.1out of 10Excellent

This codebase scores 8.1 out of 10 on defect risk, which we rate excellent. It also scores maintainability 9.1 and static performance risk 10.0 out of 10. The three are scored separately and never blended into one number. The files you change most are the weak spot: 87 of 805 files are git hotspots, and they average 5.0.

Full health report →
Documentation551pages0 with model-written prose, 551 built from the indexScore validation17/203.15× baselineOf the 20 lowest-health files, 17 were bug-fixed in the last 6 months — 3.15× the 27% baseline
Lines of code
101.1K
Files
805
Symbols
4,734
Modules
143
Languages
10

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • feat(api): add Phase 33 API completeness methodsproposed · 13h ago
  • fix(safety): eliminate unwrap() and semaphore deadlock in production codeproposed · 13h ago
  • perf(retrieval): reduce MMR reranking complexity to O(K * N)proposed · 13h ago
  • perf(retrieval): optimize score normalization loops (avoid f32::min/max)proposed · 13h ago
  • perf(retrieval): optimize GraphRAG retrieval performanceproposed · 13h ago
  • fix(bm25): use 1e-6 tolerance in test assertionsproposed · 13h ago

Needs attention

80 open
  • medium severity. Proposedfeat(api): add Phase 33 API completeness methodsAuto-proposed decision awaiting review
  • medium severity. Proposedfix(safety): eliminate unwrap() and semaphore deadlock in production codeAuto-proposed decision awaiting review
  • medium severity. Proposedperf(retrieval): reduce MMR reranking complexity to O(K * N)Auto-proposed decision awaiting review
  • medium severity. Proposedperf(retrieval): optimize score normalization loops (avoid f32::min/max)Auto-proposed decision awaiting review
  • medium severity. Proposedperf(retrieval): optimize GraphRAG retrieval performanceAuto-proposed decision awaiting review

Where the risk concentrates

All 87 hotspots →

Ranked by prior bug fixes and change frequency, mined from full git history rather than from the code alone.

FileChurnPrior fixesMaintainersCommits 90d
bm25.rssrc/retrieval99.8th8bug magnet337
hybrid.rssrc/retrieval99.5th3228
framework.rssrc99.3th16bug magnet333
framework_ops.rssrc99.0th16bug magnet328
singularity.rssrc98.8th10bug magnet2bus factor 115

Composition

Open the graph →
markdown 43%rust 41%shell 9%toml 3%yaml 2%Other 2%

Explore this codebase

  • Docs551 pages across 143 modules→
  • ChatAsk this codebase a question and get an answer with its sources→
  • Files805 files with per-file docs, health and history→
  • ArchitectureDependency graph, layers, and 17 entry points→
  • Code healthPer-file scores, 1,676 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→