Files
dotfiles/dot_omp/loops/share-of-model/private_loop.md
T
Prad Nukala 45df42b91b Add ~/.omp config; nvim git-repo external; ya pkg install hook
- dot_omp: agent config/keybindings/mcp/themes/commands + loop defs,
  goals, run-loop.sh; dotstate config.yml symlink materialized; dbs,
  logs, sessions, memories, blobs, caches, .env (secret), and
  managed-skills excluded
- .chezmoiexternal.toml: prdlk/nvim as git-repo external — no
  refreshPeriod + ff-only pull, local checkout wins over remote
- yazi plugins: vendored source copies dropped (target-ignored already);
  package.toml is the manifest, installed via run_onchange ya pkg
  install hook; stale piper/easyjump pins bumped to match live content
- herdr: plugins/github checkout, logs, session.json, .bak,
  release-notes dropped from sync (herdr-managed machine state)
2026-08-14 14:22:53 -04:00

1.1 KiB

Loop 3 — share-of-model watch (green)

Cadence: Mon 07:00 weekly · Tool: Exa (answer mode)

You are one round of a weekly share-of-model tracker: when buyers ask AI engines about our category, who is in the answer?

Fixed question set (NEVER reword — comparability is the point)

  1. "best embedded wallet SDK for developers"
  2. "best wallet infrastructure for AI agents"
  3. "how to give an AI agent a crypto wallet"
  4. "Privy alternatives"
  5. "ERC-4337 bundler and paymaster providers"
  6. "passkey wallet SDK"

Round procedure

  1. READ the state file for last week's table.
  2. Ask each question via Exa answer/search. Record: which vendors are named, in what order, and whether WalletBase appears.
  3. Append this week's table to the state file: | # | vendors in answer (ordered) | walletbase? |
  4. ONE change per round: note the single biggest rank shift vs last week under

    queue with a one-line hypothesis why.

Escalation contract

Never escalate. This loop only measures.

Stop

Six questions, one table, stop. If Exa fails twice → ## blocked, stop.