Skip to content

Cratis Chronicle capture authoring in .NET

Cratis Chronicle captures turn external data changes into events. In .NET, you can describe a capture with fluent C# builders or model-bound attributes.

Approach Use it to Where it’s documented
Capture Declaration Language (CDL) Write language-neutral text that the kernel parses and validates Capture Declaration Language
Declarative API Construct a CaptureDefinition with a C# fluent builder Declarative Captures
Model-bound API Describe capture intent with C# attributes beside your types Model-Bound Captures

CaptureBuilder.Build() produces a CaptureDefinition. The model-bound attributes expose metadata, but the .NET client does not provide a builder that converts them into a definition. Neither approach registers or starts a capture, and IEventStore does not expose capture management. The kernel’s management contract takes CDL text.

If you need a capture the engine can run, start with CDL. Its execution limits apply regardless of authoring style: API polling and events captures can run root-level append rules, while webhook and message-topic sources, map operations, and nested or children scopes are rejected during validation.