🏷️ Riksdagsmonitor — Label System

🤖 Automated Pull-Request & Issue Categorisation
🎯 File-Path Routing · Title Detection · Body Heuristics · GitHub Actions Driven

📋 Document Owner: CEO | 📅 Last Updated: 2026-05-03 (UTC) | 🏢 Owner: Hack23 AB (Org.nr 559534-7807) | 🏷️ Classification: 🟢 Public

🆕 What changed since last review (v1.0 → v1.1, 2026-05-03):

• 🔄 Drift reconciliation with the live label set (gh label list --repo Hack23/riksdagsmonitor --limit 300): the repository now carries 159 labels (was 46 in v1.0). The categories below cover the original 46 plus 113 agentic-newsroom additions, grouped as:
  • Agent ownership: agent:news-journalist, agent:security-architect, agent:documentation-architect, agent:data-pipeline-specialist, agent:intelligence-operative
  • Component routing: component:content, component:visualization, component:i18n, component:navigation, component:news, component:ai-workflows, component:security, component:architecture, component:cia-data, component:data-integration, component:data-pipeline, component:workflow, component:strategy, component:future, component:performance, component:dashboard, component:documentation
  • Priority (canonical & legacy): priority:critical, priority:high, priority:medium, priority:low (legacy priority-critical, priority-high, priority-medium, priority-low still active)
  • Type: type:feature, type:documentation, type:security, type:accessibility, type:monitoring
  • Agentic newsroom: agentic-workflows, agentic-workflow, agentic-news, automated-news, news-generation, news-content, news-article, auto-generated, ai-generated, needs-editorial-review, analysis-data, analysis-only
  • Article horizons & types: realtime-monitor, realtime-pulse, evening-analysis, week-ahead, month-ahead, year-ahead, long-horizon, forward-look, weekly-review, monthly-review, committee-reports, propositions, motions, interpellations, interpellation-debates, opposition-motions, article:motions
  • Language tracks: lang:en, lang:sv, multi-language, translations
  • Pipeline: automated-pipeline, economic-context, cia-intelligence, data-update, heartbeat, news/content, content
  • Tooling: npm, github-actions, code-quality, frontend, refactoring, typescript, validation, maintenance
• 📋 The taxonomy is documented categorically below; for the canonical machine-readable taxonomy see .github/labeler.yml and the setup workflow .github/workflows/setup-labels.yml.

This document describes the automatic labeling system for the riksdagsmonitor repository. Labels are automatically applied to pull requests based on file changes, PR titles, and PR body content.

---

📋 Overview

The riksdagsmonitor repository uses an automated labeling system powered by GitHub Actions to categorize pull requests and issues. This helps maintain organization, improves searchability, and provides quick visual context about changes.

Key Features

• ✅ Automatic labeling based on file paths, PR titles, and descriptions
• ✅ 159 labels total — 46 base labels managed by setup-labels.yml + 113 labels created dynamically by agentic workflows, GitHub Actions labeler, and manual additions
• ✅ Size labels automatically calculated from PR diff
• ✅ Security hardened workflows with SHA pinning
• ✅ Status tracking with priority and progress labels
• ✅ Agentic-newsroom taxonomy: agent:* (per-Copilot-agent owner), component:* (subsystem), priority:* / priority-*, agentic-workflows, news-generation, needs-editorial-review, auto-generated, ai-generated, horizon tags (week-ahead, month-ahead, quarter-ahead, year-ahead, long-horizon, forward-look, realtime-monitor, realtime-pulse)

Note: The setup-labels.yml workflow verifies exactly 46 base labels (the core taxonomy defined in the workflow itself). The remaining 113 labels are created on-the-fly by the agentic news workflows, the GitHub Actions labeler (.github/labeler.yml), and manual issue triage. The full live label set can be queried with gh label list --repo Hack23/riksdagsmonitor --limit 300.

---

🚀 Setup

Initial Setup

