Simulation · Musterdorf
DEFRITEN
Enter the demo

  1. I am Tura. Name the goal, I find the way. You are looking at Musterdorf, Quartura’s demo world; everything here is simulated. Tap a question whenever you like.

  2. You: /impressum

  3. Legal notice

    Fixed text · not worded by Tura

    Operator: persist GmbH

    Address: Rütisteig 1, 5210 Windisch, Switzerland

    UID: CHE-172.488.919 (VAT)

    Commercial register: Commercial register of the Canton of Aargau

    Responsible: Flavio Müller, Managing Director

    Contact: hello@persist.ch

  4. This is what the data state of a simulated grid area looks like right now:

    Metering events processed since 1 October 2026

    26,894,309,985

    Import daily at 06:00 · 57,600,000 values per day (300,000 metering points × 2 directions × 96)

    Throughput

    9,500 per second

    2 silos · Import segment 17

    Queue

    178,380 events

    Lead time ≈ 18.8 s

    ReceivedMetering pointQuarter-hourkWhValue status
    –––––
    –––––
    –––––
    –––––
    –––––

    Data state of 3 November · 300,000 metering points

    86 %90 %95 %100 %00:0006:0012:0018:0024:00

    W true value E substitute value V provisional G disturbed F missing

    Billable (W and E): 98.11 %HES segment North 01–07 without data, communication fault 09–10, hourly-read meters are missing until the next import. Substitute values per MC-CH 2025 §6.3; G and F are never sent.

    Simulation · illustrative values

    Musterdorf read

  5. The path of a rule change, proposed here by an agent:

    Substitute value formation · interpolation limit 2 h → 3 hproposed by an agent, decided by people, computed by deterministic code

    1. 1ProposalAgent “Measurement data” on behalf of the head of meteringInterpolation up to 2 h → 3 hrules.explain
    2. 2BranchCopy of the rule set, existing data unchangedBranch ersatzwert-3hbranch.open
    3. 3Re-runOctober against 300,000 metering points, as of today57.6 m values per daybranch.runHarness
    4. 4Differencemain against Branch: values and aggregates226,440 quarter-hours F → Ebranch.compare
    5. 5Change requestwith evidence and checks, four-eyes approval1 warning, 0 blockschange.submit
    6. 6Activenew rule set valid from 1 NovemberRule set hash 9f3c…a1change.status
    October 2026 · impact estimatemainBranchDifference
    Quarter-hours F412,680186,240−226,440
    Quarter-hours E3,214,5603,441,000+226,440
    LGS/LE series changed–37 of 2,88037
    Billable (W and E)99.63%99.64%+0.01 pp
    Grid usage OctoberRoadmapCHF 10,284,610.35CHF 10,291,403.55+CHF 6,793.20
    • Warn Interpolation beyond 2 h deviates from MC-CH 2025 §6.3 (default rule, deviation allowed with a reason)
    • Info Takes effect on 1 November; the October figures are an impact estimate, earlier periods stay unchanged as of their capture.

    Approved by the head of metering. Proposal, evidence, approval and rule set are in the audit log; the agent is logged with the responsible person.

    Musterdorf read

  6. Why this matters to you:

    MCP first: Every capability starts as a tool; the interface uses the same ones. Your model, your agent: no AI provider hard-wired.

    AI with limits: Agents propose, deterministic code checks and computes. Every action of an agent is logged with the responsible person.

    Branch before approval: Rule and tariff changes, including an agent’s, run against your data first: difference per metering point and aggregate, then approval with evidence.

    Art. 17c StromVGArt. 19b StromVVArt. 31e StromVV

  7. What brings you here? With your answer I tailor the examples.

  8. Ask live

    If you like, tap a question: Tura reads it live from the Musterdorf simulation.

  9. Next step

    With a code you enter the demo.

    Or write to us, and we will show you the world with your questions.