docs: the glue event axis - process-step events and inbound message/file arrivals - #21
Open
delchev wants to merge 1 commit into
Open
docs: the glue event axis - process-step events and inbound message/file arrivals#21delchev wants to merge 1 commit into
delchev wants to merge 1 commit into
Conversation
…ile arrivals The glue page said an event is an entity lifecycle event and an inbound is a webhook. Both grew: - a new "The event axis" section documents the two axes a reacting entry binds to, with the process-step shape, what is rejected at parse, and when each moment fires (reached before the step's work, completed after its writes are persisted); - "inbound - webhooks" becomes "inbound - arrivals from outside": the same create, three arrivals (path / queue-topic / polled folder), with the polled-not-watched caveat and the file handling rules. Reference index and the scope-boundary cross-links updated to match.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the two additions proposed in intent-specification#21.
The event axis — a new section on the glue page: a reacting entry (
notifications,integrations) binds to an entity lifecycle event or a process step reached/completed. A step event is an event about the record the process runs on, so every recipient path, placeholder, guard and forwarded body reads exactly as it does for a lifecycle event. Covers what is rejected at parse (undeclared process/step, a step with no observable moment, a process with no trigger) and when each moment fires (reached before the step's work; completed after its writes are persisted).inbound — arrivals from outside — the section grows from "webhooks" to the three arrivals:
path,source: { queue | topic },source: { folder, cron }. Samecreate, same ordinary write path; a folder is polled, not watched, and a read file leaves the drop folder so nothing is ingested twice.Reference index and the scope-boundary cross-links updated to match.
vitepress buildis clean.