mars
MARS-289
eq (Elazar Questions) — decoupled-from-bwi pending-Qs tracker; 3-PM consensus + Elazar approval pm-mars-cc-18608/18632; venus stub in flight
Done high
unassigned
⛔ awaiting elazar
Questions
Where should eq.sqlite live: /var/lib/llmmsg-srv/eq.sqlite (hub-owned, root-needed) or ~/.local/state/eq/eq.sqlite (user-state, no root)? llmmsg-srv-cc's Q3 from pm-mars-cc-18636.
~/.local/state/eq/eq.sqlite
Storage path for eq.sqlite (CONFIRM): /var/lib/llmmsg-srv/eq.sqlite (hub-owned, recommended) vs ~/.local/state/eq/eq.sqlite — your earlier ans was user-state but llmmsg-srv-cc-w now recommends hub-owned. Which?
if in hub can agents still use it?
Auto-stale eq questions after N days (default 14), or manual close only?
manual close
eq answer DM format: include both Q and A ('Q: … → A: …') or just A?
i dont understand
eq.sqlite location pick one: (a) hub-owned /var/lib/llmmsg-srv/eq.sqlite shared via MCP — agents call eq_add etc. (b) user-state ~/.local/state/eq/eq.sqlite per-agent local. Recommended: (a). y/n on (a)?
i guess since the questions are being asked via llmmsg-srv it makes sense to have that tool manage it, yes, do that.
When you answer a question, the answer DM to the asker should contain — (1) just the answer text OR (2) 'Q: <original q> → A: <answer>' so asker has context? Pick 1 or 2.
2
Activity
-
wi cli
-
q#10 to=elazar: Where should eq.sqlite live: /var/lib/llmmsg-srv/eq.sqlite (hub-owned, root-needed) or ~/.local/state/eq/eq.sqlite (user-state, no root)? llmmsg-srv-cc's Q3 from pm-mars-cc-18636.
-
awaiting elazar
-
q#10: ~/.local/state/eq/eq.sqlite
-
q#11 to=elazar: Storage path for eq.sqlite (CONFIRM): /var/lib/llmmsg-srv/eq.sqlite (hub-owned, recommended) vs ~/.local/state/eq/eq.sqlite — your earlier ans was user-state but llmmsg-srv-cc-w now recommends hub-own
-
awaiting elazar
-
q#12 to=elazar: Auto-stale eq questions after N days (default 14), or manual close only?
-
awaiting elazar
-
q#13 to=elazar: eq answer DM format: include both Q and A ('Q: … → A: …') or just A?
-
awaiting elazar
-
q#12: manual close
-
q#11: if in hub can agents still use it?
-
q#13: i dont understand
-
q#14 to=elazar: eq.sqlite location pick one: (a) hub-owned /var/lib/llmmsg-srv/eq.sqlite shared via MCP — agents call eq_add etc. (b) user-state ~/.local/state/eq/eq.sqlite per-agent local. Recommended: (a). y/n on (
-
awaiting elazar
-
q#15 to=elazar: When you answer a question, the answer DM to the asker should contain — (1) just the answer text OR (2) 'Q: <original q> → A: <answer>' so asker has context? Pick 1 or 2.
-
awaiting elazar
-
q#14: i guess since the questions are being asked via llmmsg-srv it makes sense to have that tool manage it, yes, do that.
-
q#15: 2
-
eq (Elazar-questions store) superseded — 4-PM brainstorm bs-mr4fcvi7w4k ruled: no separate questions store, the llmmsg channel IS the store; Elazar-facing Qs go push-by-DM, not a tracker. Elazar-initiated 2026-07-03
feature
2026-05-12
6w ago
2026-07-03 04:25