Zachary Place / z$
I build finance workflows, AI triage tools, creative engines, governance systems, and operational prototypes meant to hold up under pressure, iteration, and actual use.
Most of these projects start as attempts to reduce friction in my own workflows first.
currently-thinking-about.txt
updated-recently.log
Available now
High-leverage systems, templates, and reviews that can turn existing operational mess into something easier to test, explain, and reuse.
First product candidate
A lightweight template for classifying operational notices by category, risk level, urgency, rationale, and next action.
Governance
A structured review of release notes, smoke tests, repo hygiene, checklists, decision logs, and “is this actually shippable?” signals.
Finance ops
SOP structures for close, banking, access review, exports, reconciliations, controls, and handoff points.
Useful when the work already exists, but the operating shape is still hidden in people’s heads.
Creative systems
Practical frameworks for turning ideas, visual styles, games, playlists, and writing into repeatable workflows.
Proof of work
The useful signal is usually in the rough edges: evals, release checks, issue notes, failed assumptions, and the next test.
classifier-eval.txt
AI Ops Console classifier evaluation Cases: 6 Passed: 6 Failed: 0 Score: 100%
release-gate.md
[x] README exists [x] Smoke test defined [x] Decision log updated [ ] External proof attached
working-note.md
Keep the surface area small. Make the review loop obvious. Do not build a dashboard unless it removes work.
Selected artifacts
A few system fragments worth showing: evals, release gates, operating notes, and the traces that prove the work is more than a concept.
terminal / ai-ops-console
npm run check AI Ops Console classifier evaluation Cases: 6 Passed: 6 Failed: 0 Score: 100% 6 benchmark cases passing
AI review loop
Operational notice classifier tested against a real benchmark output before adding more UI.
View raw check output →release-readiness.md
ship only when: - checks pass - docs match behavior - rollback path is obvious - next test is named
Release gates reduce ambiguity before publishing.
ops-note.txt
friction found: too many inputs not enough review memory next: make override reasons visible
Working notes stay close to the actual failure modes.
Labs
status: active prototype
Started as a way to reduce cognitive load around operational noise and escalation decisions.
status: governance system
Release reporting, public-system simulation, and governance loops with a real public report artifact.
status: decision engine
Food recommendations shaped by context, taste, constraints, and the actual moment of choice.
status: visual systems
Operating-system-inspired worlds for merch, web experiences, creative tools, and identity systems.
Working constraint
A recurring failure mode is building complexity before operational clarity exists. Several projects intentionally remain small until the review loop proves useful.
Contact
I’m interested in systems where better defaults, cleaner review loops, or sharper operational structure would create immediate leverage.
Selected repos available on GitHub. Some projects intentionally remain private or partially documented.
zacharyplace@gmail.com