Run the label setup workflow to create all required labels:

1. Go to Actions → Setup Repository Labels
2. Click Run workflow
3. (Optional) Check "Recreate all labels" to delete existing labels first
4. Wait for completion (usually < 1 minute)

Direct link: Setup Repository Labels Workflow

Automatic Labeling

Once labels are created, the automatic labeler runs on every PR:

• Triggers on PR opened, synchronize, reopened, edited
• Applies labels based on .github/labeler.yml configuration
• Adds size labels based on diff statistics
• Posts a summary comment on new PRs

---

🏷️ Label Categories

🗳️ Content & Features

Labels for content generation and feature development:

Label	Color	Description
news		News articles and content generation
dashboard		Interactive dashboards (Chart.js/D3.js)
visualization		Data visualization features
intelligence		Political intelligence analysis

Auto-applies when:

• Changing files in news/, dashboard/, js/*-dashboard.js
• PR title starts with news:, dashboard:, viz:
• PR body contains - [x] 📰 News Content, - [x] 📊 Dashboard

---

💻 Technology

Labels for technical implementation:

Label	Color	Description
html-css		HTML/CSS changes
javascript		JavaScript code changes
workflow		GitHub Actions workflows
security		Security improvements

Auto-applies when:

• Changing .html, .css, .js files
• Modifying .github/workflows/ files
• Updating security documentation
• PR title starts with html:, js:, workflow:, security:

---

📊 Data Integration

Labels for data pipeline and integration:

Label	Color	Description
cia-data		CIA platform data integration
riksdag-data		Riksdag-Regering MCP data
data-pipeline		ETL and data processing
schema		Data schema changes

Auto-applies when:

• Changing files in cia-data/, data/cia/, schemas/
• Modifying scripts/load-cia-*.js, scripts/mcp-client.js
• PR title starts with cia:, riksdag:, pipeline:, schema:

---

🌍 Internationalization

Labels for multi-language support (14 languages):

Label	Color	Description
i18n		Internationalization/localization
translation		Translation updates
rtl		RTL language support (Arabic, Hebrew)

Auto-applies when:

• Changing index_*.html, sitemap_*.html, news/**/*-*.html
• Modifying TRANSLATION_GUIDE.md
• PR title starts with i18n:, translation:, rtl:

Supported Languages:

• English (EN), Swedish (SV), Danish (DA), Norwegian (NO), Finnish (FI)
• German (DE), French (FR), Spanish (ES), Dutch (NL)
• Arabic (AR), Hebrew (HE), Japanese (JA), Korean (KO), Chinese (ZH)

---

🔒 ISMS & Compliance

Labels for security and compliance frameworks:

Label	Color	Description
isms		ISMS compliance changes
iso-27001		ISO 27001 controls
nist-csf		NIST CSF compliance
cis-controls		CIS Controls

Auto-applies when:

• Changing SECURITY_ARCHITECTURE.md, THREAT_MODEL.md, CRA-ASSESSMENT.md
• Modifying .github/skills/iso-27001-controls/, .github/skills/nist-csf-mapping/
• PR title starts with isms:, iso-27001:, nist:, cis:

Frameworks:

• ISO 27001:2022 - Information security management
• NIST CSF 2.0 - Cybersecurity framework
• CIS Controls v8.1 - Security best practices

---

🏗️ Infrastructure & Operations

Labels for CI/CD and infrastructure:

Label	Color	Description
ci-cd		CI/CD pipeline changes
deployment		Deployment configuration
performance		Performance optimization
monitoring		Monitoring and alerting

Auto-applies when:

• Changing .github/workflows/ files
• Modifying CNAME, robots.txt, vite.config.js
• PR title starts with ci:, deploy:, perf:, monitoring:

---

🔄 Quality & Testing

Labels for code quality and testing:

Label	Color	Description
testing		Test coverage
accessibility		WCAG 2.1 AA compliance
documentation		Documentation updates
refactor		Code refactoring

