⠿ Enums · Action + CounterpartyRole Completed Runebook
T−14+
⤢ ⌃ ⧉ ✕
</> RUNE legacybank-event-enum.rosetta legacybank-party-enum.rosetta + Graph Valid
</> JAVA-GEN LegacyBankActionEnum LegacyBankCounterpartyRoleEnum + Custom Java Generate
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
namespace legacybank.eventversion "0.1.0" enum LegacyBankActionEnum: <"Lifecycle action the bank is asserting for this event. The four canonical values present on every outbound trade-event message."> NEW <"First booking of a brand-new trade."> AMEND <"Correction to an existing trade — preserves identifiers, replaces content."> CANCEL <"Full reversal of a previously-booked trade — leaves an audit record."> REPLACE <"Cancel + new pair as a single atomic operation.">
TEMPLATE GUIDE
Reference · LegacyBankActionEnum

This is what the blank runebook is heading toward. Compare line-for-line; copy nothing blindly.

Notes on the shape
  • Enum-level doc string sits below the declaration colon, indented by two spaces. It explains the enum's purpose at the model level — what concept it represents and where it appears in real data.
  • Each variant gets its own doc string, one line below the variant name, indented two more spaces. The doc string is the line that propagates into the generated Java @JsonProperty javadoc + the regulatory report column descriptions.
  • Blank lines between variants are a readability convention — Rune DSL doesn't require them, but every variant on its own paragraph keeps the file scannable as enums grow — the Lesson 4 closeout schema adds five-variant enums.