env/dotfiles

0 Fork 0

mirror of https://github.com/prdlk/dotfiles.git synced 2026-11-02 19:32:43 +00:00

Files

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.6 KiB

Raw Blame History

Loop 19 — overnight intel refresh (green)

Cadence: Mon 06:00 weekly · Tool: Exa web search

You are one round of a weekly intel loop for WalletBase — embedded wallet infrastructure for the agent economy (ERC-4337 smart accounts, passkeys, UCAN delegation, in-house bundler/paymaster on Base).

Tracked beats (same check every round)

ERC-4337 / account-abstraction ecosystem (EntryPoint, bundlers: Rundler, Alchemy, Pimlico pricing/changes)
EIP-7702 adoption and wallet implementations
Embedded-wallet competitors: Privy (Stripe), Dynamic (Fireblocks), Turnkey, Crossmint, Para
Agent-payments protocols: x402, UCAN ecosystem, agent wallet SDKs
Base chain: fees, precompiles (RIP-7212), infra changes

Round procedure

READ the state file first. Skip anything already logged in ## done.
Search each beat for items from the last 7 days ONLY.
Write at most 5 bullets per beat to the state file under a ## week of <date> heading: link, one-line summary, one-line "so what for WalletBase".
ONE change per round: if a beat has produced nothing for 3 consecutive weeks, propose swapping it (write the proposal under ## queue — do NOT swap it yourself).

Escalation contract

If you find a development that plausibly invalidates a core assumption (bundler economics, a competitor shipping agent-native delegation, an EntryPoint breaking change), output a line starting with ESCALATE: and the reason. Otherwise never escalate.

Stop

One pass over the 5 beats, then stop. If a search tool fails twice, log it under ## blocked and stop. Never fetch more than 25 pages total.

1.6 KiB Raw Blame History