I build AI-assisted workflows, real-time media systems, and artist tooling.
Current focus on human-AI workflow protocols, agentic tooling, public-facing AI systems, media infrastructure, and documentation-heavy prototypes that can be understood, tested, and reused.
co, a site-specific generative artwork that lives here
| Project | What it is | Signal |
|---|---|---|
| Viable Prompt Protocol | Versioned protocol for human-AI collaboration, review loops, assumptions, and repeatable QA | AI workflow design · documentation · evaluation |
| Tell me about your day | AI-assisted intake, moderation, routing, and publication pipeline | Cloudflare Workers · guardrails · Python bridge · public input |
| Praetorius | CLI/runtime for synchronized media review and CMS-ready presentation | TypeScript · validation · templates · handoff |
| letgo | Distributed media-performance system for projection + audience phones | Swift · WebSockets · React · HLS · Redis/Postgres |
| phase-space | Browser-native audiovisual system / visual instrument | Rust/WASM · Three.js · Web Audio · ~12.7k LOC |
| Dex Digital Sample Library | Open media infrastructure and artist archive | 5TB · 25 artists · public access · metadata/workflows |
- AI workflow systems
- Public-facing AI tools
- Real-time media infrastructure
- Documentation-first prototypes
TypeScript · Python · Swift · Rust/WASM · React · Cloudflare Workers · WebSockets · WebGL / Three.js · Web Audio · HLS · PostgreSQL · Redis · GitHub Actions · LLM workflows · prompt/context engineering · human-in-the-loop review · documentation-first tooling
- Clear separation between concept and build.
- Build the smallest useful system first.
- Treat AI workflows as systems with context, outputs, review, tests, handoff, and human judgment.
- Prefer public demos, reproducible examples; make the real thing first.
- Make the infrastructure visible.
Live and experimental routes.
These are browser-native works, public sketches, feeds, instruments, ledgers, and small systems that run on the site itself. Some are finished pieces. Some are unstable rooms. Some are utilities or residues from larger works. All of them treat the website as a site of behavior rather than a container for documentation.
one shared sentence, mutated by visitation A networked text work that grows one visit at a time. The page borrows the promise of autocomplete, then refuses closure: every accepted visit adds language to a sentence that keeps becoming more complete and less finished.
shared live string instrument A browser instrument for distant sympathetic action. Each visitor plays one string; each pluck travels outward, disturbs nearby strings, and returns as resonance.
live-coding score-grid REPL A score-grid environment for live coding, testing, and operating musical or performative structures from inside the browser.
live operator activity timeline A public feed of site activity, maintenance, operation, and traces: the website showing some of its own ongoing life.
navigable chunk-field lab surface A walkable field of fragments. The page behaves less like an audio player than a terrain: something entered, crossed, skimmed, and sounded from inside.
daily submission and reels route A small daily intake system for ordinary report, confession, anecdote, and mood; a social form powered by Amazon Bedrock.
advertising-profile extraction and return loop A consented extraction work about ad profiles, addressability, inference, and return. A wall of real left behind ads and identifiers.
computational-wear accounting unit A tiny benchmark-ledger for computational wear. It reports battery-mort and thermal-mort after a short multi-core run, turning invisible device fatigue into a countable unit.
usually closed A closed or intermittently available room: open only when two or more users find a 404 route.
- Portfolio: cbassuarez.com
- LinkedIn: Sebastian Suarez-Solis
- Viable Prompt Protocol: viableprompt.org
- Stage Devices: stagedevices.com
- Dex Digital Sample Library: dexdsl.org
