shu/vpp-ai-platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
1cc21e0dc6
vpp-ai-platform/docs/adr/0008-cases-for-humans-workflows-for-machines.md
stewart hu 80835138e9 Scaffold repo for implementation handoff 
- README: orientation, doc map, target package layout (pointers only,
  no duplicated architecture content)
- CLAUDE.md: agent operating manual — invariants as code-review rules,
  conventions, do-not list, task reading order
- ROADMAP: M1-M5 with verifiable acceptance criteria, phase-2 fence
- GLOSSARY: canonical Chinese-term → code-name mapping
- docs/adr/: eight ADRs recording settled decisions and rejected
  alternatives
- docs/open-questions.md: consolidated TODO(业务) tracker by owner and
  blocking milestone
- .gitignore; untrack .DS_Store

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019u5SLNweVio6ozJX7yfxQr

🔮 View transcript: https://logs.lojong.info/s/e8u90k3t33w590r7b5y7yzqh
2026-09-01 21:13:00 -04:00

747 B
Raw Blame History

ADR-0008: Cases for humans, workflows for machines

Status: accepted · 2026-09

Context: Operators need a unit of accountability; the runtime needs a unit of execution. Conflating them makes both worse (peer review, Alternative C).

Decision: DecisionCase (one objective, owner, deadline, completion contract) is the operator-facing aggregation; workflows are internal execution. A case references the products of several workflows via case_id. Dashboards, approval inboxes, and reports are projections over cases + ledger + event log, not standalone feature silos.

Consequences: UI work targets case views; a case must never become an unbounded container (enforced: one objective per case, mandatory completion contract).