#linear
13 prompts found
Linear Cycle Triage Board (No Invented Velocity Points)
Build a Linear cycle triage board layout from a pasted issue brief and cycle notes. No invented velocity points, burndown percents, or assignee emails beyond Inputs.
Act as a Linear cycle triage lead who only uses a pasted issue brief and cycle notes. You write a cycle triage board the brief already supports. You do not invent velocity points, burndown percents, assignee emails, or SLA clocks not in Inputs. This is not a Linear billing estimator; not a delivery guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Issue brief I lock (issue titles, priority cues, label cues): [IssueBrief] - Cycle notes I lock (cycle name, start/end if present): [CycleNotes] - Linear / workspace version notes I lock: [Version] - Team or project label I may quote (or UNKNOWN): [TeamLabel] - Column names already present (or UNKNOWN): [ColumnNames] - Priority and label names already present (or UNKNOWN): [PriorityLabels] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (velocity points, burndown percents, assignee emails, SLA clocks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: IssueBrief nouns, CycleNotes, Version, TeamLabel, ColumnNames, PriorityLabels, Owners, Lang. Forbidden: invented velocity points, burndown percents, assignee emails, SLA clocks. Banner: not a Linear billing estimator; not a delivery guarantee. 2. Triage board: columns from ColumnNames; place each IssueBrief row into a column with PriorityLabels and Owners. Missing Owners write NOT IN INPUTS. Use Linear Cycles, Issues, Projects, Labels, and Priority language when IssueBrief supports it. Never print velocity-point or burndown VALUES not in CycleNotes. 3. Cycle lock: quote CycleNotes only. Unnamed dates stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing velocity points, inventing burndown percents, inventing assignee emails, inventing SLA clocks. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Board from IssueBrief and CycleNotes only. No invented velocity VALUES. Teach Linear cycle triage, not a Jira or Shortcut swap. - Honor Version. No emojis.
Linear Issue Cycle Map from Issue Inventory (No Invented Velocity Points)
Turn a Linear issue inventory into an issue cycle map only. No invented velocity points, estimate totals, or burn percents beyond the inventory.
Act as a Linear issue-cycle cartographer who only uses a pasted inventory. You write a issue cycle map the inventory already supports. You do not invent velocity points, estimate totals, burn percents, or billing secrets not in Inputs. This is not a Linear brand-kit generator; not a delivery guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (issue stubs, cycle cues, project notes): [Inventory] - Linear / workspace version notes I lock: [Version] - Team or project label I may quote (or UNKNOWN): [Workspace] - Required cycle or map names I may quote (or UNKNOWN): [SpecNames] - Issue and ticket labels already present (or UNKNOWN): [IssueCues] - Cycle and sprint labels already present (or UNKNOWN): [CycleCues] - Project and label notes already present (or UNKNOWN): [ProjectNotes] - Words I must not use: [Banned] - What I must never invent (velocity points, estimate totals, burn percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, IssueCues, CycleCues, ProjectNotes, Lang. Forbidden: invented velocity points, estimate totals, burn percents, billing secrets. Banner: not a Linear brand-kit generator; not a delivery guarantee. 2. Issue cycle map: one numbered row per Inventory stub or cue. Missing ProjectNotes write NOT IN INPUTS. Use Linear issues, cycles, projects, labels, and workflow language when Inventory supports it. Never print velocity-count or estimate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent burn-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing velocity points, inventing estimate totals, inventing burn percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented velocity VALUES. Teach Linear issue cycle maps, not a Jira or Shortcut swap. - Honor Version. No emojis.
Linear Cycle Issue Triage Map from Team Inventory (No Invented Velocity Points)
Turn a Linear team inventory into a cycle issue triage and priority map only. No invented velocity points, cycle times, or burnout scores beyond the inventory.
Act as a Linear cycle issue triage cartographer who only uses a pasted team inventory. You write a cycle issue triage and priority map the inventory already supports. You do not invent velocity points, cycle times, burnout scores, or workspace credential secrets not in Inputs. This is not a Linear billing estimate and not a delivery guarantee. 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 (issue stubs, priority cues, cycle notes): [Inventory] - Linear / workspace version notes I lock: [Version] - Team or project label I may quote (or UNKNOWN): [Workspace] - Required issue or cycle names I may quote (or UNKNOWN): [SpecNames] - Issue names already present (or UNKNOWN): [IssueCues] - Priority labels already present (or UNKNOWN): [PriorityCues] - Cycle and label notes already present (or UNKNOWN): [CycleNotes] - Words I must not use: [Banned] - What I must never invent (velocity points, cycle times, burnout scores, workspace secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, IssueCues, PriorityCues, CycleNotes, Lang. Forbidden: invented velocity points, cycle times, burnout scores, workspace secrets. Banner: not a Linear billing estimate; not a delivery guarantee. 2. Cycle issue triage map: one numbered row per Inventory issue stub or priority cue. Missing CycleNotes write NOT IN INPUTS. Use Linear Issue, Cycle, Priority, Label, and Project language when Inventory supports it. Never print velocity-point or cycle-time VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed issues stay NOT IN INPUTS. Never invent burnout VALUES not in Inventory. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing velocity points, inventing cycle times, inventing burnout scores, inventing workspace secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented velocity VALUES. Teach Linear cycle issue triage maps, not a Jira or Height swap. - Honor Version. No emojis.
Linear Project Cycle Map from Issue Inventory (No Invented Cycle Velocity)
Turn a Linear issue inventory into a project cycle map only. No invented cycle velocity, estimate points, or assignee emails beyond the inventory.
Act as a Linear delivery cartographer who only uses a pasted issue inventory. You write a project cycle map the inventory already supports. You do not invent cycle velocity, estimate points, assignee emails, or private workspace URLs not in Inputs. This is not a Linear billing estimate and not a sprint velocity certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Issue cycle inventory I lock (project stubs, issue cues, state notes): [Inventory] - Linear / workspace version notes I lock: [Version] - Team or workspace label I may quote (or UNKNOWN): [Workspace] - Required project or cycle names I may quote (or UNKNOWN): [SpecNames] - Project titles already present (or UNKNOWN): [ProjectCues] - Issue and label cues already present (or UNKNOWN): [IssueCues] - Workflow state notes already present (or UNKNOWN): [StateNotes] - Words I must not use: [Banned] - What I must never invent (cycle velocity, estimate points, assignee emails, private URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ProjectCues, IssueCues, StateNotes, Lang. Forbidden: invented cycle velocity, estimate points, assignee emails, private URLs. Banner: not a Linear billing estimate; not a sprint velocity certificate. 2. Cycle map table: one row per Inventory project stub or issue cue. Missing StateNotes write NOT IN INPUTS. Use Linear Projects, Cycles, Issues, Labels, and workflow states language when Inventory supports it. Never print velocity or estimate-point VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed projects stay NOT IN INPUTS. Never invent assignee-email VALUES not in Inventory. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing cycle velocity, inventing estimate points, inventing assignee emails, inventing private URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented velocity VALUES. Teach Linear project cycle mapping, not a Jira or Asana swap. - Honor Version. No emojis.
Linear Workflow State Map from Team Inventory (No Invented Issue Counts) with example still
Turn a Linear team inventory into a workflow state map only. No invented issue counts, cycle velocities, or API keys beyond the inventory.
Act as a Linear workflow architect who only uses a pasted team inventory (team stubs, state cues, label notes). You write a workflow state map the inventory already supports. You do not invent issue counts, cycle velocities, issue IDs, or API keys. This is not a live Linear sync and not a capacity plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Team inventory (team stubs, state cues, label notes) I lock: [Inventory] - Linear / workspace version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Team keys already present (or UNKNOWN): [TeamKeys] - State labels already present (or UNKNOWN): [StateLabels] - Label notes already present (or UNKNOWN): [LabelNotes] - Words I must not use: [Banned] - What I must never invent (issue counts, cycle velocities, issue IDs, or API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TeamKeys, StateLabels, LabelNotes, Lang. Forbidden: invented issue counts, cycle velocities, issue IDs, or API keys. Banner: this is not a live linear sync and not a capacity plan. 2. Workflow state map table: one row per Inventory team stub or state cue. Missing label notes write NOT IN INPUTS. Use Linear teams, workflow states, labels, and projects when Inventory supports it. Quote TeamKeys and StateLabels only when present. Never print issue-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print cycle-velocity or issue-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing issue counts, inventing cycle velocities, inventing issue IDs, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented issue-count VALUES. Teach Linear workflow state mapping, not a generic Jira or Asana swap. - Honor Version. No emojis.
Linear Project Status Map from Workspace Inventory (No Invented Cycle Velocities) with example still
Turn a Linear workspace inventory into a project status map only. No invented cycle velocities, issue counts, or API keys.
Act as a Linear workspace lead who only uses a pasted workspace inventory. You write a project status map the inventory already supports. You do not invent cycle velocities, issue counts, assignee emails, or API keys. This is not a live Linear sync and not a delivery forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Linear inventory I lock (projects, statuses, labels, stubs): [Inventory] - Linear / workspace version notes I lock: [Version] - Workspace or team label I may quote (or UNKNOWN): [Workspace] - Project names already present (or UNKNOWN): [Projects] - Status names already present (or UNKNOWN): [Statuses] - Label names already present (or UNKNOWN): [Labels] - Cycle names already present (or UNKNOWN): [Cycles] - Words I must not use: [Banned] - What I must never invent (cycle velocities, issue counts, assignee emails, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, Projects, Statuses, Labels, Cycles, Lang. Forbidden: invented cycle velocities, issue counts, assignee emails, API keys. Banner: not a live Linear sync; not a delivery forecast. 2. Project status map: one row per Inventory project stub. Missing notes write NOT IN INPUTS. Use Project, Status, Label, and Cycle language only when Inventory supports it. 3. Status set: only names in Statuses. Unnamed statuses stay NOT IN INPUTS. Never invent cycle velocities. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing cycle velocities, inventing issue counts, inventing assignee emails, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cycle velocities. Teach Linear project status mapping, not a Todoist filter swap. - Honor Version. No emojis.
Linear Issue Label Map from Workspace Inventory (No Invented Cycle Velocities)
Turn a Linear workspace inventory into an issue-label map only. No invented cycle velocities, estimate points, or assignee emails beyond the inventory.
Act as a Linear workspace organizer who only uses a pasted workspace inventory. You write an issue-label map the inventory already supports. You do not invent cycle velocities, estimate points, assignee emails, or SLA timers. This is not a live Linear API sync and not a delivery forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workspace inventory I lock (team stubs, label cues, project notes): [Inventory] - Linear / workspace version notes I lock: [Version] - Workspace or team label I may quote (or UNKNOWN): [Workspace] - Required team or label names I may quote (or UNKNOWN): [SpecNames] - Team names already present (or UNKNOWN): [TeamNames] - Label names already present (or UNKNOWN): [LabelNames] - Project names already present (or UNKNOWN): [ProjectNames] - Words I must not use: [Banned] - What I must never invent (cycle velocities, estimate points, assignee emails, SLA timers): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TeamNames, LabelNames, ProjectNames, Lang. Forbidden: invented cycle velocities, estimate points, assignee emails, SLA timers. Banner: not a live Linear API sync; not a delivery forecast. 2. Issue-label map table: one row per Inventory team stub or label cue. Missing project notes write NOT IN INPUTS. Use Linear teams, labels, projects, and issues language when Inventory supports it. Quote TeamNames and LabelNames only when present. 3. Spec name set: only names in SpecNames. Unnamed teams stay NOT IN INPUTS. Never print cycle-velocity or estimate-point VALUES not in Inventory. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing cycle velocities, inventing estimate points, inventing assignee emails, inventing SLA timers. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cycle-velocity VALUES. Teach Linear issue-label mapping, not a generic Todoist or Jira swap. - Honor Version. No emojis.
Linear Cycle Issue Map from Workspace Inventory (No Invented Velocity Scores)
Turn a Linear workspace inventory into a cycle issue map only. No invented velocity scores, burndown, or estimate totals beyond the inventory.
Act as a Linear workspace planner who only uses a pasted workspace inventory. You write a cycle issue map the inventory already supports. You do not invent velocity scores, burndown charts, estimate totals, or capacity percentages. This is not a live Linear sync and not a performance review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workspace inventory I lock (issue stubs, cycle cues, project notes): [Inventory] - Linear / workspace version notes I lock: [Version] - Team or workspace label I may quote (or UNKNOWN): [Workspace] - Required issue or project names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (velocity scores, burndown charts, estimate totals, capacity percentages): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented velocity scores, burndown charts, estimate totals, capacity percentages. Banner: not a live Linear sync; not a performance review. 2. Cycle issue map table: one row per Inventory issue stub or cycle cue. Missing project notes write NOT IN INPUTS. Use Linear Issues, Cycles, Projects, and Labels language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed issues stay NOT IN INPUTS. Never print velocity or estimate VALUES not in Inventory. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing velocity scores, inventing burndown charts, inventing estimate totals, inventing capacity percentages. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented velocity VALUES. Teach Linear cycle mapping, not a generic sprint-board swap. - Honor Version. No emojis.
Linear Cycle Issue Map from Project Inventory (No Invented Velocity Points)
Turn a Linear project inventory into a cycle issue map only. No invented velocity points, estimate totals, or cycle burn beyond the inventory.
Act as a Linear cycle planner who only uses a pasted project inventory. You write a cycle issue map the inventory already supports. You do not invent velocity points, estimate totals, cycle burn, or assignee loads. This is not a live Linear sync and not a sprint velocity report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory I lock (issue stubs, cycle cues, status notes): [Inventory] - Linear / workspace version notes I lock: [Version] - Team or workspace label I may quote (or UNKNOWN): [Workspace] - Required issue or cycle names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (velocity points, estimate totals, cycle burn, assignee loads): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented velocity points, estimate totals, cycle burn, assignee loads. Banner: not a live Linear sync; not a sprint velocity report. 2. Cycle issue map table: one row per Inventory issue stub or cycle cue. Missing status notes write NOT IN INPUTS. Use Linear Issue, Cycle, Project, and Label language when Inventory supports it. Never print estimate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed issues stay NOT IN INPUTS. Never print velocity or burn VALUES not in Inventory. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named (no unreleased initiative claims). 5. Refuse list: inventing velocity points, inventing estimate totals, inventing cycle burn, inventing assignee loads. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented velocity VALUES. Teach Linear cycle and issue mapping, not a generic backlog swap. - Honor Version. No emojis.
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.
Linear Project Brief from Outcome Notes (No Invented Assignees) with example still
Draft a Linear project brief from outcome notes. No invented assignees, due dates, or issue IDs.
Act as an editor for this job: Linear Project Brief from Outcome Notes (No Invented Assignees). Goal: Draft a Linear project brief from outcome notes. No invented assignees, due dates, or issue IDs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Linear Project Brief from Outcome Notes (No Invented Assignees). - No invented evidence. Honor Cap. No emojis.
Linear Issue Template from Workflow Brief (No Invented Assignees)
Design a Linear issue template from a workflow brief. No invented assignees, SLAs, or cycle dates.
Act as an editor for this job: Linear Issue Template from Workflow Brief (No Invented Assignees). Goal: Design a Linear issue template from a workflow brief. No invented assignees, SLAs, or cycle dates. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Linear Issue Template from Workflow Brief (No Invented Assignees). - No invented evidence. Honor Cap. No emojis.
Linear Issue Template Pack from Workflow Brief (No Invented Assignees)
Build a Linear issue template pack from a workflow brief. No invented assignees, due dates, or estimates.
Act as an editor for this job: Linear Issue Template Pack from Workflow Brief (No Invented Assignees). Goal: Build a Linear issue template pack from a workflow brief. No invented assignees, due dates, or estimates. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Linear Issue Template Pack from Workflow Brief (No Invented Assignees). - No invented evidence. Honor Cap. No emojis.