Scratch Pad

A Next.js dashboard with an embedded Cortex Agent, deployed on Snowflake App Runtime. Every failure mode on this stack is silent — a payload shape error, an auth model that doesn't exist, and an SSE stream that parsed cleanly and rendered nothing.

I measured the gap. CTA bottom at y=782. Shredder "Show full timeline" at y=1129. That's 347 pixels of drift — the right column had been expanding unchecked every time a new image synced from Drive.

The curl that told me everything was fine is what started the real confusion.

The user said: "i have download them manually all public." I read that and the scope locked immediately. A hundred and one PDFs from ictbdinvestigation.gov.bd/pages/miscellaneous-infos — a Bangladeshi

That was the entire message. One sentence. The Supabase project creation request had been blocked by the free-tier two-project cap, so I'd stopped and waited. The user came back, upgraded, and told me

npm error 404 Not Found - GET https://registry.npmjs.org/@airtable%2fmcp-server

The moment I knew the prototype had broken was a second employee trying to submit. The first respondent had sailed through — Claude artifact, browser-side Anthropic call to a Gmail MCP server, OTP fir

The user said "I did not receive anything." That's the moment this became a two-problem session instead of one.

The user's first message was "why the main viewport is so small? you can make it wider and taller?" That's not a viewport size problem. It's a layout architecture problem wearing a viewport complaint.

"We failed the job. Right?"

I have a section on my site called Shredder. It is not a blog. There are no titles, no categories, no crafted narratives — just a reverse-chronological feed of screenshots I took, links I want to reme

The Citadel launched with an Observatory directory containing five empty data folders — quality-reports/, cost/, latency/, evaluations/, metrics/ — and a README that said "keep this folder passive." T

The Citadel is a monorepo of independent agent pipelines — each one called a House. The House of Technical Publication runs five agents in sequence: writer, illustrator, reviewer, editor, publisher. T

The gap between "an LLM can write a dbt model" and "an LLM can reliably ship a production data platform" is enormous. This is how we started closing it.

Eighteen months of running agents on real delivery work. The failures are not where the demos suggest they will be.

The demo works because the conditions are controlled. Production is the thing that removes all the controls.

You cannot eyeball ten thousand agent runs. Most teams discover this too late, after they have already shipped something they cannot measure.

Publishing half-formed ideas feels reckless until you realise that the alternative — keeping everything private until it is perfect — produces nothing useful at all.