Give a Jira workflow rule a memory that survives, without blowing the prompt budget

Give a Jira workflow rule a memory that survives, without blowing the prompt budget Key takeaways END STATE: a workflow rule that accumulates lessons about YOUR instance across runs, injected under a byte cap you can prove holds, with duplicates folded in rather than appended. Cap the prompt block in UTF-8 BYTES, never in string length. Measured: a Japanese memory block was 95 bytes for 53 characters — a char-based cap overshoots the budget by ~1.8x, and up to 3-4x for pure CJK. Jaccard at 0.85 is a HIGH bar. Two sentences a human reads as identical scored 0.733 and did NOT merge.