Positioning pass: lead with the fork(2) a-computer-per-agent hook and the microVM-by-default wedge

[stubbi]

Context

The deep-research pass validated two things: "a computer per agent" is the category narrative, and the fork(2) system-call metaphor is the single proven device for making fast forking instantly graspable. Our closest competitor is Daytona, whose default isolation is a container and whose parallel-fork API is still partly roadmap. We should sharpen the site to lead with the fork(2) hook and the microVM-by-default, live-fork-today wedge.

Deliverable

• A messaging pass across the homepage and key pages: lead with the fork(2) "a computer per agent" hook; state the microVM-by-default wedge vs container defaults; keep the OSS + self-host + k8s-native quadrant explicit.
• A one-line "point your agent here" hook for a developer who has never heard of the category.
• Avoid jargon that does not land; keep "sandbox," "fork," "fan-out," "a computer per agent." No em or en dashes.

Links

• Relates: website Messaging: make security/isolation a first-class pillar (without losing the fork/swarm lead) #27 (security as a pillar, closed), Pull the ~27ms proof number into the hero #13 (27ms in the hero, closed).
• Informs all use-case and integration copy.

Done when

• The homepage and primary pages lead with the validated hook and wedge.