Assertion materializer
Persist mapped assertions and inspect duplicate and conflict behavior
The platform assertion runtime persists the connected assertions. It differs from ontology-store persistence: this node does not select an external fact-store endpoint. Its declaration includes invalid-record, atomicity and duplicate/conflict policy fields.
Before using it
Create or select the real resources described above in the pipeline’s project/workspace, inspect the upstream data shape and ensure your actor can perform this operation. A configuration fragment cannot create those resources. Read First pipeline for a complete graph and fixture.
Fields and bindings
| Field | Meaning |
|---|---|
inputs | Connected assertion output |
mode | insert |
invalidRecords | reject_batch or skip |
atomicity | transactional or per_unit declaration |
policy | duplicate, unreviewed/reviewed conflict and correction declarations |
Configure
Prepare the assertion materializer node for the selected test resources. Use the operation and fields shown in this example. Show actual resource bindings, upstream/downstream ports and any write/model effects before applying the draft.Connect the mapped assertion output, inspect declared invalid-record/conflict choices and check the installed runtime’s effective behavior. There is no destination endpoint picker for this platform persistence path.
Put this section under assertionMaterializer on a full node of kind assertion_materializer. It is not a standalone API or MCP request. Replace resource placeholders, and provide the full node ports/policy and graph edges.
{
"inputs": {
"assertions": "order_assertions"
},
"mode": "insert",
"invalidRecords": "reject_batch",
"atomicity": "per_unit",
"policy": {
"duplicate": "merge",
"unreviewedConflict": "supersede",
"reviewedConflict": "preserve_and_flag",
"correction": "mark_original_corrected"
}
}Verify a bounded run
Inspect persisted assertions in the project, their source evidence and review status. Replay a duplicate and a changed claim in a test fixture; verify whether merge/supersession/flagging occurred.
Validate, save a version and run a small known fixture. Inspect the actual node result and downstream consumer, not only the graph preview.
Limits and failure behavior
The pipeline assertion persistence hook receives the full materializer configuration, including atomicity and policy. Inspect its inserted/merged/superseded/conflict counts and errors to verify effective behavior. Persistence does not automatically approve claims.