Hypothetical creation brief for this authored edition, not a historical prompt transcript. The sample answers describe the actual example rendered here.
- Purpose and audience
- Launch a product with a concrete preview, use cases, and meaningful FAQs.
- Working context
- Fieldnote is a fictional project notebook for small teams. This example demonstrates the product story and a preview of its core workflow; product capabilities and availability are illustrative.
- Example records
- Moment: Start · What you do: Write a one-page brief · What stays visible: Goal and constraints
Moment: Work · What you do: Add a weekly note · What stays visible: Progress and blockers
Moment: Decide · What you do: Record the choice · What stays visible: Reason and owner
- Content decisions
- See the first project: A café website starts with the five pages it needs. The weekly note identifies the missing menu copy. The decision log records why online ordering is outside the first release. Each piece links back to the same brief.
Who it helps: Teams with a few concurrent projects and a named owner for each one. A readable project record can help collaborators join the conversation without searching through a long message history.
Before you join: In a real launch, replace this section with verified availability, plan details, data handling, and a working sign-up destination. This sample has no sign-up form and makes no promise about a live service.
- Format and interaction
- feature layout; section navigation and expandable detail where useful; matching portrait document PDF.
- Sharing and provenance
- A hypothetical example informed by Claw Me’s small-team and Agent workflows. These are not Pete’s actual clients, finances, travel plans, research results, or commitments. Keep the real adaptation private until the owner chooses to share.