Start here — Ontario Electricity Evidence Workspace

Welcome. You do not need to know MirrorArc, energy data, or knowledge graphs to use this example. This page is your five-minute tour of a source-backed workspace built for both people and AI agents.

Public demo boundary: this is a clean-room educational example built from public Ontario energy material and labelled synthetic fixtures. It was assembled independently from the official sources in Public source register and contains no live or forward-looking output.

MirrorArc in one sentence

MirrorArc keeps original records authoritative, creates readable Markdown mirrors beside them, and connects sources, findings, decisions, and operating guidance into one governed documentation layer.

Take the five-minute tour

1. Read the workspace story. Open Ontario Electricity Evidence Workspace overview to understand

what is included and why this example exists.

2. See the evidence chain. Open Evidence layers and trust, then choose Relationship map.

Follow an original Word, spreadsheet, or repository record into its generated Markdown mirror and onward to curated knowledge.

3. Compare the three views. Use Document view for readable content, Document metadata

for provenance and lifecycle state, and Relationship map for connected context.

4. Inspect a quality decision. Open Quality gate pipeline. Its historical completeness and

reconciliation rules are explicit, so a reader can see why a row passes or fails.

5. Build agent context deliberately. Add a few records to the context pack. MirrorArc exports

paths, provenance, lifecycle metadata, and relationships—not a second uncontrolled copy of every document body.

For a click-by-click version, open Demo walkthrough.

Three things to notice

• Original and mirror are different objects. The original remains the source of truth; the

Markdown mirror is derived, refreshable, searchable, linkable, and easier for agents to inspect.

• The documentation layer accumulates knowledge. Contracts, findings, quality checks, decisions,

and runbooks connect to evidence instead of being rediscovered in every chat.

• Governance is visible. Provenance, lifecycle state, licensing, retention, and publication

boundaries travel with the documentation layer.

Choose your path

• New to the subject? Start with Questions this workspace answers and

Ontario electricity glossary.

• Reviewing evidence? Start with Public source register, Evidence lineage map, and

Cross-source evidence synthesis.

• Reviewing outputs? Start with Stakeholder brief index and Output relationship map.
• Operating the workspace? Start with Source freshness policy,

Refresh public sources runbook, and Example release checklist.

• Working as an AI agent? Read Evidence layers and trust first, cite the authoritative

record, and consolidate existing notes before creating new ones.

Workspace map

The links below are the complete navigation index. You can also use the catalog on the left or search by document, source, or relationship.

Orientation

• Ontario Electricity Evidence Workspace overview
• Questions this workspace answers
• Ontario electricity glossary
• Evidence layers and trust
• Demo walkthrough

Sources and contracts

• Public source register
• Ontario Energy Report 2023 supporting data
• OEB open data directory
• IESO Data Directory
• IESO Year in Review
• IESO zonal map reference
• Source freshness policy
• Annual demand contract
• Monthly demand range contract
• Generation output contract
• Intertie flow contract
• Evidence API contract

Pipelines and analysis

• Public data ingestion pipeline
• Normalization pipeline
• Quality gate pipeline
• Artifact mirroring pipeline
• Evidence lineage map
• 2023 annual demand finding
• 2023 generation mix finding
• 2023 peak demand finding
• 2023 intertie flow finding
• Cross-source evidence synthesis

Outputs

• Stakeholder brief index
• Output relationship map

Governance and operations

• Open data license register
• IESO reference-only boundary
• Decision - use a clean-room public corpus
• Evidence workspace risk register
• Evidence controls
• Retention and refresh policy
• Refresh public sources runbook
• Source outage runbook
• Data quality investigation runbook
• Example release checklist
• Illustrative stale-source incident
• Freshness dashboard specification