Integration Examples

Source: docs/integration-examples.md

Integration Examples

These are common patterns teams use today. Each example keeps interpretation deterministic and non-judgmental.

Pre-publish checks (marketing, legal, policy)

  1. Capture draft text before publishing.
  2. Call /interpret with artifact_type: FREE_TEXT.
  3. Store analysis_run_id alongside the draft version.
  4. Review any assumption records as "areas of possible overreach".

Outcome: review focuses on language that could be read as stronger than intended, without claiming the text is wrong.

Product release notes

Run interpretation on release notes that include performance or availability claims. If assumption records appear, add clarifying language before shipping.

Model cards and eval summaries

Use artifact_type: MODEL_CARD or EVAL_SUMMARY to keep analysis scoped to those surfaces and compare changes across versions with /diff.

CI/CD snapshots

At release time, store:

  • the artifact text
  • the analysis_run_id
  • the runtime version + ruleset version

This gives you a replayable interpretation snapshot for audit or incident review.

Document version diffs

  1. Interpret version A and version B.
  2. Call /diff with analysis_run_id_a and analysis_run_id_b.
  3. Store the drift_id and net_change.

This shows how commitment boundaries shifted between versions without judging truth.

Support and incident response

When a user reports a discrepancy, replay the original analysis run to show the exact interpretation that was recorded at the time.