ASakhilsingh.dev
UTC --:--:--

Akhil Singh

AI engineer · Pune, India

I build AI systems and the infrastructure underneath them: voice assistants, retrieval pipelines, and C++ that gets measured in nanoseconds. Most of my day-to-day work lives in private repos. This is the open-source side.

Off the keyboard: national cross-country mountain biking champion, 2021.

View EDITHSource on GitHub
FlagshipIn build

EDITH

Local-first, voice-first AI assistant for macOS with graph memory and a tiered model router.

View details →
FeaturedShipped

ohlcv-validator

C++20 market-data pipeline. 6.03 ns per record, zero allocations on the hot path.

View details →
Flagship · time in developmentT+ ---d --:--:--
In buildOpen source · MITPython · macOS · local-first

EDITH

Even Dead I'm The Hero

A local-first, voice-first AI presence for macOS. EDITH remembers your projects and working style, watches your dev sessions, and takes action on your behalf. Everything runs inside one daemon: edithd.

Local-first is a constraint, not a preference. The graph, transcripts and keys stay on the machine. The only thing that leaves is a redacted payload to the model gateway.

Commits
183
Test files
66
Slices built
0 to 6
Runtime
1 daemon
Latency shape: Opus never blocks a spoken turn
"think about our sharding strategy"
      │
      ├──> SONNET  ack now ──> "On it. I'll follow up."
      │                        turn ends, mic free
      │
      └──> OPUS    think_async, off the critical path
                 ├──> remember(detail)
                 └──> spoken summary, later
Build sheet
  • S00North-star architectureDone
  • S01Memory, Brain, edithd, Control APIDone
  • S02PR-review skillDone
  • S03Voice: wake, STT, TTSCore done
  • S04Session awarenessDone
  • S05Router + latency maskingDone
  • S06Desktop controlCore done
Subsystems
  • Voice loopWake word, speech-to-text and text-to-speech. ElevenLabs or local Piper.
  • Graph memoryKuzu graph plus sqlite-vec vectors, on disk, with bounded compaction.
  • Tiered routerSonnet is the talking voice. Opus thinks in the background and never blocks a turn.
  • Redaction choke-pointRuns inside every model call and on every TTS and bus payload.
  • Autonomy gateDefault-deny over a closed action vocabulary, with a windowed token budget.
  • Session awarenessTaps every Claude Code terminal and narrates what changed.
  • Desktop controlLaunches apps and drives terminals through osascript and open.
  • PR review skillFirst autonomous action. Confirm-gated before anything is posted.
macOS · Apple Silicon · Python 3.11 · any Anthropic-compatible gatewaySource on GitHub →
Featured · low-latency systemsv0.1.0 · MIT
ShippedC++20 · market data

ohlcv-validator

A low-latency market-data pipeline built to HFT engineering standards. It validates live and exchange-style feeds on a zero-allocation hot path, reconstructs a redundant A/B multicast feed, and rebuilds an L2 order book with snapshot recovery.

Every correctness claim has a test. Every performance claim has a measurement.

Hot path · validate6.03ns / recordsingle core · Apple Silicon · 2026-07-27 · zero allocations
Latency tail · x86 · rdtscp
p50
20 ns
p99
30 ns
p99.9
40 ns
Single core · Apple Silicon
165.8M rec/s
24 cores · x86
~1.1B rec/s
C++ tests
115
Python tests
32
Sanitizers
ASan · UBSan · TSan
Parser
Fuzzed
Feed path
Line A + B→FeedArbitrator→WireRecord→Validator→Violations
  • Zero allocations, provenA test overrides global operator new and fails on any hot-path allocation.
  • A/B feed arbitrationEvery sequence delivered once, in order, from whichever line wins. Real gaps detected, reorders tolerated.
  • Snapshot recoveryA gapped stream rebuilt through recovery is byte-identical to a from-scratch build.
  • Binary over JSONThe measured path reads fixed-stride 88-byte records straight from mmap. No parse, no copy.
Source on GitHub →
Projects

More projects

Software factory

How we build

  1. 01

    Spec

    North-star architecture first, then one spec per slice.

  2. 02

    Slice

    Ship vertical slices that work end to end, not layers.

  3. 03

    Test first

    Red to green. Hardware and network sit behind injectable seams.

  4. 04

    Measure

    Every performance claim has a benchmark with its date, host and command.

  5. 05

    Record

    Each slice closes with a completion record. Limitations get written down.

Contact

Want a walkthrough of the architecture?

Happy to go deep on any of it.