ERP Reference Desk

Why it matters

A proposal, a response to feedback, and an implemented requirement are different evidence states.

Confirmed design

ERP uses presentations, feedback forms, submissions, responses, and design memos as distinct engagement artifacts.
Sources: Presentation · Feedback Form · IESO Response to Feedback

Implementation status and limitations

Ongoing; use each document's current, supporting, or superseded label.

Engagement publication does not by itself prove market-rule or production-system implementation.
Sources: Enabling Resources Program - Framework and Modules

Open questions

What are the final rule-amendment and implementation dates for each Phase 1 module?

Build a handoff from this dossier

Build a source-bounded prompt locally. Nothing is sent until you choose what to do with it.

Question or outcomeAnalysis depth

Selected evidenceEnabling Resources Program - Framework and ModulesIESO Response to Feedback

Generated handoff

# ERP Phase 1 evidence handoff

## Outcome
Explain the selected ERP material and identify the implications for Phase 1 work.

## Selected evidence
- [2024-11-20-design-memo-enabling-resources-program-framework-and-modules-6a283195] Enabling Resources Program - Framework and Modules — IESO; 2024-11-20; authority: primary-supporting; review: reviewed; https://www.ieso.ca/-/media/Files/IESO/Document-Library/engage/erp/erp-20241120-design-memo.pdf
- [2025-03-19-response-ieso-response-to-feedback-189865b9] IESO Response to Feedback — IESO; 2025-03-19; authority: ieso-response; review: unreviewed; https://www.ieso.ca/-/media/Files/IESO/Document-Library/engage/erp/erp-20250319-Response-to-Feedback.pdf

Selected concept dossiers:
- [engagement-and-implementation] Engagement and Implementation: The sequence from design material, stakeholder engagement, IESO response, and rule or system implementation.

## Authority rules
- Treat current IESO-authored design memos as controlling program design unless a later Market Rule, Market Manual, or IESO publication supersedes them.
- Do not claim implementation unless a Market Rule, Market Manual, or other official implementation source proves it.
- Keep stakeholder submissions attributed to their authors; attribute stakeholder positions and do not present them as IESO decisions.
- Use superseded and historical sources only for lineage. Label what changed.
- Treat recordings as catalog-only unless a reviewed transcript is explicitly supplied.
- If two sources conflict, prefer the later higher-authority source and describe the conflict.

## Citations
Cite every substantive claim with document title, publication date, page when available, document ID, and canonical URL. Never invent a page number.

## Known gaps
- 2025-03-19-response-ieso-response-to-feedback-189865b9: unreviewed; ieso-response. Verify before relying on content-specific claims.

## Requested depth
Give a practical, structured analysis suitable for daily program work. Distinguish confirmed design, history, stakeholder feedback, and open questions.

## Answer format
1. Direct answer
2. Confirmed ERP design
3. Historical or stakeholder context
4. Phase 1 implications
5. Open questions and evidence gaps
6. Source list

Work only from the selected evidence. If the evidence is insufficient, say exactly what is missing.

Open ChatGPT Open Codex