Karpathy coined it this month and the industry immediately confessed by adoption: “VIBE CODING” — describing what you want in natural language, accepting what the model writes, iterating by feel, “forgetting the code even exists” — and the term’s instant ubiquity is the #242 two-year review’s (#290) missing data point arriving as slang: a meaningful fraction of new software is now being written by people supervising rather than typing, and the file’s dual ledger opens accordingly: the DEMOCRATIZATION is real (our marketing team shipped an internal tool last sprint; the #010 feature-flag wonder of 2013 is now available to anyone who can describe a spreadsheet), and the ENGINEERING ledger is exactly the #268 curriculum bet’s terrain — the gap between “it runs” and “it’s sound” (security, edge cases, maintenance) is invisible precisely to those newest to it, and the #251 review-first pedagogy just became the industry’s general problem (the file pre-registers the sequel: 2025-26’s incident reports will grow a “vibe-coded and unreviewed” category, and the orgs that built judgment infrastructure #260 will grade the difference — the ladder question #250, now economy-wide).
Anthropic shipped CLAUDE 3.7 SONNET Monday (the first “hybrid reasoning” release — extended thinking as a togglable budget rather than a separate model, the #285 two-axis doctrine collapsing into one dial, plus a coding-agent harness that the #291 sequence-reliability file will be grading all spring), with GPT-4.5’s launch reportedly tomorrow (the counter-programming calendar #291 never rests); and the crypto file logged the largest theft in history almost as routine: BYBIT, $1.5 BILLION in ETH, February 21st — Lazarus again (#225’s franchise, compounding), via compromise of the multisig SIGNING INTERFACE (the signers approved what they saw; what they saw wasn’t the transaction — the #226 Atlassian-deletion lineage arriving at the wallet layer: the UI is part of the cryptographic trust chain, and it was the unaudited part). The #240 proof-of-reserves era’s grim maturation: the exchange survived (reserves real, withdrawals honored, industry bridge loans within hours — the #230 lessons genuinely learned), and the state-actor treasury-heist economy now funds itself at nine figures per incident against interfaces, not protocols (#210’s forged-sword file: the sword was in the SIGNING SCREEN this time).
The fortnight’s quiet governance ledger: the #294 TikTok suspension holds in its legal twilight (enforcement waived, buyers circling, the law upheld-but-dormant — the file’s strangest open docket), Meta’s Community-Notes transition (#293) began US rollout, and our own #295 portfolio committee added its first formal “model-provenance” criterion (training-data jurisdiction and weight-custody questions now sit in procurement alongside SOC 2 — the #295 weights-as-border-artifact doctrine, arrived at the purchasing layer; the #275 dependency-tiering RFC’s AI appendix writes itself).
TIL: multisig UI attack surfaces — blind-signing mitigations (hardware-display verification of full transaction payloads, not hashes; the “what you sign is what executes” gap as THE custody frontier). Twelve years of this archive’s security files reduce to one migrating sentence: the vulnerability is always in the layer everyone assumed someone else audited (#031 the cert, #218 the logger, #274 the maintainer, #282 the channel file, #296 the signing screen — the sentence never changes; only the layer does).