Create MASD personas and link to cybernetic levels
Table of Contents
This page is a capture in the inbox bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
What
Once the drift between codegen and its reference implementation is resolved, introduce the personas defined in the MASD methodology (Modeller, Implementer, User, etc.) as first-class artefacts in the OreStudio documentation and wire each persona to the corresponding cybernetic level in the OreStudio information architecture. Each persona should describe its goals, typical interactions with the system, and the cybernetic layer (e.g. operational, tactical, strategic) it primarily operates at. The MASD methodology reference is at https://mcraveiro.github.io/dogen/docs/the_masd_methodology.html.
Why
OreStudio's cybernetic information architecture already defines levels of abstraction, but lacks the human-centred view of who uses the system and why. Adding MASD personas makes it explicit which user roles interact at which cybernetic level, improving both documentation clarity and future UX decisions. The prerequisite is closing the codegen drift so the persona definitions can be code-generated consistently with the rest of the model.
References
- MASD Methodology: https://mcraveiro.github.io/dogen/docs/the_masd_methodology.html
- Blocked on: resolving drift between codegen and reference implementation.
See also
- ORE Studio Site — cybernetic information architecture context.