{ "model": { "rank": 978, "code": "thing-q12132", "model_id": "vr.tr.calendar-system", "name": "calendar system", "purpose": "Let an agent handle calendar systems by type, epoch, rules, conversion and use.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.KNW", "industry": "", "version": "", "url": "/models/thing/q12132/", "tier": 2, "score": 208, "payload": { "layer": "wikidata", "aliases": [ "Lukashian calendar", "winter count", "consularia", "Schreibkalender", "traditional calendar in Vietnam", "Julian calendar", "religious calendar", "biodynamic calendar", "old calendar", "Directorium", "Discordian calendar", "fasti", "new calendar", "folk calendar", "celestial calendar", "fiscal calendar", "academic calendar", "Lukashian calendar for Earth", "legislative calendar", "Telugu calendar", "13 month calendar", "12 month calendar", "calendar round", "unspecified calendar", "lunar calendar", "Masonic calendar", "solar calendar", "Thai calendar", "Zoroastrian calendar", "Name days in France", "Pregnancy Calendar", "Lenten calendar", "traditional calendar in China", "Germanic calendar", "Inca calendar", "civil calendar", "liturgical year", "decimal calendar", "Celtic calendar", "official calendar" ], "aliasCount": 96, "merged": 96, "knownIn": 208, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q12132", "url": "https://www.wikidata.org/wiki/Q12132", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-11T07:52:46Z", "providers": [ "Claude" ], "breadth": "written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify", "pass": 2, "wave": 1, "engine": "claude" }, "metaModel": { "id": "THING-Q12132", "registryId": "vr.tr.calendar-system", "name": "calendar system", "version": "0.2.0-wave.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.KNW" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q12132/", "model": { "registry_id": "vr.tr.calendar-system", "name": "calendar system", "purpose": "Let an agent handle calendar systems by type, epoch, rules, conversion and use.", "definition": "A system for organising days into periods such as weeks, months and years, based on solar, lunar or lunisolar cycles, such as the Gregorian, Julian, Islamic, Hebrew, Chinese and traditional calendars.", "what_it_is_for": "Scheduling, recording dates and religious and civil observances.", "affordances": [ "convert dates between calendars", "compute holidays", "understand leap rules", "read historical dates correctly" ], "distinguishing_features": [ "Organises days into cycles", "Solar, lunar or lunisolar", "Has an epoch and leap rules", "Many in parallel use" ], "appearance": "Tables, almanacs and date notations.", "visual_identification": [ "Calendar names and eras", "Month names and lengths", "Record-keeping forms such as winter counts" ], "physical_properties": [], "families_and_kinds": [ "solar calendars such as Gregorian", "lunar calendars such as Islamic", "lunisolar calendars such as Hebrew and Chinese", "historical calendars such as Julian", "traditional record systems such as winter counts" ], "related_models": [ { "relation": "is a kind of", "target": "chronology and conceptual system", "why": "category" }, { "relation": "defines", "target": "leap year and month", "why": "units" }, { "relation": "is represented in", "target": "ISO 8601", "why": "standard" }, { "relation": "is used for", "target": "holiday computation", "why": "application" } ], "identifiers": [], "standards_and_regulation": [ "ISO 8601 (Gregorian)", "Unicode CLDR calendar data", "National laws on official calendars" ], "failure_modes_and_hazards": [ "Conversion errors", "Confusing Julian and Gregorian dates", "Lunar calendars depending on sighting" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "system", "name": "System", "description": "Which calendar.", "rationale": "Type and rules.", "layers": [ { "id": "type", "name": "Type", "description": "Solar, lunar.", "findings": [ { "id": "type-finding", "name": "Type", "description": "Calendar type.", "questions": [ { "text": "Which calendar is used, and what kind is it?", "kind": "definition" }, { "text": "What is its epoch?", "kind": "provenance" } ] } ] }, { "id": "rules", "name": "Rules", "description": "Months and leaps.", "findings": [ { "id": "rules-finding", "name": "Rules", "description": "Rules.", "questions": [ { "text": "How are months and leap periods determined?", "kind": "definition" }, { "text": "Are months fixed or based on sightings?", "kind": "boundary" } ] } ] } ] }, { "id": "conversion", "name": "Conversion", "description": "Between calendars.", "rationale": "Conversion needs care.", "layers": [ { "id": "convert", "name": "Convert", "description": "Algorithm.", "findings": [ { "id": "convert-finding", "name": "Convert", "description": "Conversion.", "questions": [ { "text": "What is this date in another calendar?", "kind": "measurement" }, { "text": "Which algorithm or authority?", "kind": "provenance" } ] } ] }, { "id": "historical", "name": "Historical", "description": "Old dates.", "findings": [ { "id": "historical-finding", "name": "Historical", "description": "Historical dates.", "questions": [ { "text": "Was the date recorded in the Julian or another calendar?", "kind": "boundary" }, { "text": "When did the region switch?", "kind": "provenance" } ] } ] } ] }, { "id": "observances", "name": "Observances", "description": "Holidays.", "rationale": "Calendars define holidays.", "layers": [ { "id": "holidays", "name": "Holidays", "description": "Dates.", "findings": [ { "id": "holidays-finding", "name": "Holidays", "description": "Holiday dates.", "questions": [ { "text": "When does this holiday fall this year?", "kind": "measurement" }, { "text": "According to which authority?", "kind": "provenance" } ] } ] }, { "id": "variation", "name": "Variation", "description": "Local differences.", "findings": [ { "id": "variation-finding", "name": "Variation", "description": "Local variation.", "questions": [ { "text": "Does the date vary by region or community?", "kind": "boundary" }, { "text": "Why?", "kind": "definition" } ] } ] } ] }, { "id": "software", "name": "Software", "description": "Implementation.", "rationale": "Software must support calendars.", "layers": [ { "id": "libraries", "name": "Libraries", "description": "Support.", "findings": [ { "id": "libraries-finding", "name": "Libraries", "description": "Library support.", "questions": [ { "text": "Which libraries support this calendar?", "kind": "provenance" }, { "text": "Is CLDR data used?", "kind": "provenance" } ] } ] }, { "id": "display", "name": "Display", "description": "Localisation.", "findings": [ { "id": "display-finding", "name": "Display", "description": "Localisation.", "questions": [ { "text": "How should dates be displayed for this locale?", "kind": "action" }, { "text": "Is the calendar shown explicitly?", "kind": "boundary" } ] } ] } ] } ] }, "openQuestions": [ "Should each calendar be a separate entry?", "How should conversion algorithms be linked?", "How should sighting-based months be handled?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "discipline or field of knowledge", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a calendar system, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent handle calendar systems by type, epoch, rules, conversion and use.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Lukashian calendar, winter count, consularia, Schreibkalender, traditional calendar in Vietnam, Julian calendar, religious calendar, biodynamic calendar, old calendar, Directorium, Discordian calendar, fasti.", "96 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 208 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a calendar system, and on what evidence are they told apart?" ], "whatItIsMadeOf": "content that has to be carried by something else", "physicalCharacter": [ "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "read it and act on what it says" ], "howItIsRecognised": [], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "Lukashian calendar", "winter count", "consularia", "Schreibkalender", "traditional calendar in Vietnam", "Julian calendar", "religious calendar", "biodynamic calendar", "old calendar", "Directorium", "Discordian calendar", "fasti" ] } ], "standing": "Described in 208 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 96 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one calendar system from another, and a calendar system from things that resemble it.", "rationale": "Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.", "layers": [ { "id": "naming-and-identifiers", "name": "Names and identifiers", "description": "The names this thing goes by and the identifiers that survive translation and time.", "findings": [ { "id": "preferred-name-and-aliases", "name": "Preferred name, aliases and local names", "description": "Which name to use, which names mean the same thing, and which merely sound similar.", "questions": [ { "id": "preferred-name-and-aliases-q01", "text": "What identifies and describes the name of a calendar system, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "preferred-name-and-aliases-q02", "text": "Who or what asserted this about the name of a calendar system, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "preferred-name-and-aliases-q03", "text": "What may an agent decide or do once the name of a calendar system is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "stable-identifiers", "name": "Stable identifiers and external keys", "description": "Identifiers that keep pointing at this kind of thing across systems and languages.", "questions": [ { "id": "stable-identifiers-q01", "text": "What identifies and describes an identifier for a calendar system, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stable-identifiers-q02", "text": "Who or what asserted this about an identifier for a calendar system, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stable-identifiers-q03", "text": "What may an agent decide or do once an identifier for a calendar system is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "classification-and-granularity", "name": "Classification and granularity", "description": "Where a calendar system sits among kinds, and how finely a task needs to cut it.", "findings": [ { "id": "kind-and-parents", "name": "Kind, parents and neighbouring kinds", "description": "The classes this thing belongs to and the ones it is next to.", "questions": [ { "id": "kind-and-parents-q01", "text": "What identifies and describes the kind of a calendar system, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "kind-and-parents-q02", "text": "Who or what asserted this about the kind of a calendar system, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "kind-and-parents-q03", "text": "What may an agent decide or do once the kind of a calendar system is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "distinguishing-features", "name": "Distinguishing features", "description": "What separates a calendar system from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a calendar system, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "distinguishing-features-q02", "text": "Who or what asserted this about what distinguishes a calendar system, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "distinguishing-features-q03", "text": "What may an agent decide or do once what distinguishes a calendar system is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "state-and-lifecycle", "name": "State and lifecycle", "description": "The states a calendar system passes through and the events that move it between them.", "rationale": "Most decisions about a thing depend on what state it is in now, which is a claim with a time on it, not a property.", "layers": [ { "id": "lifecycle-stages", "name": "Lifecycle stages", "description": "From coming into existence to ceasing to be one of these.", "findings": [ { "id": "stages-and-transitions", "name": "Stages and transitions", "description": "The stages worth naming and what moves a calendar system between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a calendar system, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stages-and-transitions-q02", "text": "Who or what asserted this about the lifecycle of a calendar system, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stages-and-transitions-q03", "text": "What may an agent decide or do once the lifecycle of a calendar system is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "observations-and-status", "name": "Observations and current status", "description": "What is observed about a calendar system, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a calendar system is recorded so that it can be superseded rather than overwritten.", "questions": [ { "id": "observation-record-q01", "text": "What identifies and describes an observation of a calendar system, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "observation-record-q02", "text": "Who or what asserted this about an observation of a calendar system, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "observation-record-q03", "text": "What may an agent decide or do once an observation of a calendar system is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "content-and-access", "name": "Content, encoding and access", "description": "What a calendar system says, how it is encoded and who may read it.", "rationale": "An informational thing carries content that can be copied, versioned and withheld, none of which its physical carrier explains.", "layers": [ { "id": "content-and-encoding", "name": "Content and encoding", "description": "The content itself, its format and its language.", "findings": [ { "id": "content-and-format", "name": "Content, format and language", "description": "What a calendar system contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a calendar system, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "content-and-format-q02", "text": "Who or what asserted this about the content of a calendar system, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "content-and-format-q03", "text": "What may an agent decide or do once the content of a calendar system is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "access-and-rights", "name": "Access, rights and retention", "description": "Who may read, copy or change it, and for how long it is kept.", "findings": [ { "id": "access-rules", "name": "Access rules and retention", "description": "The permissions attached to a calendar system and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a calendar system, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "access-rules-q02", "text": "Who or what asserted this about access to a calendar system, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "access-rules-q03", "text": "What may an agent decide or do once access to a calendar system is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "subject-and-method", "name": "Subject matter and method", "description": "What calendar system studies and how it establishes anything.", "rationale": "A field is identified by its questions and its methods, and those are what distinguish it from the fields next to it.", "layers": [ { "id": "subject", "name": "Subject matter", "description": "The questions it takes as its own.", "findings": [ { "id": "subject-record", "name": "Questions and objects of study", "description": "What it is about, stated so a neighbouring field can be told apart.", "questions": [ { "id": "subject-record-q01", "text": "What questions and objects does calendar system take as its own?", "kind": "definition" }, { "id": "subject-record-q02", "text": "Which questions does it share with a neighbouring field, and who claims them?", "kind": "boundary" } ] } ] }, { "id": "method", "name": "Method and evidence", "description": "How claims are established and what counts as evidence.", "findings": [ { "id": "method-record", "name": "Methods and standards of evidence", "description": "The methods used and what they are taken to establish.", "questions": [ { "id": "method-record-q01", "text": "By what methods does calendar system establish claims, and what counts as sufficient evidence?", "kind": "provenance" }, { "id": "method-record-q02", "text": "What kind of claim can this field not settle, and where should an agent look instead?", "kind": "action" } ] } ] } ] }, { "id": "institutions-and-classification", "name": "Institutions and classification", "description": "Where calendar system is practised and how catalogues place it.", "rationale": "The institutional footprint is the evidence that a field exists as a field rather than as a topic.", "layers": [ { "id": "institutions", "name": "Institutional markers", "description": "Societies, journals, degrees and departments.", "findings": [ { "id": "institution-record", "name": "Bodies and venues", "description": "Where the field organises itself.", "questions": [ { "id": "institution-record-q01", "text": "Which societies, journals or degrees mark calendar system as an established field?", "kind": "provenance" }, { "id": "institution-record-q02", "text": "What would show that it is emerging or dissolving rather than established?", "kind": "boundary" } ] } ] }, { "id": "classification", "name": "Classification schemes", "description": "Where library and research classifications put it.", "findings": [ { "id": "classification-record", "name": "Codes and their disagreements", "description": "The classification codes that place it, and where they differ.", "questions": [ { "id": "classification-record-q01", "text": "Which classification schemes place calendar system, under what codes?", "kind": "definition" }, { "id": "classification-record-q02", "text": "Where do those schemes disagree about its scope?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a calendar system came from and when it held.", "rationale": "A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.", "layers": [ { "id": "source-and-authority", "name": "Source and authority", "description": "Who said it, on what evidence, and how strongly.", "findings": [ { "id": "claim-provenance", "name": "Claim provenance and confidence", "description": "The authority behind each claim about a calendar system and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a calendar system, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "claim-provenance-q02", "text": "Who or what asserted this about a claim about a calendar system, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "claim-provenance-q03", "text": "What may an agent decide or do once a claim about a calendar system is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "time-and-versions", "name": "Time, versions and supersession", "description": "When a claim was true, when it was learnt, and what replaced it.", "findings": [ { "id": "validity-and-supersession", "name": "Validity period and supersession", "description": "How an old claim about a calendar system is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a calendar system, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "validity-and-supersession-q02", "text": "Who or what asserted this about the validity of a claim about a calendar system, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "validity-and-supersession-q03", "text": "What may an agent decide or do once the validity of a claim about a calendar system is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 12, "findings": 14, "questions": 38 } } } }