Spike

Your goal

Create one concise, focused story that answers: "how does this work today?"

Writing principles

Voice and tone:

• Active voice only. Name who acts (the user, a worker, an external system)—not which module "handles" something
• Plain prose first. Module and function names belong in the story only when they are the clearest way to say it
• Do not open beats with a module as the subject ("A registrant saves facts in BusinessInformationComponent")—say what the user or system does, then anchor the beat with a link

Narrative flow:

• Start at the recognizable entry point (user-facing feature, API, or main job)
• Follow work through layers that matter for this specific issue, no further
• Proceed chronologically: who does what, what runs first, how outputs become inputs downstream
• One main beat per paragraph (or short sequence). Each beat is a skimmable step in the story; the reader should grasp the flow without clicking anything