Skip to content
Quickstart

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.

2 published posts The blog stays small on purpose so each post explains a decision that affects the current public prototype.
1 public repo Every post should point back to the same repository and the same HTTP runtime assumptions.
2 adjacent hubs Project and docs are the neighboring reading paths when a post needs implementation detail or stable reference.
Reading path
Start with the project

Open vespid first if a post depends on actual repository scope or trust-boundary assumptions.

Then use the docs

Use Documentation when a post becomes reusable guidance instead of historical context.

Then return to implementation

Move back to the repo when the question is about code, tests, or runtime behavior rather than public framing.