implementation-feasibility.md

May 24, 2026 Β· View on GitHub

Hack23 Logo

πŸ› οΈ Implementation Feasibility Template

πŸ“Š Can the Policy Actually Be Delivered β€” By When, At What Cost, With What Risks?
🎯 Legal · Administrative · Technical · Fiscal · Workforce · Timeline

Owner Version Effective Date Classification

πŸ“‹ Document Owner: CEO | πŸ“„ Version: 1.2 | πŸ“… Last Updated: 2026-04-25 (UTC) 🏒 Owner: Hack23 AB (Org.nr 5595347807) | 🏷️ Classification: Public

πŸ“Œ Template instructions: Produce this document on every run. If the current bill has concrete delivery obligations (budget line, infrastructure, IT system, procurement, workforce change), assess that bill directly; otherwise, use this template to audit implementation feasibility for the relevant delivery backlog or previously announced measures. Save as analysis/daily/${ARTICLE_DATE}/${DOC_TYPE}/implementation-feasibility.md.

✨ What to produce: A structured feasibility review across six delivery dimensions (Legal, Administrative, Technical, Fiscal, Workforce, Timeline) with evidence and a calibrated overall-feasibility verdict (READY / FEASIBLE / CONSTRAINED / HIGH-RISK / UNLIKELY).


πŸ“ Template Contract β€” every fill of this template MUST satisfy this row.

SlotValue
Owning methodologyper-artifact-methodologies.md
Owning gate checkCheck 8 (Family D) + Check 9b (Statskontoret evidence) β€” see 05-analysis-gate.md
Required inputsStatskontoret index, agency capacity, risk-assessment.md
Horizon bandmixed (T+30…T+365) (per scripts/horizon-context.ts)
Output familyFamily D β€” Electoral & Domain
Aggregation order20 of 30 in canonical order (see scripts/render-lib/aggregator/order.ts)
Reader Intelligence Guiderow generated from implementation-feasibility.md (see scripts/render-lib/aggregator/reader-guide.ts)
Canonical evidence anchor| claim | evidence (dok_id / vote / MP intressent_id / primary-source URL) | retrieved_at | confidence | β€” every analytical claim row uses this schema.

Cross-reference: README.md Β§Template ↔ Methodology ↔ Gate-Check Matrix.

πŸ”„ Tradecraft Context

ElementValue
F3EAD StageANALYZE β€” delivery risk assessment
PIRs ServedPIR-5 (Fiscal Trajectory β€” budget feasibility), PIR-7 (Democratic Norms β€” accountability for delivery)
Admiralty FloorMinistry statements require [B2]; budget figures require [A1] (official appropriation documents)
WEP + ODNIDelivery-risk scenarios use WEP (likely/unlikely for on-time delivery); confidence MODERATE (ministries rarely disclose implementation challenges publicly)
Source Diversity FloorP1 (delivery-risk claims): β‰₯3 sources (budget dok_id + ministry statement + expert assessment); avoid single-ministry-spokesperson claims
SAT(s) AppliedPremortem Analysis (assume failure and explain why), Key Assumptions Check (delivery assumptions)
ICD 203 Standards2 (uncertainties β€” delivery risks), 5 (customer relevance β€” implementation milestones), 6 (logical argumentation)

πŸ“‹ Feasibility Context

FieldValue
Feasibility IDFEA-YYYY-MM-DD-NNN
GeneratedYYYY-MM-DD HH:MM UTC
Subject measuredok_id and short title
Responsible ministry / agencye.g., Finansdepartementet + Skatteverket
Statskontoret relevanceRelevant report/page URL or "none found"
Declared start dateYYYY-MM-DD
Declared completion dateYYYY-MM-DD
Budget envelopeSEK X.Y billion
Overall verdict🟒 READY / 🟒 FEASIBLE / 🟑 CONSTRAINED / 🟠 HIGH-RISK / πŸ”΄ UNLIKELY

🧭 Feasibility Overview

