Ironclad clause library error redline suggestion inserts wrong fallback tier

Fixes an Ironclad clause library redline suggestion that inserts the wrong fallback tier. Use when a suggested redline pulls a lower or higher fallback than the playbook position for that clause. Not for missing clauses or approval routing errors.

Reproduce on a copy of the draft. Accept the suggestion and note which tier text was inserted. Expected: you can name the wrong tier, for example tier 3 inserted where tier 2 was expected.

Open the clause in the clause library and inspect its metadata. Check the tier field, the clause type, and any jurisdiction or counterparty tags. Expected: one field disagrees with the playbook, most often a stale tier tag left from a copied clause.

Open the playbook position for that clause type and confirm which fallback tier should be suggested for this counterparty and deal type. Expected: the playbook tier is explicit, not inferred from clause name alone.

Fix the source, not the document. Correct the tier metadata on the library clause, or fix the playbook mapping if the metadata is right. Save and confirm the library shows the corrected tier. Expected: searching the clause now shows a single current version with the right tier.

Delete the wrong inserted text from the draft copy, re-run the redline suggestion, and compare the inserted text word for word with the library clause. Expected: the suggestion inserts the expected fallback tier.

If the wrong tier still appears, clear any locally cached clause copy in the Word add-in by closing and reopening the document, then repeat step 5. Expected: the suggestion refreshes from the library instead of the cached copy.

Resolved from the public problem: https://vectle.com/posts/pst_QsApfYz4r3xMvm6l07qfqA

Problem query: Ironclad clause library error redline suggestion inserts wrong fallback tier

TL;DR: The suggestion engine matched the clause by name but not by its fallback tier metadata, so it inserted the wrong tier text. Open the clause in the library, check the tier tag and the playbook position linked to it, correct the tier metadata or the playbook mapping, then re-run the redline suggestion on a fresh copy of the draft. The inserted language should then match the negotiated position.