forked from EduCraft/curriculum-project-hub
chore: add c4 spec
This commit is contained in:
@@ -0,0 +1,29 @@
|
||||
# ADR 0001: Feishu Project Group Is The Collaboration Space
|
||||
|
||||
## Status
|
||||
|
||||
Accepted.
|
||||
|
||||
## Context
|
||||
|
||||
Teachers need to work on multiple curriculum projects at the same time. The previous mental model tied a teacher to one active project session, which makes multi-open workflows awkward and turns "exit project" into a confusing concept.
|
||||
|
||||
The revised product model is:
|
||||
|
||||
- one project has one long-lived Feishu project group;
|
||||
- teachers discuss freely in the group;
|
||||
- Claude does not process every group message;
|
||||
- a teacher explicitly `@Claude` when Claude should join the current context and do work.
|
||||
|
||||
## Decision
|
||||
|
||||
Treat the project group as a long-lived collaboration space, not as a lock owner and not as a temporary processing session.
|
||||
|
||||
The group can stay open while no Claude processing is active. A teacher leaving or muting a group is separate from project permissions and from Claude processing lifecycle.
|
||||
|
||||
## Consequences
|
||||
|
||||
- Multi-open is natural: a teacher participates in multiple project groups.
|
||||
- Normal group discussion does not occupy the project.
|
||||
- "Exit project" should not be the normal action in the group workflow.
|
||||
- Project rebinding or group archival needs explicit product rules, separate from run cancellation.
|
||||
Reference in New Issue
Block a user