Research
Sweeps configured sources and records coverage, including when a source is unavailable.
Project 05 · AI agents
Job Application Agent turns a fragmented search into a controlled workflow: it finds opportunities, evaluates fit, prepares the application, and only calls something a success after the external system confirms it.
Working MVP · local-first · evolving
This is a product demonstration. Roles, companies, documents, messages, and operator history remain private.
The product question
An application combines identity, documents, preferences, consent, and irreversible actions. The challenge was not making a bot click faster, but building a system that keeps intent and execution aligned.
How it works
Sweeps configured sources and records coverage, including when a source is unavailable.
Separates role fit, opportunity quality, and objective constraints before taking action.
Builds materials and answers from verified facts without inventing experience or credentials.
Stops when consent, sensitive information, or human judgment is required.
Records an application as submitted only after the external system returns real confirmation.
Trust architecture
Product code is versioned; identity, documents, and history stay in separate local state.
Explicit permissions define what the agent may execute and where it must stop.
Prepared, blocked, and submitted are different states. The interface never disguises an attempt as an outcome.
Proven tactics become reusable playbooks while policy and execution remain auditable.
What I learned
It preserves context, explains state, knows what evidence is missing, and returns the right decision to the right person. Job applications were the use case; the lesson applies to any agent operating in the real world.
← Back to projects