Blog
The blog is the short public record for why the vespid project is taking its current shape and what architectural decisions matter before the prototype grows more surfaces.
The current vespid context
These posts explain why the public site now focuses on the vespid repository and why the project keeps ordinary HTTP ahead of adapter-specific product surfaces.
Why the site now centers on vespid
Read this first if you want the public-site decision and what changed in the narrative layer.
Why ordinary HTTP comes before adapters
Read this if you want the design reason behind the HTTP-first, contract-first posture.
Move to the docs
Use the docs when a lesson becomes stable enough to guide future work on the prototype.
Open vespid first if a post depends on actual repository scope or trust-boundary assumptions.
Use Documentation when a post becomes reusable guidance instead of historical context.
Move back to the repo when the question is about code, tests, or runtime behavior rather than public framing.