Maryland Cycling Classic
Enable an AI agent to recognise the Maryland Cycling Classic, distinguish its editions and constituent races, assess their documented status, and identify supported participation, operational and spectator actions.
Bundle → Layer → Finding → Questions Filled
6 bundles · 11 layers · 15 findings · 28 questions
Classic identity and continuity Establishes what counts as the Maryland Cycling Classic and how its editions and activities relate.
Name and authority
Connects the registry identity to documented event names and responsible organisations.
Authoritative Classic identity
Record evidence connecting official names, sponsor-qualified titles and organiser references to this registered thing.
- Which organiser or sanctioning records establish the event represented by vr.tr.maryland-cycling-classic? provenance
- Which title changes preserve the Classic's identity, and what evidence supports continuity across them? boundary
Edition and programme boundaries
Separates the recurring Classic from each edition, competitive race and associated activity.
Constituent race membership
Treat the races and associated activities included in each edition as matters for documented programme evidence.
- Which competitive races and associated activities does the official programme include in each Classic edition? boundary
- When a race category is added or removed, how does the organiser describe its relationship to the continuing Classic? definition
Edition timing and status Tracks the intended and actual temporal extent of each Classic edition.
Calendar and race day
Records source-attributed programme dates and constituent race timing.
Dated edition extent
Distinguish wider programme dates, race-day schedules and actual competition timestamps.
- What dates delimit the Classic edition's full programme, and which dates belong specifically to its competitive races? measurement
- Which calendar, time zone and timing precision apply to published starts, finishes and road-access windows? definition
Changes and occurrence
Preserves status changes, evidence of occurrence and attributed explanations.
Edition status evidence
Record announcements and subsequent outcomes without inferring completion from an old calendar listing.
- Which dated notices establish whether the edition was scheduled, postponed, cancelled or completed? provenance
- Where sources disagree about an edition's status or reasons for a change, who makes each claim and which authority can resolve it? provenance
- Which planning or attendance actions must be revised after a confirmed status change? action
Race programme and results Defines the Classic's documented competitive offerings and the evidence connecting entrants to outcomes.
Classification and entry
Identifies applicable competition categories, sanctioning and entry conditions.
Edition-specific competition conditions
Record each race's documented format and eligibility without carrying classifications forward automatically.
- What discipline, format, participant categories and sanctioning classification are documented for each race in this edition? definition
- What invitation, qualification, registration or licensing conditions govern rider and team entry? action
Starters and classification
Separates announced participation from actual starters and official outcomes.
Participation-to-result trace
Connect riders and teams to race-specific start lists, classifications and subsequent decisions.
- Which official records distinguish invited or announced teams and riders from those who actually started? provenance
- How are finish order, time gaps, non-finishes and exclusions represented in the official classification? measurement
- Which corrections or adjudications supersede an earlier published Classic result? provenance
Maryland course and road use Connects each Classic race to its documented course and the temporary use of Maryland roads.
Course version and distance
Identifies the route applicable to a specific edition and race.
Verified Classic course
Record start and finish locations, road sequence, any circuits and distance against a dated course source.
- Which Maryland locations and roads constitute the published course for this particular Classic race? boundary
- What distance, circuit arrangement and lap count does the authoritative route version specify? measurement
- Was the published course changed or shortened, and which record establishes the route actually raced? provenance
Closures and access
Relates the course to jurisdiction-specific traffic controls and public access notices.
Race road access conditions
Keep authorised closures, crossing conditions and reopening windows distinct from the course geometry.
- Which road authorities publish closures or traffic controls for the edition, and what locations and times do their notices cover? provenance
- Where and when may residents, spectators and service vehicles cross or enter the affected roads? action
Delivery and public participation Identifies who delivers the Classic and what official information supports practical involvement.
Responsibility and readiness
Connects edition delivery responsibilities to evidence of operational readiness.
Classic delivery authorities
Distinguish organiser, competition officials, road authorities and other documented operational roles.
- Who is responsible for organising the edition, directing competition and authorising its use of public roads? provenance
- What documented readiness conditions govern whether the race may start, continue, change course or stop? action
Spectating, volunteering and updates
Captures edition-specific public participation opportunities and communication channels.
Supported public actions
Ground spectator, volunteer and viewing actions in current official instructions for the relevant race or activity.
- Which official instructions govern spectator areas, accessibility, admission and volunteer registration for this edition? action
- Which channels provide authoritative race-day changes and any confirmed broadcast or streaming access? provenance
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these check these first hold for the sense of Maryland Cycling Classic this model covers, and on what evidence? provenance
Standards and regulation
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these standards and regulation hold for the sense of Maryland Cycling Classic this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these real-world use hold for the sense of Maryland Cycling Classic this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these failure modes and hazards hold for the sense of Maryland Cycling Classic this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of Maryland Cycling Classic this model covers, and on what evidence? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Activities and processes
- Entry kind
- thing
- Plane
- ACT
- Domain
- ACT.EVT
What it is Filled
The Maryland Cycling Classic is a professional one-day road cycling event in Maryland, United States, whose inaugural race took place in 2022 on a route through Baltimore County to a finish in Baltimore.
In scope
- Event identity, naming continuity and boundaries between the series, editions and constituent races
- Edition dates, local time conventions, lifecycle status and evidence of changes or cancellation
- Race categories, eligibility, competition format and official results
- Edition-specific routes, road access, race infrastructure and operational readiness
- Organiser responsibilities, participant roles and official public information
Out of scope
- General road cycling rules except their documented application to an edition
- Complete biographies, employment histories and season records of riders and teams
- Maryland geography and permanent road infrastructure beyond their event roles
- Internal governance of organising, sanctioning or sponsoring organisations
- Independent rides, festivals or other cycling events without a documented relationship to the Classic
Why it exists Filled
Enable an AI agent to recognise the Maryland Cycling Classic, distinguish its editions and constituent races, assess their documented status, and identify supported participation, operational and spectator actions.
Distinguishing features Filled
- An official organiser or sanctioning record identifies the event as the Maryland Cycling Classic; a Maryland location alone does not establish identity.
- A dated race or programme item can be linked to a particular Classic edition rather than treated as the entire recurring event.
- Race category, route and results belong to the same documented edition and constituent race; shared branding does not make those attributes interchangeable.
- A similarly branded community activity is distinguished from a competitive race through its programme designation, entry conditions and results arrangements.
What robots and AI may and may not do Filled
Must not
- Publish doping allegations without an official finding.
- Alter results without the organisers' or federation's decision.
- Encourage spectators to step into the road or follow the race in vehicles.
- Share riders' personal data beyond what they publish.
Only with a human decision
- Changing the course or safety arrangements of the race.
May
- Report race results, routes and dates from official organiser sources.
- Share road-closure and spectator information that the organisers publish.
Moral aspects Filled
- Closing roads affects Baltimore-area residents and businesses.
- Riders and spectators share public roads during the race.
Who is affected
- Riders
- Spectators
- Residents along the route
Owners Filled
Steward
The race organiser, under the national cycling federation.
Links to other meta-models Filled
parent
- Q74275170 - registry parent class
- Q74275176 - registry parent class
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.maryland-cycling-classic
- Wikidata: Q80580812 (https://www.wikidata.org/wiki/Q80580812)
Direct properties not applicable Not applicable
- Identity level: event series | edition | constituent race | associated programme activity
- Edition temporal extent: Source-attributed start and end dates or timestamps, with calendar, local time zone and precision
- Edition lifecycle: proposed | announced | scheduled | postponed | cancelled | underway | completed | unresolved
- Competition designation: Edition-specific discipline, race format, participant category and sanctioning classification as documented
- Route distance: km, linked to a constituent race, route version and planned or actual status
- Route configuration: Documented start, finish, road sequence, circuit sections and lap counts; unknown where unverified
- Responsible authority: Named organisation or official linked to an edition, responsibility and supporting source
- Participation confirmation: invited | entered | confirmed on start list | started | finished | withdrew | excluded | unresolved
Plane ACT: no invented physical properties.
Recognition optional Filled
- Official event signage identifies the race by its name and distinguishes it from other cycling events in Maryland.
- Edition dates on banners, accreditation or race materials distinguish one running from another.
- Baltimore location markings and matching official route information support identification, while cyclists and team clothing alone do not.
Capabilities and actions required Filled
- Resolve a Maryland Cycling Classic reference to the series, a particular edition or one constituent race.
- Compare documented editions to identify changes in programme, route, classification and delivery.
- Check whether a proposed rider, team, volunteer or spectator action meets the relevant edition's published conditions.
- Locate the responsible authority and latest applicable notice for schedule, access or route changes.
- Trace participation and results to official race records while preserving corrections and unresolved conflicts.
Hazards and failure modes required Filled
- Crashes in urban sections with road furniture.
- Spectator and vehicle incursions on the course.
Standards and interfaces required Filled
- UCI Cycling Regulations, Union Cycliste Internationale.
Context of use required Filled
- This event brings professional road cycling competition to Maryland through an organized one-day race.
- It is encountered in race calendars, results archives, sports coverage and local spectator information.
- Edition-specific information supports planning for attendance, race operations and road access.
Sources Filled
- Wikidata item Q80580812: Maryland Cycling Classic - identity and sense of the item
- Wikipedia: Maryland Cycling Classic - general description of the item
Open questions
- Which authoritative records establish the Classic's founding, first completed edition and continuity across any naming or organisational changes?
- Which editions were announced but did not take place, and what explanations are supported by attributable sources?
- How have constituent race categories, competition formats and sanctioning classifications changed across editions?
- Which archived route documents establish planned versus actually raced courses, including any last-minute alterations?
- Does an existing Vercy world model already cover this event, and should the registry entry link to it as the single source of truth?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q80580812/spec.json