Linear

What it does

After each weekly check of a tracked brand, RulerIQ turns your fix list into Linear issues in one team you choose. Each fix is one issue: a plain-sentence title, the evidence (which engines, how consistently, what they said against what your site says, and any cited page), the paste-ready snippet when there is one, and a link back to your fix list in RulerIQ.

Set it up

1. In Linear, open Security & access under your account settings and create a personal API key. Name it RulerIQ.
2. Give it what RulerIQ needs: read your teams, create and edit issues, and add comments. If Linear offers a choice of permissions or team access, include the team you want issues in. Full access always works, but you don't have to give more than that. The options in Linear's key dialog can change, so if something below fails, check them first.
3. Copy the key. Linear shows it once.
4. In RulerIQ, open Connect data (or Settings, Keys and connections), paste it into the Linear card and click Save key. RulerIQ checks it with Linear, then stores it encrypted.
5. Choose the team for new issues and click Use this team.

Vendor reference: Linear API: getting started.

Test it

Click Test on the Linear card. It confirms the key still works and can see your team, and tells you if the team has no Done or Todo state to close or reopen issues with. It creates nothing in Linear.

What RulerIQ creates and changes

• One issue per fix-list item, in your chosen team, with a RulerIQ label (created if the team doesn't have one). At most 25 new issues per weekly sync, highest-ranked first; the rest follow next week.
• It never creates the same fix twice. RulerIQ remembers which issue belongs to which fix. If the evidence changes in a later check, it rewrites that issue's description instead of making a new one. Put your own notes in comments, since the description gets rewritten.
• When a later check verifies a fix, it adds a comment with the evidence and moves the issue to your team's first Completed state. Verified follows the same rule as your fix list: at least two full checks after the fix was marked done, and the change has to be beyond normal run-to-run variation.
• If a verified fix regresses, it adds a comment and, if the issue is closed, moves it back to your team's first Unstarted state.
• Marking a fix done: mark it in RulerIQ, or just complete the issue in Linear. RulerIQ treats the day you completed it as the day you shipped it and checks from there.
• It does not touch an issue you moved to Canceled, or one you deleted. It stops syncing that fix and doesn't recreate it.
• It does not move an issue that someone is already working on, except to close it when verified.

Issues and comments appear as created by you, because a personal API key acts as your Linear user.

What RulerIQ can and can't access

RulerIQ uses the key only to do the things above, in the one team you chose. We store it encrypted, show only its last 4 characters after you save it, and never return it through our API. It is decrypted only by the background job that delivers to Linear and, for a moment, by the app when you press Test or pick a team. Your fix-list text and evidence go to Linear; we send nothing else.

If Linear rejects the key (revoked or expired), RulerIQ marks the connection as needing to be reconnected, stops trying, and shows a Reconnect prompt on the Linear card. A Linear outage or rate limit never affects your weekly check; RulerIQ retries a few times and then tries again after the next check.

Disconnect and delete

Click Remove on the Linear card. RulerIQ deletes your stored key and forgets which issues belong to which fixes. Issues already in Linear stay as they are. To make the key useless everywhere, delete it in Linear under Security & access. Changing teams works the same way: new issues go to the new team, and the old team's issues are left alone.