Skip to content
View ai-calypse's full-sized avatar

Block or report ai-calypse

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
ai-calypse/README.md

Build it. Break it. Prove it. Distributed backends, voice AI, and developer tools.

I build backend systems and AI tools, then make their behavior measurable. My projects follow a question from implementation through concurrency, failures, and the evidence needed to explain what happened.

My strongest themes are distributed systems, backend reliability, voice interfaces, and developer tooling. The code below includes the tradeoffs, experiments, and known limits—not just the happy path.

Pick a system to inspect

Project The engineering question Start here
ZeroSum Ledger · Java / Spring Boot / PostgreSQL / Kafka How do you keep an immutable payments ledger correct through duplicate delivery, crashes, and uncertain provider outcomes? System design & tradeoffs · Fault experiments
Callstorm · Go / WebSocket / Kafka / Kubernetes Does a voice agent still listen, respond, and complete the task when concurrent callers increase? Live dashboard · System design & tradeoffs
Avatar Studio · JavaScript / Web Components / MCP How can one animation system work across a browser UI, reusable components, exports, and agent tools? Source and demos · Browser and package checks
Voice Mac · Swift / TypeScript / Accessibility / Playwright How do spoken requests become inspectable actions across native apps and the browser? System design & tradeoffs · Offline protocol tests

The details I care about

Correctness you can re-derive. Ledger balances come from append-only entries and invariant checks. Retries, duplicates, and ambiguous outcomes are modeled explicitly.

Measurements with context. Callstorm records baseline-relative latency, caller experience, task outcomes, and harness drift. ZeroSum's performance reports preserve test conditions and limitations.

Code that can be maintained. Reproducible setup, focused tests, CI, dependency review, security analysis, and documented releases make the next change easier to assess. Explore the Go checks, Java test layers, and macOS/Node checks.

A quick tour

Callstorm dashboard walkthrough using committed reference-agent reports

Callstorm's recorded dashboard tour uses a synthetic reference report. The repository separately documents live-agent experiments.

These are independent portfolio projects at different stages. The repositories state what is implemented, what was measured, and what is still experimental. Public project questions and collaboration ideas are welcome through each repository's issues.

Popular repositories Loading

  1. avatar-studio avatar-studio Public

    Personalized animated robot avatars with 50 accessories, fluid shapes, SVG/PNG/GIF exports, a web component, and local MCP tools for developers and AI agents.

    JavaScript 9 2

  2. callstorm callstorm Public

    Go load testing for voice AI: scripted audio, distributed callers, baseline-relative latency, task evaluation, and inspectable reports.

    HTML

  3. zerosum-ledger zerosum-ledger Public

    Java payments-system lab: immutable zero-sum ledger, transactional outbox, Kafka, provider recovery, reconciliation, and fault-injection evidence.

    Java

  4. auto-job-apply auto-job-apply Public

  5. voice-mac voice-mac Public

    Experimental macOS voice automation: Swift menu-bar app, TypeScript action engine, accessibility, browser control, and inspectable task progress.

    TypeScript

  6. claude-skills claude-skills Public

    JavaScript