MirrorArc
Data Product
Local content-inclusive · contains rendered Markdown

Public beginner tour · INDEX.md

Start here — Ontario Electricity Evidence Workspace

public examplecrawlable HTML
Browse documentationAbout MirrorArcRead Markdown

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 sources recorded in ../DATA_PROVENANCE.md and contains no live or forward-looking output.

MirrorArc in one sentence

MirrorArc keeps original records authoritative, creates one readable L1 Markdown projection for each opaque source, records relationships as governed data, and renders a few purpose-specific L2 views without growing a second curated-note pile.

Take the five-minute tour

  1. Read the workspace story. This guide describes what is included and why this example exists.
  2. See the evidence chain. Choose Relationship map. Follow an original Word, spreadsheet,

    3. or repository record into its generated L1 projection and onward through governed relationships.

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

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

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

    5. 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 metadata-only selection pack, or

    6. use mirrorarc context to resolve a dynamic definition or create a bounded offline frozen pack.

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.

  • Relationships are data; synthesis is a view. Contracts, quality checks, decisions, and

    • runbooks remain authoritative records. Cross-source interpretation is rendered through a small set of cited L2 lenses and persists only when explicitly pinned or reviewed.

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

    • boundaries travel with the documentation layer.

Choose your path

Questions and terms

This example can answer historical questions about annual demand, monthly peak-to-minimum range, the grid-connected generation mix, intertie imports and exports, redistribution boundaries, and the checks that reject incomplete or inconsistent historical rows. Answers must cite an original source or L1 projection and connect to a contract or quality check.

TermWorking meaning in this example
DemandElectricity consumed in Ontario at the source-defined measurement boundary.
Peak / minimum MWHighest / lowest reported interval demand for a period.
Generation outputElectrical energy produced, grouped by fuel type, in GWh or MWh.
Intertie flowElectricity imported from or exported to neighbouring jurisdictions.
Emissions intensityGreenhouse-gas emissions per unit of generated electricity.

These navigation definitions do not replace source-specific contracts.

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 and governed views

  • Demo walkthrough
  • orientation lens — current evidence and review work
  • change-digest lens — changed evidence and affected outputs

Sources and contracts

Pipelines and analysis

Outputs

Governance and operations