A personal workflow, in motion

EDITION 02 / SEP 2026

I automatedthe busywork.Not the decision.

Find the right roles. Check the real fit. Prepare something worth sending. A connected system handles the repetitive work, while the evidence—and the final decision—stay with me.

Explore the system
VERIFY THE FITPREPARE THE EVIDENCEFOLLOW THE CONVERSATION

SOFTWARE HANDLES THE REPETITION.
I KEEP THE INTENTION.

01 / The architecture

Follow the signal.

One collector. Three independent loops.
Click any component to see what goes in,
what happens, and what comes out.

SYSTEM EXPLORER
INTERACTIVE ARCHITECTURE / ILLUSTRATIVE FLOWCOLLECT → VERIFY → PREPARE → TRACK
01 / RESOLVE THE UNKNOWNS
02 / BUILD THE APPLICATION
03 / CLOSE THE FEEDBACK LOOP
TICKET CONTEXT & DURABLE HANDOFFS INDEPENDENT AI MATCH RADAR → DASHBOARD ONE CHECK. THREE POSSIBLE OUTCOMES. A high score is not an eligibility pass.
A missing fact stays a question.
SPECIALIST SKILLS NO AUTO-SUBMIT · External action stays human-controlled
Skill / loopMCP / serviceDurable state
← Swipe to explore the full diagram →Tap a node for details
A system that keeps the context.Click a component, isolate a loop, or trace a hypothetical application.
Animated routes explain responsibility—not live traffic or service health.Architecture checked against repository sources · 28 Sep 2026

02 / Purposeful separation

Three loops.
Not one giant prompt.

Discovery no longer competes with preparation.
The service collects. Each scheduled loop has
one kind of work to move forward.

01 / VERIFIER

Is this actually
a fit?

Check the collector’s uncertainties against the full role, employer requirements and canonical CV. Pass with evidence—or ask the question that really matters.

review_needed→verify→queued
02 / PREPARER

Make the application
worth reading.

The orchestrator coordinates the specialists: research, form inspection, truthful CV trials, writing and validation. Every final artifact is linked back to the ticket.

authorized→prepare→ready
03 / EMAIL WATCH

Don’t lose
the conversation.

Read recruiting updates across Inbox and Spam. Match the exact application, preserve the email evidence, update the timeline and surface what needs attention.

message→ticket→update

The collector runs separately. Deno + PostgreSQL handle discovery and scoring on the CapRover service. The verifier and preparer work on existing tickets, not another discovery queue.

03 / A useful finish line

An application.
Not a pile of tabs.

The output is a coherent, inspectable package. It fits the actual form, stays faithful to my experience, and gives me everything I need to make the next decision.

A truthful, role-specific CV and optimization audit
A cover letter when the destination supports it
Exact, field-mapped application answers
Research, source references and actual file links
APPLICATION / REVIEW PACKAGE
ROLE-SPECIFIC · EVIDENCE-LED

Sandoche

A truthful headline for this role.

RELEVANT EXPERIENCE
SELECTED PROJECTS
SUPPORTED SKILLS. NOTHING INVENTED.
Prepared ≠ submitted
ILLUSTRATIVE PACK · NOT A REAL APPLICATIONHUMAN REVIEW NEXT ↗

04 / The specialist library

Small skills.
One consistent standard.

Twelve versioned playbooks—not twelve
independent agents. Each has a clear task.
The orchestrator preserves the boundaries.

12 / 12 SKILLSManifest · 28 Sep 2026 · Submission stays outside scheduled runs.

05 / State, not guesswork

The work stays inspectable.

A conversation can end. The evidence shouldn’t.
Durable state makes the next run a continuation,
not a fresh start with a confident guess.

ONE TICKET. ONE CURRENT STATE.

Progress with a paper trail.

Collector state lives in PostgreSQL. Application state lives in one v2 GitHub comment. Human replies, decisions and artifact links stay with the ticket.

Review needed. The collector found a role worth considering. Its score and open questions do not yet grant permission to prepare.
Any genuine blocker stays visible.

PIPELINE DASHBOARD

READ-ONLY VIEW
Prepared≠NOT APPLIED
Submitted↗ACTION EVIDENCE
Outcomes→REAL HISTORY
SCHEMATIC · NOT LIVE METRICS

Two sources. Different questions.
Project history for outcomes.
AI Match for the opportunity radar.

06 / The point of the project

Less repetition.
More intention.
Still my decision.

01

Evidence before confidence.

A full posting beats a snippet. A confirmed motivation beats a plausible story. Missing information remains visible.

02

Resume the work. Don’t reinvent it.

Keep state, exact inputs and receipts outside the conversation. Verify uncertain writes before repeating them.

03

Automate preparation, not consent.

The collector can find it. The skills can prepare it. I still choose the opportunity and the external action.

ARCHITECTURE NOTES & SOURCE CODE READ-ONLY DESIGN PREVIEW / 28 SEP 2026

Current architecture, not a deployment audit. The collector, v2 ticket state, verifier, preparation orchestrator, MCP evidence tools and skill versions were checked against repository sources on 28 September 2026. The three scheduled loops are the requested system design; this page does not assert that any scheduler is currently enabled.

One clearer name. Application Studio MCP is the display label for the existing Job Search Assistant service. No endpoint, server or tool name has been changed.

No fabricated live data. Animated paths, the guided application, document mockup and dashboard sparkline are illustrations. No candidate answers, credentials, live counts or private emails are embedded. This file performs no network requests; only deliberate external source-link navigation leaves the page.

The email loop follows the existing watch workflow and requested Gateway integration, not a new versioned skill. Source links to private repositories may require access. The source pages can change after this dated review.