update_blueprint
Idempotent
Update an existing Blueprint in place. Only passed fields change; pass [] to clear a list. workflow_name cannot be renamed and existing API keys keep working. Different from create_blueprint: modifies an existing Blueprint, mints no new key.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | New mode: observe or enforce; omit to keep current | |
| api_key | Yes | GeodesicAI API key (gai_...) | |
| require_math | No | Validate mathematical relationships | |
| customer_name | No | Organization or project name (also used for storage folder naming) | |
| workflow_name | Yes | Unique Blueprint identifier; the value passed as 'blueprint' in validate | |
| derived_fields | No | Field names the platform computes from other fields, e.g. ['subtotal','total'] | |
| semantic_checks | No | Domain-specific semantic check objects | |
| derivation_rules | No | Math rules as objects. Types: add, subtract, multiply, divide, round, copy, sum (multi-operand), items_multiply, items_sum. Each needs 'type' plus its fields; see the blueprint_guide prompt | |
| extracted_fields | No | Field names the agent extracts from source data, e.g. ['vendor','qty','unit_cost'] | |
| require_coherence | No | Check cross-field plausibility | |
| formal_constraints | No | Constraint objects. Types incl. magnitude_anchor {field,min,max}, relative_anchor {field,reference_field,ratio_min,ratio_max}, max_action_threshold {field,threshold,on_violation}, required_fields {fields}, equals, range, in_set, regex_match, items_magnitude_anchor; see the blueprint_guide prompt | |
| require_provenance | No | Require extraction source locations for fields | |
| require_consistency | No | Check internal field consistency | |
| enable_drift_tracking | No | Track pattern stability across batches | |
| require_high_assurance | No | Strictest mode: every check must pass | |
| enable_anomaly_detection | No | Flag records that break no rules but do not fit the reference pattern |