Rendering note: Mermaid 11 core does not ship the radar diagram type. The canonical fallback below is a graph LR "spoke" chart that conveys the same per-dimension score (1–5) and colour-codes each spoke by traffic-light status. Restore a radar variant only once the renderer enables the plugin and the validator (npm run validate:mermaid) accepts it.

graph LR
    D1["βš–οΈ Legal<br/>4/5"] --- OUT["🏷️ Overall<br/>🟑 CONSTRAINED"]
    D2["πŸ›οΈ Administrative<br/>3/5"] --- OUT
    D3["πŸ–₯️ Technical<br/>4/5"] --- OUT
    D4["πŸ’° Fiscal<br/>3/5"] --- OUT
    D5["πŸ‘· Workforce<br/>2/5"] --- OUT
    D6["πŸ—“οΈ Timeline<br/>3/5"] --- OUT

    style D1 fill:#4CAF50,color:#FFFFFF
    style D2 fill:#FFC107,color:#000000
    style D3 fill:#4CAF50,color:#FFFFFF
    style D4 fill:#FFC107,color:#000000
    style D5 fill:#D32F2F,color:#FFFFFF
    style D6 fill:#FFC107,color:#000000
    style OUT fill:#FF9800,color:#FFFFFF

πŸ“Š Dimension-by-Dimension Review

CheckStatusEvidence
Constitutional authority (Regeringsformen)🟒Within budgetary prerogative
EU compatibility🟑State-aid risk flagged; notification path open
Secondary-law impact🟒Skattelag amendment required, scheduled
Litigation exposure🟒Low

πŸ›οΈ Administrative feasibility β€” 3/5

Statskontoret overlay: administrative-capacity, coordination, backlog, regulatory-burden and efficiency claims should cite Statskontoret first when a relevant public report/page exists. Record URL, report title, publication date, retrieval time and Admiralty grade in data-download-manifest.md.

CheckStatusEvidence
Responsible agency capacity (Skatteverket)🟑Prior surcharge adjustment completed in 4 months; validate against relevant Statskontoret report/page where available
Inter-agency coordination (SCB, Tullverket)🟒Precedent exists
Guidance-document turnaround🟑Normal 90-day cycle
Reporting / auditing🟒Standard reports available

πŸ–₯️ Technical feasibility β€” 4/5

CheckStatusEvidence
IT systems change (Skatteverket)🟒Tax-rate parameter update
Fuel-monitoring system integration🟒Petrol-station price reporting already in place
Data pipeline / reporting🟒Existing telemetry
Cyber-risk exposure🟑Standard elevated-attention review

πŸ’° Fiscal feasibility β€” 3/5

CheckStatusEvidence
Budget envelope sufficient🟑SEK 2.8 B annualised vs. estimated SEK 2.4 B
Revenue offset identified🟠Not explicitly earmarked
Debt-ceiling impact🟒Within surplus-target tolerance
Future-year commitments🟑Sunset clause at 12 months but renewal risk

πŸ‘· Workforce feasibility β€” 2/5

CheckStatusEvidence
Staff available at Skatteverket🟠Existing hiring freeze
Skill mix (policy + IT + call-centre)🟠Call-centre surge capacity limited
Contractor routes🟑Ramavtal (framework agreements) available but slow
Training needs🟒Minimal

πŸ—“οΈ Timeline feasibility β€” 3/5

gantt
    title HD03236 Implementation Timeline
    dateFormat YYYY-MM-DD
    section Legal
    FiU committee process    :done,   l1, 2026-04-15, 2026-04-21
    Chamber vote             :active, l2, 2026-04-22, 3d
    SFS publication          :        l3, after l2, 5d
    section Administrative
    Skatteverket guidance    :        a1, 2026-05-01, 30d
    Call-centre scaling      :        a2, 2026-05-15, 45d
    section Technical
    IT parameter update      :        t1, 2026-05-10, 10d
    Price-reporting update   :        t2, 2026-05-20, 14d
    section Effect
    Pump-price drop visible  :milestone, pe, 2026-07-15, 0d

🚦 Critical Dependencies

