AI workflows
Use RowTether with an AI client through staged, read-only workflows before approving any configuration change.
Start with Connect RowTether to AI. The automation reference is the source for every tool signature, limit and recovery rule.
Diagnose a relationship
Ask the client to call get_connection, list_tables, inspect_table, get_configuration, validate_profile, start_review, get_review_status, get_results and explain_finding in that order. Require the report to include source table, row, field, destination, code, severity and coverage. The client must use discovered paths and must not modify assets.
Preview a CSV
Ask the client to inspect the current profile, start a second review with a new requestId, hasCandidate: true, the selected destination path and CSV text, then read get_results, analyze_impact and compare_reviews. A preview is read-only and covers captured consumers only; it is not proof that arbitrary Blueprint or C++ usage is safe.
Propose a rule change
Read get_configuration and retain its configurationFingerprint. Inspect real field types and supported operators, build and validate a complete schema-2 profile, review baseline and proposal sequentially, compare them, then call propose_profile. Inspect Before/After in RowTether → AI proposals and approve explicitly. A proposal is temporary and expires; a stale fingerprint requires a new proposal.