Skip to content

docs: the create-from's step axis and its append cardinality - #30

Open
delchev wants to merge 1 commit into
mainfrom
docs/generates-step-append
Open

docs: the create-from's step axis and its append cardinality#30
delchev wants to merge 1 commit into
mainfrom
docs/generates-step-append

Conversation

@delchev

@delchev delchev commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Documents the two additions proposed in intent-specification#39 (proposal 0021) on the Declarative glue page.

  • The process-step axis on generates.event — the same onStepReached / onStepCompleted: { process, step } binding notifications, integrations and departures declare, narrowed by one rule of its own: the process must run on the from: entity.
  • mode: once|append — the cardinality. once (default) is the existing at-most-once behaviour; append creates one target per delivered event, which is what expresses a log entry per step or a protocol line per transition.

Both normative blocks follow the site's ::: info Normative convention. The at-most-once paragraph is now scoped to mode: once, the event-axis section notes that a create-from binds to it too, and reference.md gains the generates.event.mode row. npx vitepress build docs passes.

Left open for the maintainer, as usual.

The glue page's create-from section now carries both axes of the event
vocabulary and the mode: once|append cardinality, with the normative rules for
each: a step binding's process must run on the from: entity, mode accepts only
the two values, and the back-reference is required in both cardinalities.

States what append is not - the absence of a guard rather than a state-aware
one, so a redelivery appends a duplicate and a voided target's replacement is
not what it expresses.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant