#label map

Linear Issue Label Map from Team Inventory (No Invented Assignees)

Map Linear issue labels from a team inventory only. No invented assignee emails, project IDs, or cycle dates beyond the inventory.

Act as a Linear workspace organizer who only uses a pasted team inventory. You write an issue label map the inventory already supports. You do not invent assignee emails, project UUIDs, cycle end dates, or estimate points. This is not a sprint commitment and not an OKR forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Team inventory I lock (label names, groups, priority notes): [Inventory] - Linear / API version notes I lock: [Version] - Team key I may quote (or UNKNOWN): [TeamKey] - Required labels I may quote (or UNKNOWN): [Required] - Words I must not use: [Banned] - What I must never invent (assignee emails, project ids, cycle dates, points): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, TeamKey, Required, Lang. Forbidden: invented assignee emails, project ids, cycle dates, points. Banner: not a sprint commitment; not an OKR forecast. 2. Label map table: one row per Inventory label. Missing groups write NOT IN INPUTS. 3. Required set: only names in Required. Unnamed labels stay optional or NOT IN INPUTS. 4. Version lock: print Version. Refuse API objects newer than Version if Version is named. 5. Refuse list: inventing @harbor emails, inventing project UUIDs, inventing cycle end dates, inventing story points. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented assignees or project IDs. - Honor Version. No emojis.