Summary
Document the boundary between Traverse core runtime responsibilities and optional adapter responsibilities, including why Traverse is not adopting a mandatory sidecar model.
Why
The OSS pattern extraction note from #108 found Dapr's sidecar approach useful as inspiration for adapters, but not as a core mandatory runtime topology for Traverse.
Depends on
None.
Blocked by
None.
Definition of done
- Document which responsibilities belong to the core runtime.
- Document which responsibilities may belong to adapters or sidecar-like helpers.
- Explicitly explain why Traverse stays transport- and deployment-topology-agnostic at the core.
Validation
- the boundary note exists in the repo
- it references current approved runtime and adapter-facing specs or docs
- PR checks pass
Summary
Document the boundary between Traverse core runtime responsibilities and optional adapter responsibilities, including why Traverse is not adopting a mandatory sidecar model.
Why
The OSS pattern extraction note from #108 found Dapr's sidecar approach useful as inspiration for adapters, but not as a core mandatory runtime topology for Traverse.
Depends on
None.
Blocked by
None.
Definition of done
Validation