Files

T

TirsvadandClaude Sonnet 5.5 fa3beaf1c1 Point commit links at the pushed planning commit

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

2026-10-05 12:32:32 +08:00

1.6 KiB

Raw Blame History

System Sequence Diagram

Metadata

Key	Value
ID	SSD-001
CrossReference	UC-001

Version History

Date	Status	Author	Reviewer	Change	Commit
2026-10-05	Proposed	Jens Tirsvad Nielsen	S02	Initial version	424f14f

Source Use Case

Create a new project (UC-001) — scenario: main success scenario

Diagram

@startuml
actor Maintainer as A
participant ":System" as S
A -> S : startProjectCreation()
S --> A : prompts for project details
A -> S : provideProjectDetails(name, description, visibility, githubOwner, giteaOwner, directory, enablePlanGate)
S --> A : checks passed
S --> A : creation summary
@enduml

System Operations

Step	Message	Parameters	Return	Use case step
1	startProjectCreation	none	prompts for project details (after configuration and tool checks)	1, 2
2	provideProjectDetails	name, description, visibility, githubOwner, giteaOwner, directory, enablePlanGate	checks passed, then a creation summary	3 to 10

Steps 4 to 9 are internal to the system, so one operation covers them. A consent question (step 8a, 9a, 9b) is a prompt from the system and is out of scope for this diagram; failure flows are out of scope here.

Lifecycle Notes

The system is one script run. It starts with the first operation and ends after the summary; nothing persists between runs.

1.6 KiB Raw Blame History