Give agents a system, not a blank canvas
Why bounded choices, generated contracts, and actionable validation make agents more useful website collaborators.
Field notes on building websites as systems.
The product principles are practical: constrain the right surface, make every capability visible, keep content portable, and let tested behavior improve more than one page.
The thinking behind the contracts
These articles are themselves collection-backed Sights content: typed records, local media, templated routes, sanitized Markdown, and generated Article metadata.
Static-first is operational design
Static output is not nostalgia. It is a deliberate reduction in runtime surface, deployment coupling, and hidden failure modes.
Component contracts compound
A component becomes infrastructure when its schema, guidance, examples, semantics, runtime, and tests travel together.
See the product principles operating on this site.
The platform pages connect each belief to a concrete content, component, theme, delivery, quality, or extension contract.