archeious/luminos
1
0
Fork 0
Code Issues 41 Pull requests Projects 1 Releases Packages Wiki Activity Actions

Compare commits

base: archeious:74477d8c2a48de888af10256b402f480a0f89257
Branches Tags
archeious:main
archeious:chore/issue-followups-session5
archeious:docs/issue-53-onboarding-internals
..
compare: archeious:8c0e29b6d862442f86a7b7e2bae0b3032e1816d6
Branches Tags
archeious:main
archeious:chore/issue-followups-session5
archeious:docs/issue-53-onboarding-internals

2 commits
74477d8c2a ... 8c0e29b6d8

Author SHA1 Message Date
Jeff Smith
8c0e29b6d8 merge: docs/issue-53-onboarding-internals (#53) 2026-04-06 23:21:44 -06:00
Jeff Smith
1892784d35 docs: add status snapshot to PLAN.md, fix domain.py file-map (#53) 2026-04-06 23:21:41 -06:00
1 changed files with 29 additions and 3 deletions
Show stats Expand all files Collapse all files

32
PLAN.md
View file

@ -1,5 +1,31 @@
# Luminos — Evolution Plan
> **Status snapshot (kept in sync with closed issues; for the canonical
> live view see [open issues](https://forgejo.labbity.unbiasedgeek.com/archeious/luminos/issues)
> and the wiki [Roadmap](https://forgejo.labbity.unbiasedgeek.com/archeious/luminos/wiki/Roadmap)).**
>
> | Phase | Status |
> |---|---|
> | 1 — Confidence tracking | ✅ shipped |
> | 2 — Survey pass | ✅ shipped |
> | 2.5 — Context budget reliability (#44) | ✅ shipped |
> | 3 — Investigation planning | ⏳ next |
> | 3.5 — MCP backend abstraction (#39) | planned |
> | 4 — External knowledge tools | planned |
> | 4.5 — Unit of analysis (#48) | planned |
> | 5 — Scale-tiered synthesis | planned |
> | 6 — Multi-level synthesis | planned |
> | 7 — Hypothesis-driven synthesis | planned |
> | 8 — Refinement pass | planned |
> | 9 — Dynamic report structure | planned |
>
> **Heads up on the File Map below:** the original plan called for a new
> `luminos_lib/domain.py` to host the survey/plan logic. In practice the
> survey pass landed inside `ai.py` (`_run_survey`, `_format_survey_block`,
> `_filter_dir_tools`) and `domain.py` was never created. Phase 3's
> planning pass will probably follow the same pattern unless `ai.py`
> grows large enough to justify a split.
## Core Philosophy
The current design is a **pipeline with AI steps**. Even though it uses an
@ -636,9 +662,9 @@ architecture. The migration pain is intentional and instructive.
| File | Changes |
|---|---|
| `luminos_lib/domain.py` | **new** — survey pass, plan pass, profile-free detection |
| `luminos_lib/prompts.py` | survey prompt, planning prompt, refinement prompt, updated dir/synthesis prompts |
| `luminos_lib/ai.py` | survey, planning, external tools, tiered synthesis, multi-level grouping, refinement, confidence-aware cache writes |
| ~~`luminos_lib/domain.py`~~ | ~~new — survey pass, plan pass~~ — **never created**; survey logic landed in `ai.py` instead |
| `luminos_lib/prompts.py` | survey prompt ✅, planning prompt, refinement prompt, updated dir/synthesis prompts |
| `luminos_lib/ai.py` | survey ✅, planning, external tools, tiered synthesis, multi-level grouping, refinement, confidence-aware cache writes |
| `luminos_lib/cache.py` | confidence fields in schemas, low-confidence query |
| `luminos_lib/report.py` | dynamic field rendering, domain-appropriate sections |
| `luminos.py` | --refine, --no-external, --refine-depth flags; wire survey into scan |