Skill: TraceMem Writing Data (Governed Writes)

Purpose

This skill explains how to modify data (insert, update, delete) within TraceMem's governance model. Writing is a high-stakes operation that often triggers policy checks.

When to Use

• When you need to create records, update status, or delete resources.
• After you have read the current state and determined a change is necessary.

When NOT to Use

• Do not write if you are in propose mode (unless prototyping in a sandbox, but generally propose implies read-only).
• Do not write without first evaluating relevant policies (unless you are sure the Data Product has no attached blocking policies).

Core Rules

• Verify Policy First: Before writing, it is best practice to call decision_evaluate to check if your proposed action is allowed.
• One Operation Per Product: Use _insert, _update, or _delete products appropriately. DO NOT try to insert on an update product.
• Flat vs Nested: You can use a flat structure (operation + fields) for function-like products (e.g. create_incident) or nested records for batch table operations.
• Governance: Writes are the primary target for human approvals. Be prepared for a write to be blocked.
• Purpose: Like reads, writes require a valid purpose.