I build the systems layer for businesses without engineers.
By day, I run the systems for a digital marketing agency. On the side, I run NoCodeWorkflows, a review site and directory for no-code and AI-agent tools. This page shows the system underneath it.
See the systemsThe System That Builds the Systems
My personal OS.
These are my personal systems, and I run them every day to power everything I build. The vault holds what I know, and only the vault is a record. The archive holds what happened. ClipBase holds what I have read. Nothing moves up until I promote it, and nothing moves out except through a sanitized mount.
-
Operating infrastructure
Two directories, never the whole vault
An agent reads whatever directory you open it in.
Each repo mounts a slice. No session ever bypassed the gate.
-
Conversation memory
The memory I deleted
A system that writes its own memories will trust them.
Every conversation searchable. The vault stays the record.
-
ClipBase retrieval eval
The fix worked and the score decreased
Most changes to a retrieval system ship, and no one measures whether they helped.
The fix ran on the live corpus. The eval says that it cost a rank slot.
NoCodeWorkflows
NoCodeWorkflows is my venture. It publishes operator-level reviews of no-code and AI-agent tools, a curated directory, and playbooks. A pipeline I built publishes the site: a saved bookmark becomes a directory entry.
The Story
- I spent eight years in behavioral-health operations: utilization review, revenue cycle, clinical documentation.
- I learned to build in 2020. Automation came first, then real code.
- Now I do the same work at agency scale, and I build my own systems on the side.
Work With Me
info@mattbastar.comSend an email about your operation. An introduction from someone we both know also works.