Skip to content

Seam Troubleshooting

Rule Did Not Match

Run:

seam transcript inspect --transcript rewrite.json --schema schemas/transcript.schema.json --decoded
seam rules explain --rules rules/ --rule a2a_prompt_laundering_replace
seam rules trace --rules rules/ --transcript rewrite.json

Common causes:

  • wrong protocol, kind, or direction
  • decoded path does not exist
  • where predicate is too narrow
  • traffic went through tap instead of proxy
  • message was a stream handshake or partial chunk rather than a complete decoded message

Replace Failed

mutate.replace applies only to string fields. If the target path is missing, non-string, regex-invalid, or has an unresolved template, the transform fails according to the configured transform failure policy.

Missing Before/After

Untouched passive records have after: null and rule_applied: null. A rewrite record should have both before and after. If not, confirm the rule matched with seam rules trace.

Stale Schema Path

Use the packaged schema path from your current execution context:

seam transcript verify --transcript rewrite.json --schema schemas/transcript.schema.json

If running from the monorepo instead of a release archive, the shared schema may be under agentic-redteam/schema/.

Report Sharing

Use transcript redact for report-safe review copies. It redacts raw payloads and common credential fields, rehashes the derivative transcript, and keeps source hash metadata in decoded redaction metadata. Do not replace the raw evidence transcript with the redacted copy.