Today: Building nnn in the mornings. Lockr support tickets in the evenings. Sleep is a hypothesis, not a fact.
srivtx. Polymath, first-principles thinker, tinkers with hardware. He builds software the way other people build furniture: by hand, on a bench, with the joints visible. Most of his work sits at the seam between systems software and the interface — Rust binaries that serve markdown, Zig frameworks for Solana, language servers, agent loops, CSS preprocessors. The recurring question is the same one: what does this look like if i stop reaching for a framework?
Five agents on one local model. Architect plans, developer writes, bugfixer runs the code, researcher reads the workspace, websearcher hits the docs. They pass a shared scratch directory back and forth.
The point is not the agents. The point is that they run on a 7B Qwen, locally, with no API key and no cloud. The agents do not invent the architecture or pick the stack. They execute. The human still decides.
Client pays by card or UPI. Dodo converts to USDC. Funds lock in a Solana PDA. The freelancer gets paid in about three seconds after the client approves a milestone. The 14-day Upwork hold dies here.
A matchmaker's CRM redesigned as a private-banking brief.
Three-column compare canvas, AI-drafted composer where the AI's job is bounded to one sentence, a 10-dimension weighted matching engine. The matching logic is reused from v1; the design system, layout, and most components are new.
Lexer, parser, AST, analyzer, symbols, interpreter — each in its own Rust file.
Built to learn how a language tool works end to end, not to ship an LSP. Same thesis as the Zed Zettelkasten work — language tooling is something I keep coming back to, sometimes from the editor side, sometimes from the parser side.
A comptime layer that knows the SBPFv3 ABI and stays out of the way at runtime. A full PDA vault — state, three instructions, every edge case — fits in under a hundred lines of Zig.