Auto-applies when:

• Changing files in tests/, cypress/, *.test.js
• Modifying **/*.md files
• PR title starts with test:, a11y:, docs:, refactor:

---

🏷️ Standard Labels

Essential workflow labels:

Label	Color	Description
bug		Bug fixes
enhancement		Enhancements
dependencies		Dependency updates

Auto-applies when:

• PR title starts with fix:, bug:, feat:, deps:
• Changing package.json, package-lock.json
• PR body contains - [x] 🐛 Bug Fix, - [x] ✨ Enhancement

---

🤖 AI & Automation

Labels for GitHub Copilot agents and agentic workflows:

Label	Color	Description
agent		Agent configuration
skill		Skill configuration
agentic-workflow		Agentic workflow changes

Auto-applies when:

• Changing .github/agents/, .github/skills/, AGENTS.md, SKILLS.md
• Modifying .github/workflows/*.md, .github/workflows/*.lock.yml
• PR title starts with agent:, skill:, aw:

---

🚦 Priority Labels

Manual labels for prioritization:

Label	Color	Description
priority-critical		Critical priority (security, outages)
priority-high		High priority (important features)
priority-medium		Medium priority (standard work)
priority-low		Low priority (nice-to-have)

Usage: Manually add to PRs/issues to indicate urgency.

---

📏 Size Labels

Automatically calculated from PR diff:

Label	Color	Lines Changed	Description
size-xs		< 10	Extra small change
size-s		10-50	Small change
size-m		50-250	Medium change
size-l		250-1000	Large change
size-xl		> 1000	Extra large change

Auto-applies: Calculated from additions + deletions in PR diff.

---

🎭 Status Labels

Manual labels for workflow tracking:

Label	Color	Description
status-needs-review		Needs code review
status-in-progress		Work in progress
status-blocked		Blocked by dependencies
status-ready		Ready to merge

Usage: Manually add/update as PR progresses through workflow.

---

🔧 Configuration

Labeler Configuration

The automatic labeler is configured in .github/labeler.yml. Labels are applied based on:

1. File path patterns - Uses glob patterns to match changed files
2. PR title - Matches title prefixes (e.g., fix:, feat:)
3. PR body - Matches checkbox patterns (e.g., - [x] 🐛 Bug Fix)

Example:

news:
  - any:
      - changed-files:
          - any-glob-to-any-file:
              - "news/**/*.html"
              - "scripts/article-template.js"
      - title: "news:*"
      - body: "- [x] 📰 News Content"

Modifying Labels

To modify the labeling system:

1. Edit label definitions: Modify .github/workflows/setup-labels.yml
2. Edit auto-labeling rules: Modify .github/labeler.yml
3. Run setup workflow: Actions → Setup Repository Labels
4. Test on new PR: Create a test PR to verify labels

---

📊 Usage Examples

Example 1: News Article PR

Files changed:

• news/2026-02-15-riksdag-budget-vote-en.html
• news/2026-02-15-riksdag-budget-vote-sv.html

Labels applied:

• ✅ news (news article)
• ✅ html-css (HTML files)
• ✅ i18n (multi-language)
• ✅ translation (Swedish translation)
• ✅ size-s (< 50 lines)

---

Example 2: Dashboard Enhancement

Files changed:

• js/politician-dashboard.js
• politician-dashboard.html
• cia-data/politician/view_riksdagen_politician_ranking_sample.csv

PR Title: feat: Add politician influence network visualization

Labels applied:

• ✅ dashboard (dashboard changes)
• ✅ visualization (data visualization)
• ✅ javascript (JS code)
• ✅ html-css (HTML file)
• ✅ cia-data (CIA data)
• ✅ enhancement (feature)
• ✅ size-m (50-250 lines)

---

Example 3: Security Architecture Update

Files changed:

• SECURITY_ARCHITECTURE.md
• THREAT_MODEL.md
• .github/skills/iso-27001-controls/SKILL.md

