{
  "id": "vapor-wares-speedrun-media-kit",
  "version": "v000_001_000",
  "campaign": "a16z Speedrun SR007",
  "product": "Vapor Wares",
  "headline": "AI-native work needs a storefront.",
  "oneLiner": "Vapor Wares is the Mac-first storefront for AI-native work.",
  "demo": {
    "title": "Vapor Wares makes AI-native work inspectable before it runs.",
    "targetRuntimeSeconds": 75,
    "hardCapSeconds": 90,
    "shotList": [
      "Open Vapor Wares.",
      "Show the storefront: app shelf, launch packet, runtime services.",
      "Open Content Pass/capability shelf: tools, docs, domain packs, receipts.",
      "Show a ware detail: privacy, support, appcast, release status.",
      "Open Release Calendar.",
      "Show Speedrun SR007 gate: demo URL, public pages, X, Reddit, proof links, submission receipt.",
      "Show Stacks/Today as the executable workbook pattern.",
      "End on the thesis: visible capabilities before the agent runs, receipts after it finishes."
    ],
    "voiceover": [
      "AI work starts in a prompt box, but the work depends on much more than a prompt: tools, apps, docs, permissions, release flags, privacy posture, and proof.",
      "Vapor Wares is a Mac-first storefront for that world. It shows the capabilities a workflow can rely on before anything runs.",
      "This shelf can hold apps, CLIs, docs, domain packs, and executable workbooks we call Stacks. Each ware carries receipts: what it installs, what it trusts, how it ships, and what gates are still open.",
      "The release calendar is the pressure surface. It shows feature flags, privacy and support posture, public proof links, demo readiness, and submission state.",
      "Underneath, wrkstrm-core turns intent into a session formula: runtime, tools, permissions, memory policy, and verification gates.",
      "The idea is simple: agent-native work should be visible before execution and provable after it finishes. Vapor Wares is the storefront for that."
    ]
  },
  "launchThread": [
    "We are building Vapor Wares: a Mac-first storefront for AI-native work. The premise is simple: before an agent runs, you should be able to inspect the tools, docs, permissions, release gates, and proof receipts it depends on.",
    "Today most AI work starts in an empty prompt box and immediately becomes hidden state: terminal output, files, tool calls, generated assets, decisions, and receipts. That state deserves a product surface.",
    "Vapor Wares makes capabilities visible as wares: apps, CLIs, Brew packages, SwiftPM binaries, docs, executable workbooks, domain packs, launch gates, and receipts.",
    "The first shelf is Content Pass. It shows what a workflow owns, trusts, recommends, and can attach before execution. Stacks are executable workbooks inside the shelf.",
    "The release calendar is the pressure surface. It tracks feature flags, privacy, support, distribution, public proof links, demo readiness, and submission receipts.",
    "The system behind it is wrkstrm: CLIA turns intent into a runtime formula, and wrkstrm-core makes the formula checkable with tools, permissions, memory policy, and verification gates.",
    "Vapor Wares makes AI-native work inspectable before execution and provable after it finishes. Demo: [DEMO_URL] Product: [VAPOR_WARES_URL]"
  ],
  "redditDraft": {
    "title": "I am building a Mac storefront for AI-native work, because prompt boxes hide too much setup state",
    "body": "I am working on Vapor Wares, a Mac-first storefront for AI-native work. AI workflows depend on a lot of hidden setup: apps, CLIs, docs, permissions, local files, release flags, domain packs, and proof artifacts. Vapor Wares shows those dependencies as wares before the agent runs and keeps receipts attached after it finishes. Would you use a local shelf that shows what an AI workflow can rely on before it runs, and what receipts prove after it finishes? Demo: [DEMO_URL] Product page: [VAPOR_WARES_URL]"
  },
  "ads": [
    {
      "name": "Founder feed",
      "headline": "Stop launching agents from invisible setup.",
      "body": "Vapor Wares is a Mac-first storefront for AI-native work. Inspect tools, docs, permissions, release gates, and proof receipts before an agent runs.",
      "cta": "Watch the demo."
    },
    {
      "name": "Builder feed",
      "headline": "Your AI workflow has dependencies. Show them.",
      "body": "Apps, CLIs, docs, domain packs, feature flags, privacy posture, and receipts belong on one shelf. Vapor Wares makes them inspectable.",
      "cta": "Open Vapor Wares."
    },
    {
      "name": "Speedrun",
      "headline": "Agent-native work needs a storefront.",
      "body": "Vapor Wares makes AI-native work visible before execution and provable after it finishes.",
      "cta": "See the launch packet."
    }
  ],
  "letters": [
    {
      "name": "Warm intro",
      "subject": "Vapor Wares, our Speedrun application",
      "body": "Hi [Name],\n\nWe are applying to a16z Speedrun with Vapor Wares, a Mac-first storefront for AI-native work.\n\nThe short version: AI work depends on hidden setup. Before an agent runs, a builder should be able to inspect the tools, docs, permissions, release gates, and proof receipts the workflow relies on. Vapor Wares turns those dependencies into visible wares and keeps the receipts attached after the run.\n\nHere is the 90-second demo: [DEMO_URL]\nHere is the product page: [VAPOR_WARES_URL]\n\nIf this resonates, I would be grateful for a quick reaction or a warm pointer to someone who thinks deeply about agent-native developer workflows.\n\nThank you,\nCristian"
    },
    {
      "name": "Reviewer follow-up",
      "subject": "Vapor Wares proof packet",
      "body": "Hi [Name],\n\nSharing the Vapor Wares proof packet ahead of submission.\n\nThe application thesis is: AI-native work should be inspectable before execution and provable after it finishes. Vapor Wares is the Mac-first storefront for that surface.\n\nLinks:\n- Demo: [DEMO_URL]\n- Product page: [VAPOR_WARES_URL]\n- Launch packet: [LAUNCH_PACKET_URL]\n- GitHub/proof: [PROOF_URL]\n\nThe main thing I would love feedback on is whether the product is legible in the first 30 seconds.\n\nCristian"
    },
    {
      "name": "Design partner",
      "subject": "Can I show you a Mac app for inspecting AI workflow setup?",
      "body": "Hi [Name],\n\nI am looking for 2-3 design partners for Vapor Wares.\n\nIt is a Mac-first storefront for AI-native work. Instead of launching an agent from a blank prompt and hoping the setup is right, Vapor Wares shows the capabilities, docs, permissions, release gates, and proof receipts attached to a workflow before it runs.\n\nIf you regularly build with ChatGPT, Codex, Claude, local repos, CLIs, and native apps, I think you are exactly the person I need to learn from.\n\nCould I send a 90-second demo and ask for your blunt reaction?\n\nCristian"
    }
  ]
}