Architecture: the general scope and the new-project sequence (for M2.5) #104

Merged
dongar merged 2 commits from arch-general into main 2026-10-06 00:29:49 +00:00
2 Commits
Author SHA1 Message Date
dongarandClaude Opus 5.5 b78fd58c85 general never gets a build VM: an experiment means starting the project
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 3m44s
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE
2026-10-06 00:22:02 +00:00
dongarandClaude Opus 5.5 d301cba362 Architecture: the general scope and the new-project sequence (for M2.5)
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 3m47s
- L1: `general`, the scope of conversation not (yet) about a project: an
  item per thread, no repository, build VM or execution; closes after a day
  idle, a later reply starting a linked item.
- L5: every conversation is an item from its first message; chit-chat is
  answered, only work gets a Gitea issue.
- D1: a conversation's record issue is opened once it's work on a project.
  The new-project sequence: proposal, a provisioning checklist in Matrix,
  verified when the operator says done, a tracking issue carrying the
  distilled decisions (not the raw chat), then the architecture PRs.
- Q: a scratch build VM for general replaces the answered question about
  records for pure conversations.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE
2026-10-06 00:21:34 +00:00