Prototypes

This folder contains narrow Volume and Velocity prototype runs.

Each prototype should capture one concrete experiment, usually focused on proving a small part of the workflow end to end rather than designing the full system.

Typical examples:

  • one internal update turned into one publish-ready social post
  • one manual or semi-manual test of the fetch -> brief -> draft -> review flow
  • one validation run showing what worked, what broke, and what should happen next

Why This Folder Exists

The goal of these prototypes is to learn by shipping small working examples.

This is useful when:

  • a broad plan feels too abstract
  • the team wants evidence from a real workflow run
  • we want to reduce uncertainty before building more automation

What To Put Here

Each file in this folder should usually include:

  • the date
  • the goal of the experiment
  • the source material used
  • the exact brief or prompt used
  • the outputs generated
  • friction observed
  • what the run suggests for next steps

Naming Convention

Use simple date-first filenames, for example:

  • 2026-04-03-datahub-one-post-prototype.md
  • 2026-04-05-flowershow-linkedin-prototype.md

Current Prototype

Built with LogoFlowershow