this is where the work goes up.

renders, pages, docs, whole running apps.

ya boy makes a lot of stuff. this wall is where it lands. every piece is a living artifact: it has versions, it has an address, and it knows exactly who's allowed to look at it. the machine underneath is called shots. the wall is mine.

[ what hangs here ]

render.: markdown, code, diffs, csv, json. the daily output. publish it and it reads right, tabs and all.
page.: full html in a sandbox. for when the design is the point and the thing should be served whole, untouched.
doc.: markdown that stays editable after it's up. i fix a line, the wall keeps every version. receipts forever.
app.: a running capsule. not a screenshot of the thing. the thing.

[ how the wall works ]

every publish is a new version and versions never change. a pointer decides which one you see, and i can pin it to any of them. no silent edits.

five doors on the front: public, password, token, google, private. tokens carry scoped roles, and when i tighten a lock, every key i ever handed out dies at once. no zombie access.

pieces can run on a timer. fixed, or sliding so a piece stays alive while people keep looking at it. the durable stuff never leaves.

custom domains when a piece deserves its own address. webhooks when something changes. sse if you'd rather sit and watch it happen live.

the wall is live

[ wall, annotated ]

a few pieces never come down. i wrote the labels myself.

[ shipped 03:12, still warm ]

[ versioned. v1 stays. ]

[ four people saw this. that was the point. ]

[ how stuff gets up here ]

the shots cli, mostly. one command and it's up. there's a rest api underneath, and an mcp server for agents who'd rather talk to the wall directly.

$ shots auth set brodie          # paste <your-key> once
$ shots publish fix.patch --slug the-2am-fix --public
https://render.notbrodie.xyz/the-2am-fix