KIDO Events

KIDO for investors

What 404 sources teach you about a local market

KIDO’s value is not a long list of links. It is the system that turns fragmented activity information into structured evidence, learns from corrections, and serves families and organizations from the same data.

Blog Live Build Report

The catalog is visible. The operating knowledge behind it is the harder asset to reproduce.

Every provider, calendar, registration system, PDF, and municipal site describes local activities differently. KIDO makes that fragmented supply comparable without hiding the evidence or the gaps.

  • One structured layer for families and organizations
  • Repeatable collection for stable sources
  • Corrections captured as reusable rules
  • Trust built into publication, not added later

Market shape

The market is fragmented before it is searchable

A family looking for a summer camp, a weekend event, or a weekly class is searching across municipal systems, libraries, studios, clubs, ticketing platforms, PDFs, and provider websites. Each source describes ages, dates, schedules, prices, and availability differently. A directory can collect the links. It takes a data system to make the choices comparable.

KIDO currently represents 9,894 events, camps, and programs from 404 sources in Waterloo Region. The useful asset is not only that catalog. It is the accumulated knowledge required to identify a listing, preserve its evidence, classify it consistently, resolve its location, and keep it current as the source changes.

9,894normalized events, camps, and programs
404represented public sources
3,879one-time and date-based events
6,015camps and recurring programs

Operating leverage

Repeatable collection makes each source more valuable

Stable sources use deterministic APIs, feeds, paging, and mappings. Source-provided dates, prices, ages, schedules, and descriptions remain authoritative. AI is reserved for bounded judgment such as assigning a genuinely new listing to KIDO’s taxonomy. Later runs preserve stable decisions while continuing to update facts from the source.

The live Build Report records 537 source runs, with 521 completed successfully. During the reporting window, 530 data-focused work requests accompanied 20,002 ingested records. That relationship is not an accuracy score. It is a useful view of steering load and whether coverage becomes more repeatable as the system learns.

One request can improve hundreds of records, and one difficult record can require several requests. KIDO reports the work without turning it into a false record-error percentage.

Compounding knowledge

Corrections become part of the product

Local activity data contains many small traps. A deposit is not the base price. A registration portal is not always a public evidence page. An online program needs an explicit delivery mode. A recurring class should not become dozens of separate events. A provider’s theme should not override what a particular listing actually offers.

KIDO records these corrections, then moves repeated lessons into code, configuration, validation, or focused tests. The next similar source benefits from the last difficult one. That accumulated operating knowledge is the part of the system that compounds.

Preserve evidence

Keep the original source and public verification path attached to the normalized record.

Turn judgment into a rule

Move repeated corrections into enforceable code, configuration, validation, and tests.

Reuse one data layer

Support browsing, organization tools, reporting, and new product surfaces from the same structured records.

Keep approval separate

Collection, review, local publication, and production release remain distinct decisions.

Trust architecture

Missing information stays visible

Every normalized record currently has source evidence and a usable location mode. Age coverage is 99.8 percent, date or ongoing-status coverage is 99.9 percent, and registration-link coverage is 99.7 percent. These are completeness measures, not proof that every field is correct.

The gaps remain visible too. Structured price coverage is 93.9 percent and listing-image coverage is 64 percent. Some sources legitimately omit those fields. KIDO treats missing coverage as a review signal instead of inventing a value. A successful ingest also does not automatically become public data.

Shared infrastructure

One data layer can serve the whole market

Families use the normalized catalog to compare activities, filter by age and date, save ideas, follow organizations, and ask KIDO for relevant options. Hard constraints such as age, date, price, location, and listing type stay deterministic even when semantic search helps interpret a request.

Organizations use the same records to claim their presence, manage source-driven updates, answer questions, and see which pages families discover. Search, provider tools, reporting, and future market analysis can share the underlying source work instead of rebuilding it for each surface.

The visible product is local discovery. The durable system is the evidence, workflow, and accumulated judgment that make local discovery trustworthy and repeatable.

See the evidence

Follow the operating record as it changes

The live reports stay separate from this editorial view so their measurements can update with the project.