Files

T

TirsvadandClaude Sonnet 5.5 02875aee5f Accept planning baseline and UC-001 artifacts

Add the Use Case Diagram, Domain Model (use case and project), Dictionary,
Operation Contract, Sequence Diagram, review records RC-001 to RC-015 and
the Traceability Matrix. Split US-001 into one story per milestone, make
GitHub optional (AGPL license applied when chosen), and accept BC-001,
SA-001, PP-001, UCD-001, US-001, UC-001, SSD-001, DM-001, DM-002, OC-001,
SD-001, DICT-001 and MIL-001 to MIL-003 after review.

Refs: no issues synced yet (sync-project.sh dry run only)

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

2026-10-05 13:41:36 +08:00

1.9 KiB

Raw Blame History

System Sequence Diagram

Metadata

Key	Value
ID	SSD-001
CrossReference	UC-001, DM-001, OC-001

Version History

Date	Status	Author	Reviewer	Change	Commit
2026-10-05	Rejected	Jens Tirsvad Nielsen	S02	Initial version	424f14f
2026-10-05	Accepted	Jens Tirsvad Nielsen	S02	Optional GitHub; choosing GitHub applies the AGPL license to the Gitea repository Cited OC-001 and DM-001	pending

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, giteaOwner, githubOwner, 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, giteaOwner, githubOwner (optional; given means GitHub is chosen and the Gitea repository gets the AGPL license; omitted means no GitHub and no license), 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.9 KiB Raw Blame History