1The chain — what happens when you type a prompt

Every prompt walks the same five hops. The first three live in the cloud and are always reachable; the last two run locally on M5 (this machine) where Photoshop lives.

2What gets produced — the four file tiers

Each render generates four artifacts. You only need the first two. The PSD and TIFF exist as the AI's audit trail and for the rare moment a print shop demands them.

3What runs cloud-side — works without M5

• Chat / vision Q&A about images — Bedrock looks at any photo, answers questions, suggests edits. No daemon required.
• Queueing edits — prompts wait in S3 until M5 wakes. Queue an edit from your phone; M5 picks it up next time it's online.
• Render history — every prior run lives in S3 forever. The 🗂 pin opens the full archive.
• Knowledge Base lookups — house style, prior render specs, founder-profile color directives. Bedrock pulls from KB 0FPTYLESU4 automatically.

4What runs on M5 — your CC subscription powers this

• Actual Photoshop execution — Liquify, Neural Filters, Camera Raw. The CC subscription on walterlambertj92@gmail.com is what makes the AI's edit decisions land as real pixel changes.
• Source RAW / master files — ~/Desktop/Revasser-SOU/. Originals never leave the machine.
• Render daemon — LaunchAgent nyc.revasser.editorial-render-daemon. Polls S3 every 20s, runs the render, uploads results.

5Permanent home

6Prompt vocabulary — what the chat translates for you

Type the left side. The chat looks at the image, derives the right side, and queues the render. You don't have to learn the lexicon — the translation is the product. The right column is shown so you can verify the model picked the right deltas, not so you have to type them.