PR Title: security: Update ISO 27001 control mapping

Labels applied:

• ✅ security (security changes)
• ✅ isms (ISMS compliance)
• ✅ iso-27001 (ISO 27001)
• ✅ documentation (markdown files)
• ✅ skill (skill changes)
• ✅ size-m (50-250 lines)

---

Example 4: CI/CD Workflow

Files changed:

• .github/workflows/data-pipeline.yml
• .github/workflows/quality-checks.yml

PR Title: ci: Optimize data pipeline workflow

Labels applied:

• ✅ workflow (GitHub Actions)
• ✅ ci-cd (CI/CD changes)
• ✅ data-pipeline (data pipeline)
• ✅ performance (optimization)
• ✅ size-s (< 50 lines)

---

🛠️ Troubleshooting

Labels Not Applied

Problem: Labels are not being applied to PRs.

Solutions:

1. Check if labels exist: Actions → Setup Repository Labels → Run workflow
2. Verify labeler workflow ran: Actions → Pull Request Automatic Labeler
3. Check workflow logs for errors
4. Ensure .github/labeler.yml is valid YAML

---

Missing Labels

Problem: Some labels don't exist in the repository.

Solution:

1. Go to Actions → Setup Repository Labels
2. Click "Run workflow"
3. (Optional) Check "Recreate all labels" to rebuild from scratch
4. Wait for completion
5. Re-trigger labeler on existing PRs

---

Size Label Incorrect

Problem: Size label doesn't match PR diff.

Explanation: Size is calculated from total changes (additions + deletions), not just additions.

Formula:

TOTAL_CHANGES = ADDITIONS + DELETIONS
if TOTAL_CHANGES < 10: size-xs
elif TOTAL_CHANGES < 50: size-s
elif TOTAL_CHANGES < 250: size-m
elif TOTAL_CHANGES < 1000: size-l
else: size-xl

---

📚 References

• Labeler Configuration: .github/labeler.yml
• Setup Workflow: .github/workflows/setup-labels.yml
• Labeler Workflow: .github/workflows/labeler.yml
• GitHub Labeler Action: actions/labeler
• ISMS Documentation: Hack23 ISMS-PUBLIC

---

🤝 Contributing

When contributing to the labeling system:

1. ✅ Test label changes on a test PR first
2. ✅ Document new labels in this file
3. ✅ Follow existing color scheme patterns
4. ✅ Ensure labels align with repository structure
5. ✅ Update WORKFLOWS.md if adding new workflows

---

Last Updated: 2026-02-15
Version: 1.0
Maintained by: Hack23 AB (Org.nr 5595347807)

---

🔗 Hack23 Ecosystem

🌐 Platforms	📦 Open-Source Projects	🛡️ Governance & Standards
🗳️ Riksdagsmonitor — Swedish Parliament intelligence 🇪🇺 EU Parliament Monitor — European coverage 🕵️ Citizen Intelligence Agency — political-data engine 🌐 Hack23 AB — corporate site 📰 Hack23 Blog — engineering & policy 💼 Hack23 on LinkedIn	🗳️ Hack23/riksdagsmonitor 🕵️ Hack23/cia 🇪🇺 Hack23/euparliamentmonitor 🔌 Hack23/european-parliament-mcp ✅ Hack23/cia-compliance-manager 🥋 Hack23/black-trigram 🏠 Hack23/homepage	🛡️ Hack23 ISMS-PUBLIC — public ISMS 🔒 Information Security Policy 🤖 AI Policy 🧪 Secure Development Policy 🎯 Threat Modeling Policy ⚠️ Vulnerability Management 🏷️ Classification Framework

🗳️ Empower citizens · 🔍 Strengthen democratic accountability · 🕵️ Illuminate the political process

_{© 2008–2026 Hack23 AB (Org.nr 559534-7807) · Maintainer: James Pether Sörling, CISSP CISM}