🔄 Procedures-Feed Staleness Mitigation Record

May 15, 2026 · View on GitHub

📌 Template Instructions: Copy to analysis/daily/{date}/{article-type}-run{N}/intelligence/procedures-proxy.md. Produced whenever get_procedures_feed returns the known 1972–1987 tail (STALENESS_WARNING). Documents the mitigation chain applied and provides the adopted-texts proxy evidence. Referenced from mcp-reliability-audit.md §"Data-source bridge".

🎯 Purpose: Standardised record of the get_procedures_feed staleness pattern and the mitigation applied. Prevents each agent from re-discovering and re-documenting the same known upstream limitation independently. See the authoritative triage entry in .github/prompts/07-mcp-reference.md §11.

⚠️ Staleness Incident Record

Field	Value
Tool called	`get_procedures_feed`
STALENESS_WARNING detected?	Yes (present in `dataQualityWarnings`) / No
Returned era	1972–1987 (expected EP upstream tail) / other
Items returned	N items (stale)
Is this a new defect?	No — known EP upstream limitation (documented behaviour)
Triage reference	`.github/prompts/07-mcp-reference.md §11 "Procedures-feed staleness"`
Action	Do NOT file a new upstream issue — apply adopted-texts proxy mitigation below

1️⃣ Staleness Mitigation Chain

%%{init: {"theme":"dark","themeVariables":{"primaryColor":"#1565C0","primaryTextColor":"#ffffff","primaryBorderColor":"#0A3F7F","lineColor":"#90CAF9","secondaryColor":"#2E7D32","secondaryTextColor":"#ffffff","tertiaryColor":"#FF9800","tertiaryTextColor":"#000000","mainBkg":"#1565C0","secondBkg":"#2E7D32","tertiaryBkg":"#FF9800","noteBkgColor":"#FFC107","noteTextColor":"#000000","errorBkgColor":"#D32F2F","fontFamily":"Inter, Helvetica, Arial, sans-serif"}}}%%
flowchart LR
    A["get_procedures_feed<br/>⚠️ STALENESS_WARNING<br/>1972–1987 tail"] -->|"Known upstream limitation"| B["Ignore stale feed<br/>Do NOT re-file issue"]
    B --> C["get_procedures<br/>paginated list<br/>✅ Current data"]
    B --> D["get_adopted_texts<br/>✅ Outcome proxy"]
    C --> E["Procedure stages<br/>current as of run date"]
    D --> F["Adopted outcomes<br/>confirm procedure completions"]
    E --> G["Legislative pipeline analysis<br/>Stage B artifacts"]
    F --> G

    style A fill:#FF9800,color:#000000
    style B fill:#9E9E9E,color:#ffffff
    style C fill:#2E7D32,color:#ffffff
    style D fill:#2E7D32,color:#ffffff
    style G fill:#1565C0,color:#ffffff

2️⃣ Fallback Data Sources Used

Source	Tool	Outcome	Records	Freshness
Procedures list (primary fallback)	`get_procedures` (paginated, `limit=50`)	✅ current / ❌ empty	N procedures	Current
Adopted texts (outcome proxy)	`get_adopted_texts` (current year)	✅ available / ❌ empty	N texts	Published YYYY-MM-DD
Plenary decisions (session-level proxy)	`get_meeting_decisions` (per sitting)	✅/❌	N decisions	Per session

Fallback narrative:

State which tools were called, how many records each returned, and whether the combination provides sufficient procedure-stage data for the analysis period. Example: "get_procedures returned N active procedures with committee/rapporteur assignments; get_adopted_texts confirmed M procedure completions in the period."

3️⃣ Procedure Coverage (Via Fallback)

One row per procedure in scope that would normally be sourced from get_procedures_feed.

Procedure code	Title (short)	Stage (from `get_procedures`)	Adopted? (from `get_adopted_texts`)	Confidence
20XX/NNNN(COD)	Short title	Committee / Plenary / Trilogue / Adopted	Yes / No / Pending	🟢/🟡
20XX/NNNN(COD)	Short title	Stage	Yes/No/Pending	🟢/🟡

4️⃣ Impact on Stage-B Artifacts

Artifact	Impact of procedures-feed staleness	Mitigation applied
`intelligence/voting-patterns.md`	Low — voting analysis uses RCV data, not procedures feed	None
`intelligence/legislative-pipeline-forecast.md`	Medium — transit-time priors may be incomplete	Used `get_procedures` paginated list as data source
`intelligence/mcp-reliability-audit.md`	Documented — logged as known limitation	Reference this artifact
`risk-scoring/legislative-velocity-risk.md`	Medium — stalled procedures detection uses feed	Used `get_procedures` + `get_adopted_texts` proxy
All other artifacts	Low	None — reference this artifact for context

5️⃣ Confidence Assessment

Field	Value
Procedure stage data confidence	🟢 HIGH (from `get_procedures` paginated list)
Procedure outcome data confidence	🟢 HIGH (from `get_adopted_texts`)
Procedures-feed staleness impact	Negligible — mitigated by fallback sources
Admiralty grade for fallback data	A2 (`get_procedures` is an authoritative EP source)

🔗 Cross-References

.github/prompts/07-mcp-reference.md §11 — Audit-Recurring Items Triage Table (procedures-feed staleness is a documented behaviour, not a defect)
../mcp-reliability-audit.md — parent audit artifact; §"Data-source bridge" references this file
../data-availability-assessment.md — Stage A triage artifact; §5 "Procedures-Feed Staleness Note" triggers this template
../../methodologies/osint-tradecraft-standards.md — Admiralty grade for EP API sources

Document Control: analysis/templates/intelligence/procedures-proxy.md · Template v1.0 · Triggered by: get_procedures_feed STALENESS_WARNING · See .github/prompts/07-mcp-reference.md §11 for the authoritative triage classification.