Operating Flow — Android
First-class Android client — not a companion. Every capability from web is available in your pocket: chat, calls, meetings with AI summaries, task triage, ask-anything. Optimized for one-handed use, glanceable, ambient.
Onboarding & auth
Everything you build.
conversation.
Home & inbox
@Opus in #askshiva-memory
Rahul mentioned you: "please review the memory refactor PR"
- SULTAN eval is 2 days ahead of curve — v0.7 could ship Friday.
- Aventra contract still pending signature — nudge them today.
- Dev is overloaded — 6 open tasks across 3 projects.
Communication
Meetings & calls
Decided to gate rerank below top-3, delay pgvector to dedicated-store migration until 10M vectors, and add owner_type to embeddings now to prepare for per-user memory shadows.
Rahul argued the RagService interface makes future migration cheap; Priya confirmed evals show rerank hurts below top-3. Opus locked owner_type tagging as non-negotiable for shadow readiness.
Recent thread: memory rerank fix. Rahul agreed to push refactor tonight; likely wants sign-off on org_config.rerank_threshold gate.
Execution
Gate rerank behind org_config.rerank_threshold
Introduce an org_config.rerank_threshold knob so the reranker only runs above N hits. Priya's eval shows recall@10 moves 61 → 74% when we skip rerank on <3 hits. Ship gated, add to eval baseline.
Adding eval baseline PR now — should be ready before you start.
Cool. I'll wire the flag through RagService and land the PR today.
What if every project had a living "genome" — mission, arch, contributors, decisions, risks — that updates itself from graph state?
Love it. A tree layout on desktop, tabbed on mobile. Genome should include a "what would break this project" section.
Materialize it from decision events + task events. Read-through cache, invalidate on any node write in the project subgraph.
Synthesizing: 3 threads converge on a "self-writing project brief". Nearest neighbor: Living Docs Updater (v5 prompt, 340 calls). Suggest promoting to spec.
Add an "unresolved contradictions" section — every project probably has 2-3 lurking ones we forget about.
AI
You rejected the vector-store migration in today's architecture review. Rahul argued pgvector's operational simplicity beats marginal latency wins under 10M rows. Revisit when a rerank benchmark exceeds the current bge baseline.
- •Contract signed yesterday. $84k, 12-week engagement.
- •Their CTO Anaya cares about audit trail — flag GodEngine gate.
- •NDA revisions still open — do not commit to timelines yet.
- 1.Which model — SULTAN v0.7 vs AskShiva runtime for their pilot?
- 2.Onboard Rahul or Arjun as their engineering point of contact?
You & settings
confidential room