Rules

Rules place token entries on tickets and projects. They work like the rules in a banking app: set once, every new token entry lands where it belongs, and people only handle the exceptions.

Signals

A signal is a fact about a session that hints at where its cost belongs:

• the branch and the working directory
• the repository
• the pull request number
• the subagent type
• ticket keys that match a project's ticket key pattern, found in your prompts, the session title or the pull request title

Prompts and titles are read on the machine. Only the ticket keys found in them leave it, as Security and privacy lists.

The default rules

Add your own in the web app under Rules, in the mod's pane, or with the CLI.

Order

Rules run in order, and the first that matches wins. Organization rules run before personal ones, so a person's own rules only handle what the organization's rules leave open.

When prompts name several tickets

By default the ticket named most often in your prompts wins, and on a tie the latest one. An organization can switch this to an equal split between the tickets, or to the first one named.

When nothing matches

The token entry stays unattributed and shows up in your review list. The share placed by rules is your attribution; you set the attribution target.