Agent Kit / Public reference
The work,
clearly documented.
For people and the agents helping them. Find relevant experience, follow the evidence and prepare a useful conversation.
01 / Match the work
Experience with context.
Start with the problem. Each area links to a specific part of a published case, including my role and the project's current stage.
Workflow automation
Clarify handoffs, prepare context and keep accountable review steps visible.
- Smart Lead System In operation
Product architecture, workflow design and operating QA.
- Field Operations In operation
Product design, operational data flow and QA strategy.
- Invoice System In operation / scoped payments
Product and workflow design, system architecture, AI-assisted implementation and operational verification.
What I would need to understand
- Where does work slow down or get lost?
- Who needs to review the next decision?
- What information must be ready before that handoff?
Practical web tools
Build focused, reviewable tools around a real operating process and clear public information.
- LowVoltagePlan Controlled pilot
Field workflow, scope modeling and review-gated product architecture.
- Smart Control Website Live website
Business requirements, website direction, AI-assisted development and content review.
What I would need to understand
- What should a person be able to understand or decide online?
- Which details need review before work starts?
- What evidence can be published safely?
Equipment and software integration
Connect condition monitoring, device workflows and software while preserving clear control boundaries.
- EcoGen Automation Controller Working prototype
Control workflow, low-voltage wiring, relay integration, controller setup and bench testing.
- Chevrolet Volt Diagnostics Toolkit Research & development
Diagnostics workflow, signal research and safety boundary design.
What I would need to understand
- What condition or device state needs to be visible?
- Which routine decision is safe to automate?
- Where must a person retain manual control?
Technical installation coordination
Coordinate teams, site logistics, electrical work and lighting control under practical constraints.
- My Heart is a Void, the Void is a Mirror Completed in 2020
Installation Lead: team leadership, site organization, lamp-post installation, electrical work and lighting control.
- My Heart is a Void, the Void is a Mirror Completed in 2020
Installation Lead: team leadership, site organization, lamp-post installation, electrical work and lighting control.
What I would need to understand
- What site restrictions affect the installation?
- What must arrive, be protected or be returned intact?
- Who owns coordination, safety and the next site decision?
02 / Inspect the record
Every case. Its actual stage.
A prototype is not a production deployment. An archived screenshot is not a live system check.
- Live interactive prototype
Worm Lab
Product concept, experiment workflow, interface direction and AI-assisted implementation.
Read Markdown - In operation
- In operation
- Working prototype
EcoGen Automation Controller
Control workflow, low-voltage wiring, relay integration, controller setup and bench testing.
Read Markdown - Controlled pilot
- Research & development
Chevrolet Volt Diagnostics Toolkit
Diagnostics workflow, signal research and safety boundary design.
Read Markdown - Live website
Smart Control Website
Business requirements, website direction, AI-assisted development and content review.
Read Markdown - Shadow research
MAC.BID Auction Research
Research workflow, risk-policy design and AI-assisted implementation.
Read Markdown - Engineering alpha
SafeRouter Home
Product requirements, network-policy workflow and AI-assisted engineering.
Read Markdown - Completed in 2020
My Heart is a Void, the Void is a Mirror
Installation Lead: team leadership, site organization, lamp-post installation, electrical work and lighting control.
Read Markdown - In operation / scoped payments
Invoice System
Product and workflow design, system architecture, AI-assisted implementation and operational verification.
Read Markdown
03 / Check the basis
Facts come with their limits.
- Project statuses are published as stated and distinguish live work, prototypes, research and completed installations.
- Public sources are linked where they are already published. Other details are explicitly marked as the owner's first-hand account.
- Screenshots retain their published demo, archive, synthetic-data and test-state boundaries.
- No private customer records, hardware identifiers, account access details, pricing or current availability are published.
- The reviewedOn date describes this published public record; it is not a new verification of a live runtime or external service.
For example, in the Odesa installation case, Gian Maria Tosatti is the artist and I am the installation lead. The account of carrying materials and returning the fixtures intact is mine. The organizers' publications document the exhibition and its support.
Read that case's evidence notes04 / Choose a format
One record. Several ways to read it.
These public files are generated from the same biography and case data as the site. They require no account, API key or JavaScript.
Start here
A short index with links to the profile, projects and brief guide.
/llms.txtProfile data
Identity, areas of work, relevant cases and collaboration boundaries.
/profile.jsonProject catalogue
All published cases, with roles, stages, sources and limitations.
/projects.jsonProfile in plain text
The published biography and a guide to the work.
/profile.mdPrepare a brief
Questions to answer before discussing a project. Nothing is sent.
/inquiry.mdThe JSON format is versioned. Review dates describe the published record, not a fresh check of each project's runtime. The index is a convenience, not a guarantee of inclusion in AI search.
05 / Prepare the conversation
A useful brief, not an automatic send.
Gather the context, identify open questions and let the person requesting the work review the draft.
- NameRequired for a useful brief
- The person preparing the draft.
- Email or phoneRequired for a useful brief
- A reply address or phone number for an eventual human-reviewed inquiry.
- What needs to work better?Required for a useful brief
- The current workflow, recurring friction, desired outcome and relevant constraints.
- Project areasIf known
- Optional selections from the published list: Custom software, AI automation, IT support, Field systems, Integrations, Not sure yet.
Before taking the next step
Not published. Discuss scope before pricing.
Not published. Discuss current availability before planning work.
- This guide describes a draft; it does not submit or store an inquiry.
- This Agent Kit prepares drafts only; use the website contact form to send an inquiry when available.
- A person must review any final inquiry before it is sent through an enabled contact channel.