{ "model": { "rank": 508, "code": "thing-q12271", "model_id": "vr.tr.architecture", "name": "architecture", "purpose": "Let an agent handle architecture as a discipline, profession and body of works, with styles, practitioners, regulation and heritage.", "family": "Thing Registry", "category": "Activities and processes", "status": "research-draft", "kind": "thing", "plane": "ACT", "domain": "ACT.ACT", "industry": "", "version": "", "url": "/models/thing/q12271/", "tier": 2, "score": 251, "payload": { "layer": "wikidata", "aliases": [ "lavatorium", "minka", "Kabuto-zukuri", "Tamugimata multilayered house", "gyoka", "gasshō-zukuri", "building services engineering", "Building Services Technology", "anti-rollback device", "Residential frame engineering", "rock-cut architecture", "rock-cut architecture in India", "funerary architecture", "Kibitsu-zukuri", "hyper-density structure", "visionary architecture", "open-source architecture", "transport civil engineering", "naval architecture", "Carpenter's Joy", "Māori architecture", "naval architecture and marine engineering", "Bionic architecture", "architectural heritage and conservation", "architectural computer science", "architectural geometry", "upstream-downstream axis", "neo-Mudéjar", "architecture of the Earth", "prehistoric architecture", "Islamic architecture", "sacred architecture", "colonial architecture", "Dutch colonial architecture", "Moroccan architecture", "colonial architecture of Latin America", "International Gothic art in Europe", "Indo-Islamic architecture", "Islamic architecture of North Macedonia", "Religious Islamic architecture" ], "aliasCount": 361, "merged": 362, "knownIn": 251, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.architecture-act", "source": { "dataset": "wikidata", "item": "Q12271", "url": "https://www.wikidata.org/wiki/Q12271", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-11T05:07:43Z", "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-Q12271", "registryId": "vr.tr.architecture", "name": "architecture", "version": "0.2.0-wave.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q12271/", "model": { "registry_id": "vr.tr.architecture", "name": "architecture", "purpose": "Let an agent handle architecture as a discipline, profession and body of works, with styles, practitioners, regulation and heritage.", "definition": "The art and practice of designing buildings and other structures, and the built results considered as works of design, including vernacular traditions and styles.", "what_it_is_for": "Shaping built environments for use, safety, meaning and beauty.", "affordances": [ "design buildings and spaces", "practise it, as a registered architect where required", "study and teach it", "protect it, as heritage" ], "distinguishing_features": [ "A discipline and profession as well as its products", "Protected title in many countries", "Includes vernacular building without architects", "Building services engineering is a related discipline" ], "appearance": "Buildings and spaces; drawings, models and plans; styles visible in form, materials and ornament.", "visual_identification": [ "Style features such as roof forms, proportions and ornament", "Vernacular types such as minka or gassho-zukuri farmhouses", "Architects credits on drawings and plaques" ], "physical_properties": [], "families_and_kinds": [ "by style: classical, gothic, modernist and many more", "vernacular architecture", "landscape and interior architecture", "sustainable and passive design" ], "related_models": [ { "relation": "produces", "target": "building", "why": "buildings as works" }, { "relation": "is practised by", "target": "architect", "why": "profession" }, { "relation": "is regulated by", "target": "building and planning law", "why": "rules" }, { "relation": "is confused with", "target": "software architecture", "why": "a metaphorical use" } ], "identifiers": [], "standards_and_regulation": [ "Architects registration law, such as the EU Professional Qualifications Directive", "Building codes and planning law", "UNESCO World Heritage Convention" ], "failure_modes_and_hazards": [ "Unsafe designs", "Loss of heritage", "Inaccessible design" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "style-and-type", "name": "Style and type", "description": "What kind of architecture.", "rationale": "Style and type place a work.", "layers": [ { "id": "style", "name": "Style", "description": "Period and movement.", "findings": [ { "id": "style-finding", "name": "Style", "description": "The style.", "questions": [ { "text": "Which style or movement does this work belong to?", "kind": "definition" }, { "text": "Which features show it?", "kind": "definition" } ] } ] }, { "id": "typology", "name": "Typology", "description": "Building type.", "findings": [ { "id": "typology-finding", "name": "Typology", "description": "The building type.", "questions": [ { "text": "What building type is it?", "kind": "definition" }, { "text": "Is it a vernacular type?", "kind": "definition" } ] } ] } ] }, { "id": "practice", "name": "Practice", "description": "Architects and design.", "rationale": "Practice is regulated and credited.", "layers": [ { "id": "architect", "name": "Architect", "description": "Designer and firm.", "findings": [ { "id": "architect-finding", "name": "Credit", "description": "Who designed it.", "questions": [ { "text": "Who designed it, and when?", "kind": "provenance" }, { "text": "Is the architect registered?", "kind": "provenance" } ] } ] }, { "id": "process", "name": "Design process", "description": "Brief to completion.", "findings": [ { "id": "process-finding", "name": "Process", "description": "Stages of design.", "questions": [ { "text": "What were the brief and design stages?", "kind": "definition" }, { "text": "Which approvals were needed?", "kind": "boundary" } ] } ] } ] }, { "id": "performance", "name": "Performance", "description": "How well it works.", "rationale": "Architecture is judged by use as well as form.", "layers": [ { "id": "function", "name": "Function", "description": "Use and accessibility.", "findings": [ { "id": "function-finding", "name": "Function", "description": "How it serves users.", "questions": [ { "text": "How well does it serve its users, including disabled people?", "kind": "measurement" }, { "text": "What post-occupancy evaluation exists?", "kind": "provenance" } ] } ] }, { "id": "sustainability", "name": "Sustainability", "description": "Energy and materials.", "findings": [ { "id": "sustainability-finding", "name": "Sustainability", "description": "Environmental performance.", "questions": [ { "text": "What are its energy and carbon performance?", "kind": "measurement" }, { "text": "Which certifications does it have?", "kind": "provenance" } ] } ] } ] }, { "id": "heritage", "name": "Heritage", "description": "Protection of works.", "rationale": "Significant architecture is protected.", "layers": [ { "id": "status", "name": "Status", "description": "Listing.", "findings": [ { "id": "status-finding", "name": "Heritage status", "description": "Protection status.", "questions": [ { "text": "Is this work protected, at which level?", "kind": "provenance" }, { "text": "What changes need consent?", "kind": "boundary" } ] } ] }, { "id": "conservation", "name": "Conservation", "description": "Repair and change.", "findings": [ { "id": "conservation-finding", "name": "Conservation", "description": "Conservation approach.", "questions": [ { "text": "How should it be repaired?", "kind": "action" }, { "text": "Which charters guide conservation?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Should styles be separate entries?", "How should vernacular types be linked to regions?", "How should architects and works be linked?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "abstract concept", "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 architecture, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent handle architecture as a discipline, profession and body of works, with styles, practitioners, regulation and heritage.", "characteristics": { "substance": "activity", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: lavatorium, minka, Kabuto-zukuri, Tamugimata multilayered house, gyoka, gasshō-zukuri, building services engineering, Building Services Technology, anti-rollback device, Residential frame engineering, rock-cut architecture, rock-cut architecture in India.", "362 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 251 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 architecture, and on what evidence are they told apart?" ], "whatItIsMadeOf": "something that happens over time", "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": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Nothing to see. What is recognised is an instance of it, and which instances count is exactly what is argued about." ], "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": [ "lavatorium", "minka", "Kabuto-zukuri", "Tamugimata multilayered house", "gyoka", "gasshō-zukuri", "building services engineering", "Building Services Technology", "anti-rollback device", "Residential frame engineering", "rock-cut architecture", "rock-cut architecture in India" ] } ], "standing": "Described in 251 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 362 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 architecture from another, and a architecture 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 architecture, 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 architecture, 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 architecture 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 architecture, 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 architecture, 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 architecture 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 architecture 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 architecture, 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 architecture, 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 architecture 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 architecture from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a architecture, 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 architecture, 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 architecture 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 architecture 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 architecture between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a architecture, 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 architecture, 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 architecture 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 architecture, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a architecture 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 architecture, 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 architecture, 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 architecture is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "process-and-outcome", "name": "Process, inputs and outcome", "description": "How a architecture proceeds, what it needs and what it leaves behind.", "rationale": "An activity is known by its steps and its results, and both have to be recordable while it is still running.", "layers": [ { "id": "steps-and-sequence", "name": "Steps and sequence", "description": "The steps of a architecture, their order and what may run in parallel.", "findings": [ { "id": "steps-and-preconditions", "name": "Steps, preconditions and completion", "description": "What has to be true before each step of a architecture and what marks it done.", "questions": [ { "id": "steps-and-preconditions-q01", "text": "What identifies and describes a step of a architecture, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "steps-and-preconditions-q02", "text": "Who or what asserted this about a step of a architecture, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "steps-and-preconditions-q03", "text": "What may an agent decide or do once a step of a architecture is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "inputs-and-results", "name": "Inputs, resources and results", "description": "What a architecture consumes and what it produces.", "findings": [ { "id": "inputs-and-outputs", "name": "Inputs, outputs and side effects", "description": "The resources a architecture takes and the results it leaves, wanted or not.", "questions": [ { "id": "inputs-and-outputs-q01", "text": "What identifies and describes the inputs and results of a architecture, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "inputs-and-outputs-q02", "text": "Who or what asserted this about the inputs and results of a architecture, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "inputs-and-outputs-q03", "text": "What may an agent decide or do once the inputs and results of a architecture is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "definitions-in-contest", "name": "Definitions and who holds them", "description": "What architecture is taken to mean, and by whom.", "rationale": "When a field disagrees about a concept, the disagreement is the content. A model that picks one definition silently destroys the information.", "layers": [ { "id": "competing-definitions", "name": "Competing definitions", "description": "The main readings and the traditions behind them.", "findings": [ { "id": "definition-map", "name": "Definitions and their holders", "description": "Each definition with the school or body that holds it.", "questions": [ { "id": "definition-map-q01", "text": "Which definitions of architecture are in use, and which tradition or body holds each?", "kind": "definition" }, { "id": "definition-map-q02", "text": "What turns on the difference between them in practice?", "kind": "boundary" } ] } ] }, { "id": "operationalisation", "name": "Operationalisation", "description": "How it is measured or applied when it has to be.", "findings": [ { "id": "operational-record", "name": "Measures and proxies", "description": "Instruments and indicators used to stand in for it.", "questions": [ { "id": "operational-record-q01", "text": "How is architecture operationalised or measured in practice, and by what instrument?", "kind": "measurement" }, { "id": "operational-record-q02", "text": "What does that operationalisation leave out, and when does that matter?", "kind": "boundary" } ] } ] } ] }, { "id": "instances-and-use", "name": "Instances, use and consequence", "description": "What counts as an instance of architecture and what follows from calling something that.", "rationale": "Applying a concept is an act with consequences, so a model must say what the label licenses and what it does not.", "layers": [ { "id": "instances", "name": "What counts as an instance", "description": "Clear cases, borderline cases and non-cases.", "findings": [ { "id": "instance-tests", "name": "Tests for an instance", "description": "What would settle whether something falls under it.", "questions": [ { "id": "instance-tests-q01", "text": "What would settle whether something is an instance of architecture?", "kind": "boundary" }, { "id": "instance-tests-q02", "text": "Which borderline cases are argued about, and on what grounds?", "kind": "definition" } ] } ] }, { "id": "consequence", "name": "Consequence of application", "description": "Rights, duties or decisions that follow from the label.", "findings": [ { "id": "consequence-record", "name": "What the label licenses", "description": "What an agent may do once something is classified this way.", "questions": [ { "id": "consequence-record-q01", "text": "What follows practically once something is treated as architecture?", "kind": "action" }, { "id": "consequence-record-q02", "text": "What must an agent not infer from the label alone?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a architecture 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 architecture and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a architecture, 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 architecture, 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 architecture 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 architecture is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a architecture, 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 architecture, 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 architecture 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 } } } }