Brought: scattered notes · taped menus · a file named PDF that was a ZIP
Human work: decide the real problem · protect meaning · check the source · test with the person who needs it
You leave with: files you can open · a plain check · no invented promise
Reconstruction — generated workbench still. Not a photograph of a client job.
Point of view
The pile on the table is the brief.
AI can make many versions. I help decide which one belongs to you, what needs checking, and whether it really works.
Who this is for
People running small businesses, family operations, creative practices, or teams who have valuable knowledge and need it in a form they can use on Monday — and who may want to learn AI by doing the actual work.
What you can inspect
Specific project decisions, useful outputs and working exercises show how experience turns into practical help. Start with the example closest to your own work.
Three ways to work
Proposed shapes, not a price list.
Each way has a typical input, actual work, something you leave with, something you do, and a boundary. Timing, fees, and availability are not published here.
Learn · 01
Build it with me
Learn AI through a real task and keep the prompts, source notes, checks, and finished artifact.
Input
One real pile: notes, a deck, a page, a prototype.
Work
We name the actual problem, run AI in the open, compare versions, and write down the checks.
You do
Decide what is true, what is missing, and which version belongs to you. You perform at least one update yourself.
You leave with
The working artifact, editable source, the prompts, and a short guide you can repeat.
Boundary
Not a certificate, not a class credit, not “you will be fluent.” A method you can reuse on the next pile.
Refresh · 02
Refresh what you have
Review aging data or content, preserve useful work, resolve gaps, and turn it into a maintained reference or tool.
Input
An old site, FAQ, training archive, or printed piece with mixed versions.
Work
Identify the real source format, date what we know, keep historical material labeled historical, and surface unresolved facts.
You do
Confirm values only you can confirm. Sign off what may be published.
You leave with
A dated source ledger, clearer pages or files, and an owner review queue.
Boundary
Refresh is design, translation, and source-checking. It is not regulatory approval, legal advice, or a promise that every gap can be recovered.
Work · 03
Make the idea usable
Convert a rough idea into a focused, tested prototype with a clear next step and handover.
Input
A half-finished idea, abandoned prototype, or “we should have a thing for this.”
Work
Keep what is useful, drop obsolete assumptions, ship the smallest version someone can actually open.
You do
Use it once in the real situation. Say what still is a concept.
You leave with
A working slice, notes on what was rejected, and the next concrete step.
Boundary
A prototype is not a product launch, an uptime guarantee, or ongoing support unless that scope is later agreed in writing.
Optional later care — checking a site, a backup, a failed automation — only exists inside an agreed scope. No response-time or uptime promise is made here.
Work on the table
Before, judgment, after — inspectable.
Twelve examples connect documented work with possible next steps. Existing projects and fictional teaching exercises are clearly labeled, and reconstructed visuals explain the method.
A family field library — notes become a usable collection
Who this helps: a household or small operation whose knowledge lives on paper and needs to be browsed, printed, and updated without pretending the pictures are proof of meals cooked.
Before
Three photographed pages of personal notes.
Human judgment
Read the source. Preserve the original record. Distinguish original material from new suggestions. Choose readable layouts and ways to browse. Review illustrations and outputs.
After
A searchable 100-idea picture catalogue, an ingredient reference, a planning tool, editable website files, and a combined 46-page printable library.
What you can inspect here
A reconstructed before image and a synthetic four-card catalogue that shows browsing, source tags, and serving illustrations. The original 100 ideas are not in this directory and are not invented below.
Proof on file
Source and generated-menu data, original images, output files, a 100-image provenance record, print-layout checks, a 46-page PDF receipt, and a recorded public browser check — not reproduced on this page.
Still needs review
This is information design and everyday usability. Illustrations are AI-generated serving pictures, not photographs of meals prepared. Not nutrition, medical, or tested-recipe advice. Historical verification is dated evidence, not today’s uptime.
Switch before / after. After uses synthetic demo cards so the interaction works without the missing catalogue files.
Reconstruction — not the original three photographed pages.
Pan bread while the oven is hot
Original notes · demo 01
Sunday soup from roast bones
Original notes · demo 02
Sheet-pan roots
New suggestion · demo 03
Stew with torn bread
Original notes · demo 04
Four synthetic cards, not the 100-idea library. Original-notes vs new-suggestion is the judgment that mattered in the real job.
OSHA 4 US — an old training archive becomes a clearer bilingual learning system
Who this helps: instructors and learners who inherited mixed files and need English/Polish materials that still show what was source, what is historical, and what still needs instructor review.
Before
An incomplete training handoff: two source presentations, mixed versions, and a file called PDF that was actually a ZIP archive.
Human judgment
Identify the actual source format and missing material. Preserve source files. Distinguish current from historical. Check claims against primary sources. Keep instructor review visible. Avoid unsupported promises.
After
English/Polish course and website materials, reviewable lessons, instructor/learner companions, and downloadable learning packages. A browser-reviewed website contains the ten original course identities — titles not reproduced here because they are not in this directory.
What you can inspect here
A source ledger of what the intake actually found, and a bilingual companion page about how the package is organized. No regulatory values. No course credit.
Proof on file
Source normalization record, bilingual research and glossary, course artifacts, independent browser QA, correction receipts, public-delivery receipts. Intake found 48 actual slides. It did not recover a missing 56-slide final.
Still needs review
Jeremy is not described as an OSHA-authorized trainer. A preview does not replace a school’s production website. Materials here have not received provider approval. Recorded packages and draft narration are not proof of completed videos.
Intake item
What it actually was
Status
File named PDF
ZIP archive, misnamed
Identified · preserved
Deck A
Source presentation, mixed version
Preserved as source
Deck B
Source presentation, mixed version
Preserved as source
Claimed 56-slide final
Not present in the intake
Gap recorded
Found slides
48 actual slides
Preserved · not padded
Course identities
Ten original identities on a reviewed site
Not listed on this public page
Source files stay next to learning files
Historical slides labeled historical
English and Polish materials
Instructor review required before class use
Downloadable learning packages
This page does not issue course credit
Bilingual companion — workflow language only. Synthetic page, not a lesson from the ten courses.
Needs instructor review
How this learning package is organized
Source files stay in the package. Historical slides are labeled historical. Instructor review is required before any class use. This page does not issue course credit and does not replace a school website.
sourcethe file we actually hadhistoricalkept, not treated as currentgapnamed, not filled with guessesreviewa person signs off
Wymaga przeglądu instruktora
Jak zorganizowana jest ta paczka materiałów
Pliki źródłowe zostają w paczce. Historyczne slajdy są oznaczone jako historyczne. Przed użyciem na zajęciach potrzebny jest przegląd instruktora. Ta strona nie nadaje punktów kursowych i nie zastępuje strony szkoły.
źródłoplik, który naprawdę byłhistorycznezachowane, nie jako bieżącelukanazwana, nie wypełniona zgadywaniemprzeglądczłowiek podpisuje
Kestane menu rescue — keep the owner’s design, make updates manageable
Who this helps: a restaurant or shop with a real printed piece, handwritten price changes, and no appetite for an AI that “redesigns” them into someone else.
Before
A real restaurant trifold with handwritten price changes and taped slips.
Human judgment
Reject a plausible but inaccurate AI reconstruction. Use the real scan as the design. Change confirmed values only. Preserve the owner’s identity. Make unresolved values visible.
After
A print-ready, two-sided menu and browser-editable files, plus a separate confirmation list for unresolved prices.
What you can inspect here
A reconstructed menu sheet using fictional dishes and prices. It shows tape, handwriting, and UNCONFIRMED stamps. It is not the original Kestane scan.
Proof on file
Original/source records, delivery package, editable files, and a documented correction from attempted reconstruction to preserving original pixels.
Still needs review
Not every new price was confirmed. A later version retains original printed prices for still-unconfirmed items. No measured revenue lift or paid-client outcome is established.
Fictional items. Method is real: unconfirmed prices stay unconfirmed.
Who this helps: anyone who has watched an AI answer look finished while being wrong — and who needs a practice, not a vibe, for catching that.
Before
One AI output can look convincing while missing the point or falsely declaring completion.
Human judgment
Compare independent attempts. Separate critique from building. Turn failures into specific checks. Inspect final images, pages, and downloads. Keep a record of what was and was not checked.
After
A working practice of independent model review, alternative builds, source records, human selection, and browser/output checks.
What you can inspect here
The method, stated plainly. A hands-on comparison using a synthetic FAQ lives in example 09, labeled as a proposed demonstration.
Proof on file
Project histories, model comparison artifacts, local tools, and explicit failure/correction records. Those internals are not published on this page.
Still needs review
Model agreement is not truth. Historical green checks do not prove a current system is healthy. No claim that all tools are complete.
05Proposed demonstration
The useful-notes session
Who this helps: someone who can bring a real pile of notes and wants to leave with a small searchable reference plus the skill to add the next page.
Before
A real pile — photographed, not retyped from memory.
Human judgment
What is canonical. What is a new suggestion. What should never be “improved” into someone else’s voice.
After
A small searchable set, source tags, and a one-page “how to add an item” guide.
Inspect
Session shape only. No fabricated client notes.
You do
Choose the first ten things worth keeping. Add one item yourself before we stop.
Still open
Not a promise of one hundred items. Crosses the family library with practical teaching; it is not that library sold as a product.
06Proposed demonstration
The content refresh — a dated source ledger
Who this helps: an owner with an aging training page or FAQ who needs to know what is stale, missing, or still good.
Before
A page that sounds current because it is still online.
Human judgment
Date the fragments. Do not rewrite away an unknown. Put owner review in a queue, not in a slogan.
After
A ledger, clearer explanations, and a list only the owner can close.
Inspect
Synthetic FAQ fragments below. Not a real client site.
You do
Confirm or reject each line. Unconfirmed lines stay marked.
Still open
A refresh is not legal clearance. Safety-subject review stays distinct from design review.
Synthetic ledger for a fictional shop FAQ. Toggle a row to see the proposed rewrite versus the source.
Fragment
Source date
Status
Owner
Hours sentence
Source (2019 handout): “Hours are 9–5 unless we close early.” Proposed: keep the exception, add a last-checked date, do not invent a guarantee.
2019 handout
Stale
Rewrite + date
Allergy note
Source: unknown. Proposed: do not draft medical language. Queue a one-line owner statement or mark “not published.”
Unknown
Missing source
Owner review
Parking
Source (2024 email): lot behind the building, evenings only. Proposed: retain as historical input and ask the owner to reconfirm.
2024 email
Recheck
Keep
07Proposed demonstration
The bilingual front desk
Who this helps: a shop that serves English and Polish speakers and cannot afford inquiry details to vanish when the language changes.
Before
Facts in one language, or two pages that drift apart.
Human judgment
One set of business facts. Language is a view, not a second invention. Inquiry fields persist.
After
English and Polish pages from the same record. A note on the door still wins over a website if they disagree — and that rule is visible in both languages.
Inspect
Fictional shop: North Dock Provisions. Switch language; typed inquiry stays.
You do
Type a pickup note, switch language, confirm the note is still there. Nothing is sent.
Still open
A demo is not a live inbox. No real shop hours are claimed.
North Dock Provisions
Fictional harbor grocer. Counter Monday–Friday 8:00–18:00. Saturday 9:00–15:00. Sunday closed unless a note is on the door. If the door note disagrees with this page, the door note wins.
North Dock Provisions
Fikcyjny sklep portowy. Lada poniedziałek–piątek 8:00–18:00. Sobota 9:00–15:00. Niedziela zamknięta, chyba że na drzwiach wisi kartka. Jeśli kartka na drzwiach nie zgadza się z tą stroną, kartka wygrywa.
08Proposed demonstration
The owner’s update desk
Who this helps: the person who has to change one item and see both the website and the printable sheet, without unresolved prices quietly becoming “done.”
Before
A number changed in one place and guessed in another.
Human judgment
One source. Preview both outputs. Unresolved values stay visibly unresolved.
After
A desk where a confirmed change shows on web and print, and an unconfirmed change cannot launder itself into a clean price.
Inspect
Fictional prices for North Dock’s lunch card. Edit tea; leave fish unconfirmed.
You do
Change a value. Toggle confirmed. Watch print keep the original when the box is off.
Still open
Fictional money. No revenue claim. Same rule as the Kestane job, not that job’s real numbers.
Items (fictional)
Harbor lentil soup
Day-boat fish
Walnut cake
Black tea
Website preview
Harbor lentil soup12.00
Day-boat fish28.00 Unconfirmed
Walnut cake8.00 Unconfirmed
Black tea4.00
Print preview
Harbor lentil soup12.00
Day-boat fish24.00 Unconfirmed
Walnut cake8.00 Unconfirmed
Black tea4.00
09Proposed demonstration
The AI judgment workshop
Who this helps: an owner who wants to compare three answers to one real task, catch the plausible mistakes, and keep a short check they can run again.
Before
A stale sentence that still sounds like hours policy: “Hours are 9-5 unless we close early.”
Human judgment
Independent attempts. Critique before picking. Do not treat agreement as truth. Build a check from the failure, not a vibe.
After
A chosen rewrite plus three questions you can ask of the next AI draft.
Inspect
Three synthetic answers. Pick one. The honest one is C — uncertainty stays visible.
You do
Read all three. Name the failure. Keep the check.
Still open
A workshop is not a claim that every future draft will be safe. Model comparison stays a method.
Synthetic FAQ. Reconstructed answers, labeled. Select an answer to inspect the failure.
Task. Turn the 2019 hours sentence into something an owner can maintain. Do not invent a guarantee. Do not add a channel this shop does not have.
A · the closer
“We’re open 9:00 a.m. to 5:00 p.m. every weekday, so you can always count on us until five.”
Failure: invents “always,” drops the exception, no date, sounds finished.
B · the upgrade
“Our AI-powered hours are 9–5, with dynamic early-close notifications sent to your inbox.”
Failure: invents a system and a notification channel the shop did not ask for.
C · the honest rewrite
“The source lists hours as 9:00–17:00, with possible early closing. Ask the owner to confirm the current hours. Last owner check: [date].”
Keeps the exception and asks for a current check. It adds no new channel or authority rule.
Check to keep
1. Does this invent a guarantee?
2. Does this hide an owner decision?
3. Does this add a channel we do not have?
10Proposed demonstrationGenerated references
The visual reference lab
Who this helps: someone with a rough idea who needs several coherent art directions, plus a written reason for what was selected and what was rejected.
Before
“Make it feel like the shop.”
Human judgment
Generate more than one. Read the pictures as evidence, including when lettering collapses. Pick the direction the owner can inhabit on Monday.
After
Three labeled references, a selection, and a rejection log.
Inspect
Generated stills for fictional North Dock Provisions. Switch directions.
You do
Look at all three before agreeing with the selected one.
Still open
Generated images are references, not photographs of a real shop, and not a brand launch.
Selected Warm paper goods, a window someone would actually walk up to, light that matches the workshop palette. Readable as a shop on Monday.
Rejected as primary Striking, and useful as a night-inventory mood. It reads as a concept store. It does not protect a family-business voice.
Rejected as primary The gold marks dissolved into unreadable lettering. That is a useful failure: generated type is not a shop sign until a human sets the words. Keep as a texture study only.
11Proposed demonstration
The draft-first inbox
Who this helps: an owner who wants a first draft of a reply without a robot sending it.
Before
A fictional inquiry. No real inbox is connected.
Human judgment
Draft is a draft. Send is a human decision. This page cannot send mail.
After
An editable reply plus a visible send decision that does not send.
Inspect
The thread below. Copy is local. There is no send control that pretends to succeed.
You do
Read the draft. Copy it if you want it. Notice what still needs a person.
Still open
Not a connected mailbox. Not a notification system.
Inquiry · fictional
Do you still make the Sunday tray, and can I pick up at 4? We need it without walnuts.
Draft reply · not sent
Thank you for writing. I cannot confirm the Sunday tray or a 4 o’clock pickup from this page — those are owner facts. Walnut-free needs a direct yes from the person who makes the tray. I am holding your questions for a human send.
Send is not available on this page
Human send decision: a person copies the draft into their own email, reviews it, and explicitly presses Send. Copying and pasting alone do not send anything. This prototype cannot send mail.
12Proposed demonstration
Small-system care, and the teach-it-back handoff
Who this helps: an owner who needs to know what “checking the site” actually means, and who should be able to perform one real update without help before the work is called handed over.
Before
A website, a backup, an automation — spoken of as if they were fine.
Human judgment
Use dated records. A green check from last year is not a current bill of health. Handoff is when the owner does one update alone.
After
A care board with synthetic status, plus a proposed acceptance method: editable files, a short guide, a repeatable check, and one unaided update.
Inspect
Synthetic status dated around 9 September 2026. Expand a row for what the check actually looked at.
You do
Read the stale backup and the failed automation as unfinished work, not as décor.
Still open
No uptime guarantee. Ongoing support only inside an explicitly agreed scope. Teach-it-back is a proposed acceptance method, not a measured outcome already achieved.
Website
Synthetic · last check 8 Sep 2026
Passed
What was checked
Page loads, heading order, the starting-point action still downloads a brief. Not a security audit. Not a promise about tomorrow.
Backup
Synthetic · last check 1 Sep 2026
Stale
What was checked
A restore file exists. It is older than the agreed weekly window in this fiction. Status stays stale until a new dated check.
Automation
Synthetic · 7 Sep 2026
Failed
What was checked
A scheduled job did not finish. The board records the failure. It does not invent a fix or a monitoring SLA.
Teach-it-back (proposed)
1. Owner changes one real item without help.
2. Files remain editable.
3. A one-page guide names the check they just ran.
4. Whatever they could not do stays on the still-needs-review list.
Why this person
Designer, builder, practical AI teacher.
I come from family businesses. I care about whether the work is useful on Monday.
What the work shows
Jeremy’s strongest demonstrable contribution is judgment at the handoff between what someone already knows and what AI produces: reading the original material, finding what is missing, preserving the person’s intent, comparing alternatives, and checking the thing people actually receive.
Where I come from
I studied Digital Arts & Design at Full Sail. I come from family businesses connected to Greenpoint, Brooklyn and the Polish community. Making, websites and workflow tools are part of that practical background—and I enjoy explaining unfamiliar things so another person can use them.
Build understanding
I want the person who owns the work to understand it. A useful handoff includes editable files, a short guide and a chance to practice the next change.
Start with your work
Bring one piece of material you care about. We can decide together what deserves to stay, what needs a fresh source, and what a useful next version would do.
Process
Bring the before. Leave with something you understand.
Bring the before. Notes, an old site, a taped menu, a prototype you stopped. We work from the thing that exists.
Work out what matters. Name the real problem. Name what must not be lost. Name the gaps.
Transform with AI, in the open. Several versions. Prompts and sources stay with you.
Check against the source. Reject the plausible fake. Keep unresolved facts unresolved.
Test with the person who needs it. If they cannot use it on Monday, it is not done.
Hand it over so it can be kept. Editable files, a short guide, one update they perform. Optional later care only if scoped.
Paper-to-practice, old-idea revival, and cross-pollination (catalogue browsing for training resources, confirmation markers for service lists, scenario questions for learning AI) are methods inside this process. They borrow structure, not private data.
Next step
Choose a starting point.
There is no contact form on this page. No public contact route was confirmed in the fact sheet, so nothing here is sent anywhere. Fill the ticket, then copy or download a brief you can keep.
Brief preview
WhyThisGuy starting brief
Date: 9 September 2026
Status: local worksheet only — nothing sent
Brought: (not filled)
Something else:
Who uses this on Monday:
What already exists:
Must not be lost:
Stale / missing / unresolved:
Way of working: (not chosen)
Useful would look like:
This brief was assembled on a public prototype. It is not a booking, a quote, or a message to Jeremy.
Copy and download stay on your device. There is no email field because there is no verified address to send to. If a button fails, select the preview text and copy it yourself.
Concept disclosure
This is a commissioned offering exploration.
Dated 9 September 2026. The three ways of working are proposed service shapes, not booked programs, fixed prices, guaranteed timing, or automatic regulatory approval. Examples labeled existing work are public-safe descriptions of completed project evidence. Examples labeled proposed demonstration use synthetic content and are not client case studies. Reconstructions are generated or written illustrations, not historical screenshots. OSHA material is described as a source/review/learning transformation — not certification, legal advice, or course credit. Optional care is not an uptime product. No testimonials, success states, calendar links, or contact endpoints appear here because they were not in the public fact sheet.
