System / Service Story

Short Description.

Notes & Guidelines

• File name: ss-0001-template.md
• Focus on system / service behavior
• Include inputs, outputs, and interactions
• Keep it concise and testable

1. Story

As a <system / service / actor> I want <process / operation / behavior> So that <system-level outcome / integration / automation>

2. Inputs / Triggers

• Input 1: <data, event, API call, etc.>
• Input 2: …
• Input 3: …

3. Outputs / Results

• Output 1: <expected result / response>
• Output 2: …
• Output 3: …

4. Acceptance Criteria

• AC1:
• AC2: …
• AC3: …

5. Context / Notes

• Relevant constraints or requirements
• Dependencies on other systems/services
• Additional technical info, diagrams, or links