Daeseon Yoo
Back to project
·Update·2 min

Architecture deep-dives for 4 more projects — source-verified, adversarially checked

Fanned out the architecture deep-dive surface (piloted on talkak) to Mimi, DocVault, Beside, and ScreenBridge. Each was extracted from the actual local repo by an analyze → adversarial-verify → write pipeline; the verify pass cut or corrected a real wrong number on every project before it shipped. Every claim cites real files; every number is measured. EN now; the loader falls back to EN for KO until KO versions are written. ScreenBridge and Meta-Smart-Glass: ScreenBridge done; Meta hit a rate limit mid-run and is the one remaining.

What I did

Each project's /projects/<slug>/architecture page now carries a source-verified deep-dive in the same shape as the talkak pilot: a measured-metrics table, a request-path mermaid diagram, the core mechanisms with the real file names inline, and an honest "what this doesn't do" section.

How it stayed honest

Each project ran through analyze → adversarial verify → write. The verify stage re-opened every cited file and re-ran every measurement, and it caught a real error on every single project:

These are exactly the numbers an engineer reading the repo in an interview would have caught. Better the adversarial pass caught them first.

What's left

Verified by

npm run build clean (all /projects/[slug]/architecture routes prerender, no MDX crash from the generics/diagrams); on a fresh local server all five architecture pages return 200 and the project pages now show the "Architecture →" link.

Commit

69e91ab