Subscriptions
@kortexya/reasoninglayer / Subscriptions
Subscriptions
Section titled “Subscriptions”Term-change subscriptions — the engine tells the application what changed.
Remarks
Section titled “Remarks”A subscription is a durable pattern. Every term change that matches it is POSTed to a URL the application owns.
⚠️ The subscription is durable; the event is not. Delivery is best-effort with bounded retry and there is no outbox. An event whose retries are exhausted, or one produced while the engine process dies, is LOST. A retry after an ambiguous failure may DUPLICATE. Make the receiving handler idempotent, and read DeliveryStatusDto.failed — it is the only record that an event was lost.
References
Section titled “References”CreateSubscriptionRequest
Section titled “CreateSubscriptionRequest”Re-exports CreateSubscriptionRequest
CreateSubscriptionResponse
Section titled “CreateSubscriptionResponse”Re-exports CreateSubscriptionResponse
DeliveryStatusDto
Section titled “DeliveryStatusDto”Re-exports DeliveryStatusDto
FeatureFilterDto
Section titled “FeatureFilterDto”Re-exports FeatureFilterDto
ListSubscriptionsResponse
Section titled “ListSubscriptionsResponse”Re-exports ListSubscriptionsResponse
SubscriptionDto
Section titled “SubscriptionDto”Re-exports SubscriptionDto
SubscriptionEventKind
Section titled “SubscriptionEventKind”Re-exports SubscriptionEventKind
UpdateSubscriptionRequest
Section titled “UpdateSubscriptionRequest”Re-exports UpdateSubscriptionRequest