01 / AUTOMATIONExecuted in n8n
One broken workflow.
A verifiable repair.
Reproducing a mapping failure, then accounting for every record with validation, conflict handling and visible outcomes.
Independent automation & systems
Make the
complicated
work.
Fragile workflows. Messy data. Moving parts.
We turn them into software with a clear job
and the checks to back it up.
Project-led. AI-assisted. Tested in the details.
SYSTEM STUDY / 001 INPUT → OUTCOME
RAW_INPUT{?}incoming payload
VALIDATEknown inputs.
explicit outcomes.
explicit outcomes.
ACCEPTclean & ready
REVIEWvisible exception
DEDUPLICATEwithin this batch
Less guesswork.
More defined behavior.
SCHEMATIC
01 / THE PORTFOLIO
Built, tested,
and still evolving.
Four independent projects.
Different problems.
Evidence you can inspect.
One broken workflow.
02 / SOLANALive-use history
Trading automation.
Operational visibility.
A perpetuals project connecting trade monitoring, dashboard controls and cost reporting, with a separate development and learning track.
03 / DATA TOOLSLocal prototype
Small CSV edits.
Big things to notice.
A browser utility comparing Shopify product exports for supported price, identifier, blank-field and variant differences.
04 / EXECUTION SYSTEMSPre-launch
Fast execution.
Deliberate boundaries.
Jupiter YOLO engineering around transaction validation, swap and settlement checks, bounded execution and recovery handling.
Test counts refer to each project’s recorded checks, not customer outcomes. YOLO’s funded own-wallet lifecycle remains unverified. Read the evidence summary ↗
02 / THE PROOF BENCH
Don’t just read about it.
Break something.
Change an input. Run the repair.
See exactly what happens.
Everything stays in this browser.
02 / OBSERVED OUTCOMEREADY
0Accepted
0Rejected
0Batch duplicate
Synthetic examples. This bench runs the shared mapping logic in JavaScript; the before/after exports were separately executed in n8n 2.44.6. Duplicate checks apply within one run only. Inspect the demo source ↗
03 / HOW WE WORK
A smaller scope.
A clearer result.
Good engineering starts with a specific problem. We agree on the expected behavior, make the change, and show the checks.
Download the project resumeFind the actual failure.
Trace the inputs, reproduce the issue and separate symptoms from causes.
Define what “fixed” means.
Agree on scope, outputs and acceptance checks before implementation.
Make it hold up.
Test normal inputs, missing data and failure paths. Keep exceptions visible.
Hand over something usable.
Focused code, reproducible checks and straightforward notes for the next person.
04 / YOUR NEXT SYSTEM
What needs
to work better?
Start with the problem. This local brief builder turns it into a useful first conversation. Email it only when you choose to send.
cncpyro-yolo@agentmail.to ↗Our project inbox. Send a sanitized description to start.
For Upwork projects, paste the brief into Upwork Messages. Scope and a funded milestone come before implementation.
Copy or save locally, or open your email app. Nothing is sent automatically.