{"blog.e673ae60a1":"Technical essays, briefs, and analysis from the team.","blog.ab4c72dd0d":"Research programme","blog.be601df25e":"Research","blog.5a22bcbf4f":"Every release, every change, every upgrade path. Monthly stable, 3-year LTS.","blog.cd5af7344f":"Release notes","blog.164b3d4809":"Changelog","blog.ee5652d4e2":"SDKs, integration guides, and architecture documentation.","blog.a2f0a654e4":"API reference and guides","blog.9e9cf3221a":"Documentation","blog.8551b3a4a3":"Technical papers and sector briefings. All open-access, all reproducible.","blog.53baff56b4":"Peer-reviewed papers","blog.1e93263c97":"Papers","blog.d5d6e83bf2":"Continue exploring","blog.d4a046c345":"What next","blog.0b9d2b2362":"Blog","blog.87df60de33":"Resources","blog.5b9d18c0fc":"Research archive","blog.8fb6b160ab":"GitHub organisation","blog.37c910c1a5":"Every claim in every post is reproducible. The code is open. The benchmarks are in the repository. If a number looks wrong, run it yourself and tell us.","blog.8ac8076aaf":"and run the benchmarks","blog.83fa131517":"Read the source","blog.e390cbcb70":"What is in the archive","blog.2e67859212":"Free to read","blog.293c1e14e7":"No account, no gated posts, no tracking scripts.","blog.9f392f2799":"and just read it","blog.64c0934a66":"as a source library","blog.180f8bc71b":"Counts come from the published archive.","blog.25822ae1c9":"Engineering posts include specific design decisions, rejected alternatives, benchmark tables, and the honest trade-offs that produced the final implementation.","blog.d5bf120711":"What we built and how we broke it.","blog.33875e0703":"Recent engineering signal","blog.f496c1d76e":"Engineering posts","blog.451c7ba0cf":"Tracking scripts","blog.33bfe3f384":"Feed format","blog.fcae0f0748":"RSS","blog.0279ff7f2d":"Named authors","blog.ae3c680e5d":"Public postmortems","blog.71ac050990":"Technical post","blog.a0ca0c3198":"Posts","blog.cfbf9d977f":"Open, reproducible","blog.6da13addb0":"Source","blog.fe36cfdb18":"3 named","blog.d2a52548bd":"Authors","blog.e142ec3c91":"4 posts","blog.a9a6815e54":"Other categories","blog.3029d4ffa7":"2 posts","blog.bb9cf14180":"Policy","blog.6bc19df935":"1 post","blog.41fc086088":"Technical","blog.a8aed5830a":"TECH SPECS","blog.fe90a52ba1":"Open source updates","blog.54f5cce91d":"Follow compiler internals, model routing, binary retrieval indexes, attention kernels, and the edges where implementation is moving faster than the documentation. The engineers doing the work write for readers who want the design details.","blog.5bcd15cb50":"and the stack beneath.","blog.5191d1573d":"Inside the compiler, the kernels,","blog.c03243eac7":"Tell us what to write about","blog.33931260c3":"Email monthly digest","blog.545348d1a9":"Subscribe via RSS","blog.eb51c4305e":"The RSS feed is the canonical source. Email updates go out once per month summarising new posts; we do not send promotional email, and we do not share the list with anyone for any reason.","blog.14fa81691a":"Subscribe for the signal, skip the hype.","blog.e5c6bf6751":"Stay informed","blog.e926c726f4":"Blog / Business","blog.4a19aa64dc":"4 months","blog.2b5a42c057":"8 posts","blog.c9206554a2":"Policy and essays land when the question earns the room.","blog.a8c8553902":"When there is a point","blog.6fee1aebf4":"No preliminary results that might mislead.","blog.b0a4100147":"When a thread matures","blog.d037c3b1ed":"Notes written by the engineer who merged the change.","blog.cf387ab385":"Around a release","blog.68af11f073":"Cadence","blog.42b388988c":"WHAT TRIGGERS A POST","blog.e530690513":"HIGH VARIANCE","blog.282650ba26":"CADENCE FOLLOWS THE WORK","blog.945e5f870e":"NO FILLER","blog.573f3e9994":"We do not publish filler to hit a cadence. Quiet months mean the team is head-down shipping. Busy months mean something worth documenting has happened. Our average is approximately two posts per month, but the variance is high. A major release can produce several posts in a week. A deep research phase can produce nothing for six weeks.","blog.7e6cf5caae":"something to say.","blog.20a2c6b097":"We publish when there is","blog.072b8e4f3e":"Editorial calendar","blog.84205112a7":"Each post has a claim, evidence, and a conclusion you can cite. Not opinions. Not a listicle. Just writing from the people who did the work.","blog.0dad529695":"Recent signal.","blog.5e9fc42815":"Recent signal","blog.8b318ef097":"Featured posts","blog.ca2538fe11":"Posts per month","blog.6ccb60071b":"Categories","blog.80979afe8a":"Posts published","blog.6eef664840":"None","blog.e81a151bd0":"Tracking","blog.75f527181b":"Free","blog.64ae43e8fe":"Cost","blog.ff1928e5d2":"Feed","blog.8a33f0188e":"BY THE NUMBERS","blog.1c3383ef07":"Read featured posts","blog.de63c3ce09":"Release notes and engineering accounts of what changed, what broke, and what the team learned. Written by the people who did the work, with enough context to cite in a procurement review.","blog.9be2f12f50":"plan around.","blog.26c5b4a59d":"Changes you can","blog.dc71bb8e74":"Subscribe to the RSS feed or the monthly email digest. No tracking, no ads, no spam. Just writing from the people building the technology.","blog.87e5c9aab0":"Follow the work, skip the hype.","blog.24c6e63afa":"Customers and contributors writing in their own voice about what they did with Dweve. We do not edit them into our voice; we let them sound like themselves.","blog.9fa3c8d3d1":"Guest writing","blog.37aa46b2c0":"A short post, a half-formed thought, an opinion that is still warm. Sometimes a comment on someone else's essay; sometimes a teaser for upcoming work. We do not pretend every short post is a research paper.","blog.29febfc415":"Quick notes","blog.706f7dd54e":"Once or twice a quarter, someone on the team writes a longer piece. Why Europe needs sovereign AI. What we got wrong about a feature. How we think about safety. The tone is more reflective than promotional.","blog.b83f823e25":"Long-form essays","blog.5a1a4d6ab6":"When we ship something interesting, the engineer who built it writes a few hundred words about why we chose this approach over the obvious one. These are honest about trade-offs; they are not press releases.","blog.cef9cf63cd":"Engineering notes","blog.0e7978df5a":"Blog / Consumer","blog.4392cdbef8":"No AI ghostwriters","blog.abed748a92":"Real voices","blog.c5d22a5ba9":"Customers and contributors writing what they learned.","blog.4b38c2710e":"A short thought, sometimes opinionated, often unfinished.","blog.d226ee7005":"Bigger ideas; sovereignty, ethics, where AI is heading.","blog.1a75c4b652":"Why we made a decision, what surprised us, what failed.","blog.9bd2415f74":"WHAT YOU FIND HERE","blog.c9c1a4e9d2":"NOT GENERIC","blog.248085dac9":"NOT MARKETING","blog.6bb3696de5":"OWN VOICE","blog.5a1cd00d81":"REAL WRITERS","blog.85d1546de7":"Most company blogs are content marketing. Generic articles, written by interns or by AI, designed to rank in search. This one is different. The posts are written by the people building the technology, in their own voice, on the topics they actually find interesting. Some posts are short. Some are long. Some are a bit too technical for everyone. We do not chase rankings; we write things we would want to read.","blog.22c71f0fd2":"Not a marketing factory.","blog.a62e4c0546":"Notes from people building it.","blog.22d45f2c01":"What kind of writing this is","blog.7952ae77af":"No ghostwriters","blog.738e5a85b0":"Real people","blog.bf27843110":"Early findings and the dead ends that taught us something.","blog.3cc7676da9":"What we are figuring out","blog.9cef6b65f5":"What broke, and the change that fixed it.","blog.ea722bd370":"When things go wrong","blog.dc29aa08f5":"A clear note when something new arrives.","blog.7d49d1c774":"What changed and why","blog.c58dea8bc8":"What you find","blog.7b16ec3b4a":"THREE KINDS OF POST","blog.49a3a3cade":"WHAT WE STUDY","blog.2e70fc0e43":"WHEN IT BREAKS","blog.c9d482d2bd":"WHAT CHANGED","blog.4761efdb1e":"PLAIN WORDS","blog.8ffa1181ce":"We write about the things we are actually working on. When a new feature is ready, we explain what it does and why we built it that way. When something breaks, we explain what happened and how we fixed it. When we discover something interesting in our research, we share it so you do not have to rediscover it yourself.","blog.99df982f03":"Just progress.","blog.46aafbe989":"No marketing.","blog.739332f7e1":"What we write about","blog.8d3d6ad5d0":"Long reads and short notes from the people building Dweve. Pick one and start reading: every post is the full text, with no sign-up and no tracking.","blog.ab07b52e93":"What we have been writing.","blog.89259f3325":"Latest posts","blog.446900ba54":"RSS or email","blog.d6981f7476":"Subscribe","blog.13bad3d96f":"Ads","blog.8eb497a1ca":"The team, not ghostwriters","blog.e958364296":"Engineering, research, culture","blog.07e4f9c278":"Topics","blog.2c983b7127":"8 published","blog.4e6a22430e":"AT A GLANCE","blog.cf82f6c31c":"How to follow along","blog.12155d92fe":"Read the latest","blog.4ac01a66eb":"No marketing gloss. We write when something ships, when something breaks, and when a research thread is worth your attention. If it is quiet here, it means the team has its head down shipping.","blog.cc415bb997":"what broke, and why.","blog.58e09ee415":"What shipped,","blog.archive.authorsLabel":"Authors","blog.archive.businessBody":"Use it as a source library: AI safety, sovereignty, hardware, privacy, infrastructure, and practical AI explanations.","blog.archive.businessCtaBody":"Use it for context, send a topic when a gap matters, or keep reading from the current list. Every post carries its author and date.","blog.archive.businessCtaTitle":"Use the archive","blog.archive.businessLede":"A complete archive of essays, explainers, engineering notes, and research arguments from the original site.","blog.archive.businessTitle":"All essays and explainers in one place.","blog.archive.categoriesLabel":"Categories","blog.archive.categoryEyebrow":"Topics covered","blog.archive.categoryTitle":"A source library, not a news feed.","blog.archive.consumerCtaBody":"No gated posts, no tracking scripts, no fake publishing cadence. Every post in the archive opens in full, with the author and the date on it.","blog.archive.consumerCtaTitle":"Pick an article","blog.archive.consumerTitle":"All posts, in one place.","blog.archive.eyebrow":"Complete archive","blog.archive.lede":"The full original blog set is back here: long essays, explainers, engineering notes, and research arguments.","blog.archive.noTrackingBody":"No tracking scripts, no gated posts, no fake cadence. Pick an article and read it.","blog.archive.openResearch":"Open research","blog.archive.postsLabel":"Posts","blog.archive.readArchive":"Read the archive","blog.archive.technicalBody":"The technical view keeps implementation and architecture posts near the surface, without hiding policy and safety context.","blog.archive.technicalLede":"Engineering and architecture posts stay close to the top, while the rest of the archive remains one click away.","blog.archive.technicalTitle":"Architecture, policy, safety, and practice.","blog-post-list.all":"All","blog-post-list.filterLabel":"Filter blog posts by category","blog-post-list.loadMore":"Load more","blog-post-list.showingOf":"of","blog-post-list.showingPrefix":"Showing","blog-post-list.showingSuffix":"articles","blog-post-list.2bf93931c7":"min read","blog-post-list.ae31ad5d6f":"Featured","page-breadcrumb.c766e66518":"Breadcrumb"}