Astro content collections
ENGTyped Markdown with build-time validation. The schema catches bad frontmatter before a deploy, not after.
Radar
A deliberately short list of tools, patterns and risks worth a decision. Rings describe maturity, not enthusiasm. A blip moves when the evidence changes.
Proven in production. Use it unless you have a specific reason not to.
Typed Markdown with build-time validation. The schema catches bad frontmatter before a deploy, not after.
Vendor-neutral traces, metrics and logs. Instrument once; change backends without rewriting the app.
Static full-text search that ships as small per-page chunks. No search cluster, no API key, no runtime.
Worth using on a real project, with an exit plan.
Generate share cards at build with Satori. One design, zero runtime, no per-post cover art.
Kernel-level detection without a sidecar per pod. Strong signal, but tuning alerts is real work.
A policy and audit point between agents and tool servers. Useful, but the auth model is still settling.
Promising, but the operational cost is not settled yet.
Isolated execution for tool-using agents. The right idea; the escape hatches and snapshot story are immature.
Hybrid key exchange is deployable now. Certificate migration is the long pole, so inventory matters more than the cipher.
Avoid for new work until the risk or the ecosystem changes.
A system prompt is not an authorization boundary. Pair policy with deterministic checks and least-privilege tools.
Tags are mutable. A compromised action tag is a supply-chain path into your deploy. Pin to a commit SHA.
How to read this
Radar is a decision aid, not a ranking. “Adopt” means the operational cost is understood. “Hold” means the risk outweighs the benefit for new work right now. Every entry links to the primary documentation so you can disagree with the placement.