#DependencyOwnerRisk if missed
D1Chamber vote passes by 2026-04-24KammarenEntire package delayed
D2SFS publication within 5 days post-voteRegeringskanslietDelays IT update
D3Skatteverket IT parameter changeSkatteverketImplementation date slips
D4Call-centre staffingSkatteverket HRCitizen complaints surge
D5EU-Commission non-interventionCommissionFormal review forces 6-12 m delay

🧯 Risk Register (feasibility-specific)

#RiskLIScoreMitigation
FR-1EU state-aid review opens before SFS3515Pre-notify Commission now
FR-2Call-centre capacity overwhelmed4312Activate framework contract
FR-3Price-reporting integrity issues248Independent pump-price audit
FR-4Revenue-offset gap breaks surplus target3412Identify offset before Q3 budget
FR-5Workforce gap at Skatteverket4312Emergency hiring authorisation

πŸ“Š Comparable Delivery Benchmarks

Comparable measureDelivery timeOutcome
2022 Electricity-price support6 months to first paymentDelivered but with CRM overload
2019 Reduced VAT on e-books5 monthsOn-time, minimal issues
Norway StrΓΈmstΓΈtte 20233 monthsDelivered with price-cap simplification

βœ… Verdict and Preconditions

Overall: 🟑 CONSTRAINED β€” deliverable by declared date only if D1, D3, D4 land on schedule and EU Commission does not intervene.

PreconditionStatusAction required
EU pre-notification submittedπŸ”΄ Not doneOpen dialogue this week
Call-centre surge contract triggeredπŸ”΄ Not doneAuthorise by 2026-05-01
Revenue-offset identifiedπŸ”΄ Not doneInclude in Q3 budget bill

LinkPath
Risk registerrisk-assessment.md
Scenario analysisscenario-analysis.md
Comparative internationalcomparative-international.md
Per-document analysisdocuments/HD03236-analysis.md

Document Control


βœ… Pass-2 Self-Audit Checklist (v4.4 β€” required)

Purpose: AI-FIRST principle requires a Pass-2 read-back-and-improve. After producing this artifact in Pass 1, re-read it end-to-end and verify each item below. Document any remediation in methodology-reflection.md §"Pass-2 audit log". Any unchecked ❌ box at the end of Pass 2 forces a Pass-3 rewrite of the affected section.

  • Tradecraft anchors honoured β€” F3EAD stage matches the artifact's role; PIRs declared in the Β§Tradecraft Context block are actually addressed in the body; Admiralty grades attached to every external source; WEP band + ODNI confidence on every probabilistic judgement.
  • Source diversity floor met β€” at least the minimum number of independent MCP sources required by the artifact's tradecraft block are cited; single-source claims are explicitly labelled [SINGLE-SOURCE β€” corroboration pending].
  • Evidence specificity β€” every quantified claim cites a dok_id (Riksdag), an SCB / IMF dataflow code, or a named external source with date; no "according to data" / "studies show" hand-waves.
  • Named-actor discipline β€” every political claim names β‰₯ 1 person (party + role + dated act/quote) or labels the absence ([diffuse β€” no named actor]).
  • Counter-narrative present β€” at least one explicit competing hypothesis, dissent quote, or framed objection appears in the body; "no opposition recorded" is itself a finding to label, not silence.
  • Election 2026 lens applied β€” the Β§"Election 2026 Implications" subsection (or equivalent) addresses electoral salience, coalition pressure, and forward indicators; not boilerplate.
  • No illustrative content shipped as fact β€” every [REQUIRED] placeholder is filled OR removed; every Example: block is clearly fenced or removed; no fabricated dok_id, vote count, or quote leaks into the final artifact.
  • Cross-references resolve β€” every [link](file.md) in this artifact points to a file that exists in the run folder (analysis/daily/$ARTICLE_DATE/$SUBFOLDER/) or to a methodology / template under analysis/.
  • Mermaid renders β€” every fenced ```mermaid block parses (no missing class definitions, no orphan nodes, no >40-node graphs that overflow viewport on mobile).
  • Line-floor check β€” artifact length β‰₯ the per-artifact floor in reference-quality-thresholds.json; shorter artifacts trigger Pass-2 rewrite, never a [truncated] note.