2.3 KiB
Composition profiles
Composition profiles encode diagram logic, not visual decoration.
Shared rules
- Publication SVGs contain only nodes, boundaries, edges, state/time annotations required to decode them, and optional legends for non-obvious symbols.
- Global title, subtitle/question, footer, takeaway band, pattern number, watermark, gradient, glow, and decorative metric cards are forbidden.
- For non-comparison and non-timeline profiles, at least 80% of nodes participate in the central relation.
Profiles
component-flow
Source/actor on the left, processing stages in reading order, terminal store/event/effect on the right. Separate return and asynchronous event paths when their semantics differ.
orchestrator-workers
One orchestrator above a worker field. Dispatch/control arrows descend; results, stdout, callbacks, or notifications return on labeled routes.
query-fanout
Query input and parser/selector remain distinct. A router or selector fans out to two or more equivalent shard/store nodes with identical shape and alignment.
timeline
One horizontal time axis. Milestones have unique positions. Date/offset annotations stay adjacent to their marker. Do not render time as service calls.
reconciliation-loop
Desired state, controller, and actual state form the primary triad. Reconcile action moves forward; watch/status feedback returns. Failure is marked on the failed action path.
resource-controller
Specification/custom-resource nodes use document semantics; controller nodes use controller semantics; created runtime resources remain visibly separate from declarative resources.
two-zone-pipeline
At least two evidenced groups. Boundary crossings are labeled. Loops exist only where the source establishes a cycle.
sequence
Participants are lifelines. Messages are ordered top-to-bottom. Responses or asynchronous notifications use dashed semantics only when grounded.
ports-adapters
Application/domain core in the center. Inbound adapters on the left, outbound adapters on the right, optional port nodes adjacent to the core. Dependency direction follows the prose, not assumed runtime flow.
comparison
Two or more aligned items with comparable detail lines. No call edge is implied unless the prose explicitly establishes one. This profile is not a fallback for missing relationships.