Skip to content
Merulan

Actions and writeback

Actions and writeback separate a requested change from its confirmed effect and the evidence needed to resolve it.

Actions and writeback connect a change to its result in Company Schema. Read an accepted request back to find out whether its effect is known.

Ownership

Actions and writeback meet at the change to a Record. An Action defines work a caller can invoke. Writeback controls a change to an external system. The Console lists Actions at /schema/actions and writeback requests at /schema/writeback. A local change and an external change take different paths. Read the request's result to find out which path applies. The launch control alone cannot tell you.

Lifecycle

Actions and writeback keep evidence while work proceeds. An Action Run freezes its target selection and records a result for each target. Work may finish with errors or leave effects needing review. A writeback result says whether the change committed or passed to an executor. Readback keeps the request state and links to the effect. An accepted request does not prove that an external write committed.

Boundaries

Actions and writeback check values and access before a write. A field's writeback policy defines who owns an external change. Changing that policy can affect its callers. ontology.migrations.plan records the schema change when it needs a plan. Data Pipelines owns incoming data and lineage. An external write does not replace that import history or the rules for a Record's fields.

Failures

Actions and writeback can leave different kinds of unfinished work. An Action target can fail, lose access, or have an accepted effect awaiting confirmation. The last case needs the effect owner's readback before any repeat. A writeback request can be parked for manual review. Its missing local result does not prove that the external system did nothing. Repeating a write without checking that evidence can repeat the effect.

Recovery

Actions and writeback expose repair at the object that owns the unresolved result. Inspect action runs follows target counts and attention items to writeback readback. A parked write with stored context can use Redrive to finish its local work. Redrive does not call the external system again. Repair controls check the caller's access and record the state change. Read the request and Record values to check the result.

The Console explains sign-in and Workspace selection before you inspect Actions and writeback there. Action Run and writeback call contracts are absent from this family's published Operations page.