Context and trend baseline
Saved project context, milestones, health history, risk lineage, official snapshots, and deterministic project selection.
A lightweight product/engineering map for the /project-update-test workflow. The aim is to keep useful future ideas visible without pretending they are all urgent.
Saved project context, milestones, health history, risk lineage, official snapshots, and deterministic project selection.
Manual/background knowledge, approved-report ingestion hooks, MiniLM embeddings, semantic/keyword retrieval, queue status, and backfill tooling.
Retrieved knowledge is available to the analyser as supplemental context, never as transcript evidence. Semantic milestone and risk matching are now in place.
A scoped Ask endpoint and UI can retrieve relevant project memory, with retrieval-only fallback when generation is unavailable.
Build a small set of repeatable project-update cases so we can measure quality instead of relying on one-off smoke tests.
Document the moving parts so the system is easier to run and safer to change later.
The generated mode exists, but live validation should use disposable fake memory first so real project memory is not sent externally just for testing.
Not needed yet. Keep official/manual/background knowledge indefinitely, keep real approved-report memory for now, and clean up test junk aggressively. Revisit auto-compaction only if retrieval becomes noisy or the knowledge store grows enough to need lifecycle management.