connectors_atlassian v1
Generated by the pinned ess generate --kind docs from adapters/atlassian/spec/ess. Structural validation establishes consistency; behaviour, storage and cross-record predicates remain implementation obligations.
The system as a graph
A command is accepted by the component that owns its context, emits the events one of its outcomes declares, and a dashed edge is a binding carrying an event into the next command. Design §9 begins one step earlier, at the actor who invokes the first command, and so does this graph: a solid edge out of an actor is a grant, and an actor drawn with no edge at all may invoke nothing — which is something the model says, not an arrow somebody forgot.
Bounded contexts
- documents (
connectors_atlassian.documents) — Atlassian-owned native document representation and membership vocabulary. Six types, no entities, no views, no commands, no events, no errors and no actors.
Components
A component is a unit of ownership, not a deployment. How many of each runs, and what each needs, is the topology.
The other pages
| page | what is on it |
|---|---|
| documents | the connectors_atlassian.documents vocabulary: its types, entities, views, commands, events, errors and actors |
| Interactions | every binding, with what it guarantees and what happens when it fails |
| Type crossings | every conversion this system permits, and the reason someone gave for it |
| Topology | what each component needs in order to run |
More columns: swipe horizontally, or focus the table and use the arrow keys.
Generated from connectors_atlassian v1 · model digest 5c7d172d47a33c3a8b86887d0ed8c3353afabdf24952da462a3debd8d34404c7 · contract digest 044569e19f3acbe26962ef9d02457a6de53f8f51296e90f2459cc1bc3cd1f6b8. Do not edit this file; change the specification and regenerate it with ess generate.