Module outcomes 

Argument/outcome shapes for the mutation entrypoints (Engine::create_entity, update_entity, delete_entity, relate_entity, rename_entity). The MCP wire envelopes and CLI command output formatters branch on these shapes; their field layouts are part of the engine’s public surface.

Structs

CreateEntityArgs

Arguments for [Engine::create_entity].

CreateEntityOutcome

Successful outcome of [Engine::create_entity].

DeleteEntityArgs

Arguments for [Engine::delete_entity].

DeleteEntityOutcome

Successful outcome of [Engine::delete_entity].

RelateEntityArgs

Arguments for [Engine::relate_entity].

RelateEntityOutcome

Successful outcome of [Engine::relate_entity].

RelationDeclared

One batched relation declaration applied by a mutation call. Echoed in UpdateEntityOutcome::relations_declared and CreateEntityOutcome::relations_declared so agents see, in the same response, what landed and which targets had to be stubbed.

RenameEntityArgs

Arguments for [Engine::rename_entity].

RenameEntityOutcome

Successful outcome of [Engine::rename_entity].

SetSchemaOutcome

Stable response shape of [Engine::set_mem_schema] — all five fields are always present, populated per outcome.

UpdateEntityArgs

Arguments for [Engine::update_entity].

UpdateEntityOutcome

Successful outcome of [Engine::update_entity].

Enums

RelateAction

What a relate call did to the source’s relationships.

SetSchemaResult

Outcome discriminator for [Engine::set_mem_schema]. The agent branches on this — never on which response fields are populated (stable additive shape, no response-shape polymorphism).