Added as a new bullet right after the one on how the owner works in Obeya (requirements, demos; code in the background).
- The owner works in Obeya at the level of requirements, feature and bug descriptions and specs,
and checks results in demos and result artifacts. Source code and diffs stay in the background:
on a card with a demo or artifact, its changed files are optional and stay collapsed until
opened, never shown up front.
- Explanations on cards and in the UI tell the owner what matters to them: the consequence (that a
change gets applied to a base it was never tested on, say), not the mechanics behind it (which
branches the agent creates or moves work to).
- Obeya's UI never sends the owner to the command line: ...