Files

T

retoor af080fe68e Strict goal verification, approval hardening, retrieval eval, work limits, sandbox caps (1.38.0)

- Approval: re-prompt unknown answers (max 3), shell-only affirmative
  guidance recovery; destructive actions stay strict
- GoalVerifier subagent with strict JSON verdicts, bounded follow-up
  rounds, nonzero exit plus open turn on unverified one-shots
- Retrieval eval (Hit@K/MRR/nDCG/Context Precision), FTS cascade with
  title weighting, query/read event logging, --eval-retrieval CLI
- Supervisor caps (8 parallel, 64 records) and scheduler hardening
  (4 fires/tick, per-schedule lease, stated misfire policy)
- Sandbox box resource trio: 2g/2.0/256 at create, best-effort
  update for existing boxes, rm -f recovery pointer
- Research archive: 12 subjects, 667 sources, 27 conclusions;
  suites 979 + 16 green

2026-10-18 12:13:24 +02:00

1.0 KiB

Raw Blame History

pg-raggraph: RAG first, graph second

Metadata

Field	Value
Institute	Molodetz Institute — Research & Retrieval Division
Subject	prompt-context-scaling
Document type	Source Citation Card
Tier	2
Source title	pg-raggraph: RAG first, graph second
Source URL	https://github.com/yonk-labs/pg-raggraph
Source type	repository
Date researched	2026-10-18
Researched by	tai (agent), model: Muse Spark, on behalf of retoor
Research method	Search aggregator result listing (not independently opened or quoted)
Confidence	Not independently verified
Status	Active

Why it's here

Surfaced by the GraphRAG comparison search; the snippet states the graph as enhancer design (vector plus BM25 first, one-hop traversal only to rerank or expand weak retrieval). That ordering is what tai's search-plus-expand already does; seen only as a snippet.

Changelog

Date	Change
2026-10-18	Logged as consulted-but-not-analyzed.

1.0 KiB Raw Blame History

pg-raggraph: RAG first, graph second

Metadata

Why it's here

Changelog

1.0 KiB

Raw Blame History