{ "model": { "rank": 3663, "code": "thing-q105190", "model_id": "vr.tr.levee", "name": "levee", "purpose": "Enable an AI agent to recognise a levee, record its flood-containment role and condition, and identify inspection, maintenance or emergency decisions requiring qualified assessment.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q105190/", "tier": 2, "score": 83, "payload": { "layer": "wikidata", "aliases": [ "compartmentation dike", "fish pond dam", "sea wall", "Noma-dote", "Levees", "Pole dike", "sleeper dike", "Schardeich", "zeemuur", "Veenkades", "summer dike", "Flood embankment", "winter dike" ], "aliasCount": 13, "merged": 13, "knownIn": 83, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q105190", "url": "https://www.wikidata.org/wiki/Q105190", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T14:49:26Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 26.1, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a07c57-41f7-7621-b557-c5c0fff99323\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: levee\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 004: 1001 registere", "usd": 0, "recall": true }, "codex": { "seconds": 78.5, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a07c57-4204-7971-a04c-c3f4f813d842\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: levee\nRegistry id: vr.tr.levee\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext for " } } }, "metaModel": { "id": "THING-Q105190", "registryId": "vr.tr.levee", "name": "levee", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q105190/", "model": { "registry_id": "vr.tr.levee", "name": "levee", "purpose": "Enable an AI agent to recognise a levee, record its flood-containment role and condition, and identify inspection, maintenance or emergency decisions requiring qualified assessment.", "definition": "A levee is an elongated embankment, constructed or naturally deposited, alongside a river or other water body that limits the lateral spread of water onto adjacent land.", "scope_statement": "This model owns the physical identity, configuration, hydraulic role, condition and management of an engineered levee embankment or reach; naturally deposited levees remain a sense-boundary question pending registry clarification.", "in_scope": [ "Levee alignment, reach boundaries, crest, slopes, toes and foundation interfaces", "Relationship between the waterside, intended protected area and connected flood-defence features", "Embankment materials, seepage controls, drainage and penetrations", "Observed deterioration, loading conditions and potential breach pathways", "Inspection, maintenance, access and emergency responsibilities" ], "out_of_scope": [ "Natural riverbank deposits classified as natural levees", "Reservoir dams whose primary role is impounding stored water", "Standalone floodwalls, gates and pumping stations as independently modelled assets", "Catchment-wide rainfall, runoff and river-flow forecasting", "Detailed models of buildings, populations and economic losses within the protected area", "Flood insurance, land-use policy and emergency services as institutional systems" ], "distinguishing_features": [ "It is an engineered embankment intended to limit floodwater entry into an identified area; an elevated riverbank without that engineering role does not establish this sense of levee.", "Its flood-containment role depends on a continuous alignment and effective connections or terminations, rather than merely the height of an isolated mound.", "It separates a waterside from an intended protected side; its principal function is flood exclusion rather than reservoir storage.", "An embankment forms its principal barrier body; a standalone structural wall belongs to the neighbouring floodwall model.", "A road or railway embankment qualifies only where a flood-containment role is established, rather than inferred from its shape." ], "characteristics": [ { "name": "Asset extent and segmentation", "kind": "relation", "unit_or_values": "Mapped alignment, reach identifiers, endpoints and parent levee-system reference", "why_it_matters": "Defines which physical length an observation or decision concerns." }, { "name": "Flood-containment role", "kind": "category", "unit_or_values": "Riverine, coastal, other documented role, or unresolved", "why_it_matters": "Identifies the relevant loading context without assuming all levees face the same conditions." }, { "name": "Waterside and intended protected area", "kind": "relation", "unit_or_values": "Waterbody reference, side designation and mapped protected-area reference", "why_it_matters": "Makes the direction and intended consequence of containment explicit." }, { "name": "Crest elevation profile", "kind": "measurement", "unit_or_values": "Metres relative to a named vertical datum, by location and survey date", "why_it_matters": "Locates low points and supports comparison with water levels." }, { "name": "Cross-section geometry", "kind": "measurement", "unit_or_values": "Crest width and embankment height in metres; side slopes as horizontal-to-vertical ratios", "why_it_matters": "Describes the barrier geometry relevant to access, erosion and stability assessment." }, { "name": "Freeboard for a specified scenario", "kind": "measurement", "unit_or_values": "Metres between local crest elevation and a specified water-surface elevation, using a common datum", "why_it_matters": "Records a scenario-dependent margin without treating it as a guarantee of protection." }, { "name": "Embankment and foundation composition", "kind": "category", "unit_or_values": "Documented material zones and foundation strata; investigation method and confidence", "why_it_matters": "Supports interpretation of seepage, settlement and stability concerns." }, { "name": "Connected and crossing assets", "kind": "relation", "unit_or_values": "References to closures, floodwalls, culverts, pipes, drains, pumps and adjoining reaches", "why_it_matters": "Identifies interfaces that can determine whether the wider barrier functions." }, { "name": "Observed distress", "kind": "state", "unit_or_values": "Dated and located observations of cracking, settlement, erosion, slides, seepage, boils or burrows; uninspected where applicable", "why_it_matters": "Separates observed evidence from inferred failure mechanisms." }, { "name": "Management responsibility", "kind": "relation", "unit_or_values": "Owner, operator, inspection authority and emergency contact references, with reach-specific remit", "why_it_matters": "Establishes who can assess findings and authorise interventions." } ], "affordances": [ "Locate a levee reach and trace its connections to the surrounding flood-defence system.", "Compare surveyed crest levels with a documented water-level scenario to flag potential low points.", "Record and compare inspections of slopes, toes, crest, drainage and penetrations.", "Flag distress observations for qualified assessment using documented local escalation criteria.", "Identify maintenance needs and check access, asset interfaces and authorisation requirements.", "Retrieve applicable flood-response actions and responsible contacts for the affected reach." ] }, "sources": [], "structure": { "bundles": [ { "id": "levee-identity-and-continuity", "name": "Levee identity and continuity", "description": "Establishes the engineered levee sense, asset extent and continuity of the flood barrier.", "rationale": "A raised bank cannot be assessed as a levee without establishing its intended role and connections.", "layers": [ { "id": "engineered-role-and-extent", "name": "Engineered role and extent", "description": "Defines which embankment and flood-containment purpose the record represents.", "findings": [ { "id": "levee-sense-and-reach", "name": "Levee sense and reach", "description": "Records evidence of an engineered flood-containment role and distinguishes a reach from the complete system.", "questions": [ { "text": "What record establishes that this embankment serves as an engineered levee?", "kind": "provenance", "id": "levee-sense-and-reach-q01" }, { "text": "Where does the modelled reach begin and end, and which larger system contains it?", "kind": "boundary", "id": "levee-sense-and-reach-q02" } ] } ] }, { "id": "barrier-connections", "name": "Barrier connections", "description": "Captures terminations, transitions and interruptions along the containment alignment.", "findings": [ { "id": "tie-ins-and-openings", "name": "Tie-ins and openings", "description": "Identifies how the embankment joins high ground or other defences and where openings require separate closure assets.", "questions": [ { "text": "How does each endpoint connect to high ground, another levee reach or a structural defence?", "kind": "boundary", "id": "tie-ins-and-openings-q01" }, { "text": "Which crossings or openings interrupt containment, and what linked assets provide their closure?", "kind": "boundary", "id": "tie-ins-and-openings-q02" } ] } ] } ] }, { "id": "geometry-and-hydraulic-loading", "name": "Geometry and hydraulic loading", "description": "Relates the levee's surveyed shape to the flood conditions it is intended to withstand.", "rationale": "Levee height has limited meaning without a datum, location and specified hydraulic scenario.", "layers": [ { "id": "surveyed-barrier-profile", "name": "Surveyed barrier profile", "description": "Records crest levels, cross-sections and survey reliability.", "findings": [ { "id": "crest-and-section-evidence", "name": "Crest and section evidence", "description": "Establishes the measured barrier geometry, including local low points and changes over time.", "questions": [ { "text": "What are the crest elevations, crest widths and side slopes along the reach, with units and vertical datum?", "kind": "measurement", "id": "crest-and-section-evidence-q01" }, { "text": "When and how were these dimensions surveyed, and which portions remain unmeasured?", "kind": "provenance", "id": "crest-and-section-evidence-q02" } ] } ] }, { "id": "flood-scenarios-and-margins", "name": "Flood scenarios and margins", "description": "Associates water levels, durations and relevant wave or flow effects with explicit scenarios.", "findings": [ { "id": "scenario-specific-containment", "name": "Scenario-specific containment", "description": "Records the loading assumptions behind any claimed containment margin or overtopping assessment.", "questions": [ { "text": "Which documented scenario supplies the water-level profile, loading duration and relevant wave or current conditions?", "kind": "provenance", "id": "scenario-specific-containment-q01" }, { "text": "For that scenario, where is freeboard smallest and how are overtopping or overflow routes assessed?", "kind": "measurement", "id": "scenario-specific-containment-q02" } ] } ] } ] }, { "id": "embankment-foundation-and-seepage", "name": "Embankment, foundation and seepage", "description": "Describes the material barrier and the paths water can take through or beneath it.", "rationale": "Floodwater may compromise a levee through its body or foundation even while remaining below the crest.", "layers": [ { "id": "material-zones-and-foundation", "name": "Material zones and foundation", "description": "Captures construction history, material variability and subsurface evidence.", "findings": [ { "id": "ground-model-and-modifications", "name": "Ground model and modifications", "description": "Records known fill zones, foundation strata and alterations that affect interpretation of the embankment.", "questions": [ { "text": "What investigations or construction records establish the embankment zones and underlying strata?", "kind": "provenance", "id": "ground-model-and-modifications-q01" }, { "text": "Where are material boundaries, buried features or later enlargements uncertain?", "kind": "boundary", "id": "ground-model-and-modifications-q02" } ] } ] }, { "id": "seepage-controls-and-pathways", "name": "Seepage controls and pathways", "description": "Connects drainage and seepage-control features with penetrations and observed water movement.", "findings": [ { "id": "through-and-under-seepage", "name": "Through and under seepage", "description": "Maps known water pathways and control features without assuming that their presence proves effectiveness.", "questions": [ { "text": "Where are filters, drains, cutoffs, relief wells and pipe penetrations located, and which records describe their configuration?", "kind": "provenance", "id": "through-and-under-seepage-q01" }, { "text": "What seepage flows, pore pressures or sediment-bearing discharges have been observed, at which locations and water levels?", "kind": "measurement", "id": "through-and-under-seepage-q02" } ] } ] } ] }, { "id": "condition-and-failure-pathways", "name": "Condition and failure pathways", "description": "Organises evidence of deterioration and relates it to assessed loss-of-containment mechanisms.", "rationale": "Inspection observations need levee-specific interpretation while remaining distinct from engineering conclusions.", "layers": [ { "id": "surface-and-deformation-condition", "name": "Surface and deformation condition", "description": "Records changes to the crest, slopes, toes and protective cover.", "findings": [ { "id": "located-distress-and-change", "name": "Located distress and change", "description": "Captures erosion, settlement, cracking, sliding, burrows and cover damage with their observed extent and progression.", "questions": [ { "text": "Where are distress features located, how large are they, and how have they changed since the previous inspection?", "kind": "measurement", "id": "located-distress-and-change-q01" }, { "text": "Which surfaces were obscured, inaccessible or otherwise not inspected?", "kind": "boundary", "id": "located-distress-and-change-q02" } ] } ] }, { "id": "assessed-loss-of-containment", "name": "Assessed loss of containment", "description": "Links observations and loading scenarios to qualified assessments of potential failure.", "findings": [ { "id": "failure-mechanisms-and-escalation", "name": "Failure mechanisms and escalation", "description": "Records assessments of overtopping erosion, internal erosion, instability or interface failure, together with their uncertainty.", "questions": [ { "text": "Which potential failure mechanisms have been assessed for this reach, by whom and using what evidence?", "kind": "provenance", "id": "failure-mechanisms-and-escalation-q01" }, { "text": "Which observed changes meet documented criteria for urgent review or emergency escalation?", "kind": "action", "id": "failure-mechanisms-and-escalation-q02" } ] } ] } ] }, { "id": "stewardship-and-flood-response", "name": "Stewardship and flood response", "description": "Connects routine upkeep and flood-period actions to the responsible organisations and linked assets.", "rationale": "A levee's practical function depends on inspection, maintained access and coordinated action at its interfaces.", "layers": [ { "id": "inspection-and-maintenance", "name": "Inspection and maintenance", "description": "Records upkeep obligations and the controls governing physical intervention.", "findings": [ { "id": "reach-care-and-authority", "name": "Reach care and authority", "description": "Identifies responsibility for inspections and maintenance of the embankment, cover, drainage and access routes.", "questions": [ { "text": "Who owns, operates and inspects this reach, and which documented requirements govern those duties?", "kind": "provenance", "id": "reach-care-and-authority-q01" }, { "text": "What maintenance is due, and what permissions or engineering review are required before excavation, vegetation removal or crest loading?", "kind": "action", "id": "reach-care-and-authority-q02" } ] } ] }, { "id": "flood-period-dependencies", "name": "Flood-period dependencies", "description": "Records event-specific readiness and coordination with closures, drainage and emergency management.", "findings": [ { "id": "readiness-triggers-and-handoffs", "name": "Readiness, triggers and handoffs", "description": "Connects documented flood triggers to patrols, interface checks and responsible decision-makers.", "questions": [ { "text": "Which local triggers initiate patrols, closure checks, drainage checks or emergency notifications?", "kind": "action", "id": "readiness-triggers-and-handoffs-q01" }, { "text": "Which linked assets and access routes must be available, and who confirms their readiness during a flood?", "kind": "action", "id": "readiness-triggers-and-handoffs-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "The registry provides no sense; this description prioritizes flood-defense infrastructure while acknowledging the geomorphological sense.", "Dimensions and protection levels vary too widely to give a defensible generic typical range.", "Regulatory and manual references are recalled, not checked; verify their current versions and applicability. FEMA recognition does not guarantee protection against all floods." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of levee this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Natural levee", "Engineered earthen levee", "River levee", "Coastal levee", "Setback levee", "Ring levee" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of levee this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "USACE National Levee Database", "value_or_pattern": "Database-assigned levee system and segment identifiers", "note": "Identifies individual U.S. levee systems and their segments, not the generic concept." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of levee this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "FEMA, 44 CFR ยง 65.10: requirements for recognizing levee systems on National Flood Insurance Program maps.", "U.S. Army Corps of Engineers, EM 1110-2-1913, Design and Construction of Levees." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of levee this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Reduce river flooding of settlements, farmland and infrastructure.", "Limit coastal inundation from elevated sea levels and storm surge.", "Enclose low-lying areas as part of flood-management systems that may also require pumps and drainage structures.", "Set back flood defenses from a river to provide additional space for floodwater." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of levee this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Overtopping can erode an earthen levee and initiate a breach.", "Seepage through or beneath the embankment can cause internal erosion and piping.", "Slope instability or foundation failure can cause sliding and loss of crest elevation.", "Settlement, animal burrows, roots and deteriorated penetrations can weaken the embankment or create seepage paths.", "Breaching can cause rapid inundation; rainfall and drainage backflow can also flood the enclosed area without a breach." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of levee this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Levee is common U.S. terminology; dike or dyke and flood embankment are used in other regions, with overlapping meanings.", "Dutch dikes commonly form parts of integrated systems involving polders, sluices and pumping stations.", "Engineering criteria and legal recognition depend on jurisdiction, flood regime and the consequences of failure." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of levee this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "dam", "difference": "A dam typically crosses a watercourse to impound or control water; a levee typically borders a water body to restrict lateral inundation." }, { "name": "floodwall", "difference": "A floodwall provides a flood barrier principally through a structural wall rather than an earth embankment." }, { "name": "dike", "difference": "Often a synonym for levee in flood management; terminology alone does not reliably separate them." }, { "name": "seawall", "difference": "A seawall is generally a structural coastal defense against waves and erosion, whereas a coastal levee is an embankment primarily limiting inundation." }, { "name": "natural levee", "difference": "A natural levee forms through sediment deposition during overbank flooding rather than deliberate construction." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of levee this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.levee cover only engineered flood embankments, or does the registry also intend the geomorphological sense of a natural levee?", "Which existing Vercy world model, if any, already owns the levee concept or its broader flood-defence system?", "Which jurisdiction-specific definitions and issuing bodies govern levee classification, assessment, inspection and recognition of protection claims?", "Should mixed embankment-and-floodwall alignments be represented as one composite levee asset or as linked assets under a flood-defence system?", "What evidence and qualified review are required before condition observations can support a protection claim or an intervention decision?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "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 levee, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a levee, record its flood-containment role and condition, and identify inspection, maintenance or emergency decisions requiring qualified assessment.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: compartmentation dike, fish pond dam, sea wall, Noma-dote, Levees, Pole dike, sleeper dike, Schardeich, zeemuur, Veenkades, summer dike, Flood embankment.", "13 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 83 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 levee, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "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": [ "Recognised by form, by the arrangement of its controls, and by markings - a plate, a model number, a certification mark. Form alone rarely separates two models that do very different things." ], "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": [ "compartmentation dike", "fish pond dam", "sea wall", "Noma-dote", "Levees", "Pole dike", "sleeper dike", "Schardeich", "zeemuur", "Veenkades", "summer dike", "Flood embankment" ] } ], "standing": "Described in 83 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 13 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 levee from another, and a levee 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 levee, 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 levee, 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 levee 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 levee, 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 levee, 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 levee 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 levee 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 levee, 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 levee, 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 levee 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 levee from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a levee, 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 levee, 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 levee is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "form-and-composition", "name": "Form, composition and condition", "description": "What a levee is made of, what shape and size it takes, and what state it is in.", "rationale": "A physical thing can be measured, and a model that cannot record its measurements cannot support any decision that depends on them.", "layers": [ { "id": "form-and-dimensions", "name": "Form and dimensions", "description": "Shape, size, mass and the ranges these take across examples.", "findings": [ { "id": "measurable-dimensions", "name": "Measurable dimensions and their units", "description": "The quantities worth recording and the units they are recorded in.", "questions": [ { "id": "measurable-dimensions-q01", "text": "What identifies and describes the dimensions of a levee, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "measurable-dimensions-q02", "text": "Who or what asserted this about the dimensions of a levee, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "measurable-dimensions-q03", "text": "What may an agent decide or do once the dimensions of a levee is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "material-and-composition", "name": "Material and composition", "description": "Materials, parts and how they are put together.", "findings": [ { "id": "parts-and-materials", "name": "Parts and materials", "description": "What a levee is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a levee, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "parts-and-materials-q02", "text": "Who or what asserted this about the composition of a levee, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "parts-and-materials-q03", "text": "What may an agent decide or do once the composition of a levee is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "condition-and-integrity", "name": "Condition and integrity", "description": "Wear, damage, health and the difference between working and broken.", "findings": [ { "id": "condition-assessment", "name": "Condition, damage and health", "description": "How the condition of a levee is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a levee, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "condition-assessment-q02", "text": "Who or what asserted this about the condition of a levee, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "condition-assessment-q03", "text": "What may an agent decide or do once the condition of a levee is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "place-and-movement", "name": "Place and movement", "description": "Where a levee is, how it got there and where it may go (varies).", "rationale": "A thing that can move needs its position recorded with a time, or every later claim about it is about a place it has left.", "layers": [ { "id": "location-and-placement", "name": "Location and placement", "description": "Position, containment and the reference frame the position is given in.", "findings": [ { "id": "position-and-frame", "name": "Position, container and reference frame", "description": "Where a levee is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a levee, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "position-and-frame-q02", "text": "Who or what asserted this about the location of a levee, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "position-and-frame-q03", "text": "What may an agent decide or do once the location of a levee is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "movement-and-transfer", "name": "Movement and transfer", "description": "How a levee is carried, installed or relocated.", "findings": [ { "id": "movement-events", "name": "Movement events and constraints", "description": "What counts as a movement, what records it and what limits it.", "questions": [ { "id": "movement-events-q01", "text": "What identifies and describes the movement of a levee, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "movement-events-q02", "text": "Who or what asserted this about the movement of a levee, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "movement-events-q03", "text": "What may an agent decide or do once the movement of a levee 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 levee 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 levee between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a levee, 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 levee, 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 levee 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 levee, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a levee 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 levee, 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 levee, 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 levee is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "function-and-principle", "name": "Function and operating principle", "description": "What levee is for and how it achieves it.", "rationale": "Two devices with the same name can work on different principles, and the principle is what predicts failure and constrains use.", "layers": [ { "id": "intended-function", "name": "Intended function", "description": "The job it does, and the jobs it is used for anyway.", "findings": [ { "id": "function-record", "name": "Function, principle and variants", "description": "What it does, how, and which variants do it differently.", "questions": [ { "id": "function-record-q01", "text": "What function does levee perform, on what operating principle, and which variants differ in that principle?", "kind": "definition" }, { "id": "function-record-q02", "text": "What use falls outside the intended function but happens in practice?", "kind": "boundary" } ] } ] }, { "id": "capacity-and-rating", "name": "Capacity and rating", "description": "The numbers that say what it can do and where it stops.", "findings": [ { "id": "ratings", "name": "Ratings and their conditions", "description": "Rated capacity, power, throughput and the conditions each assumes.", "questions": [ { "id": "ratings-q01", "text": "What ratings characterise levee, in what units, and under what stated conditions?", "kind": "measurement" }, { "id": "ratings-q02", "text": "What happens beyond the rating - degradation, refusal, damage - and how is that detected?", "kind": "action" } ] } ] } ] }, { "id": "operation-and-state", "name": "Operation, controls and state", "description": "How levee is operated and what state it is in right now.", "rationale": "An agent acting on a device needs its current state and the controls that change it, not just its specification.", "layers": [ { "id": "controls-and-modes", "name": "Controls and modes", "description": "What can be set, what that changes, and what is interlocked.", "findings": [ { "id": "control-surface", "name": "Control surface and interlocks", "description": "The settings available and the conditions that block them.", "questions": [ { "id": "control-surface-q01", "text": "What controls and modes does levee have, and what does each change?", "kind": "definition" }, { "id": "control-surface-q02", "text": "Which actions are interlocked or forbidden in which state, and what must be true before acting?", "kind": "action" } ] } ] }, { "id": "condition-and-maintenance", "name": "Condition and maintenance", "description": "Wear, service intervals, consumables and the line between working and broken.", "findings": [ { "id": "service-record", "name": "Condition, service and consumables", "description": "What is consumed, what is serviced, and how condition is judged.", "questions": [ { "id": "service-record-q01", "text": "What consumables and service does levee need, at what interval, and on whose authority?", "kind": "measurement" }, { "id": "service-record-q02", "text": "What evidence separates a unit that is working from one that is out of service?", "kind": "boundary" } ] } ] } ] }, { "id": "kind-model-unit", "name": "Kind, model and unit", "description": "Whether a claim about levee is about the kind, a product line, or one physical unit.", "rationale": "This is the boundary most often got wrong for made things, and getting it wrong mixes a catalogue entry with the machine in the yard.", "layers": [ { "id": "level-of-reference", "name": "Level of reference", "description": "The three levels and what belongs at each.", "findings": [ { "id": "level-rules", "name": "What belongs to kind, model and unit", "description": "Which properties are shared by all of them and which are not.", "questions": [ { "id": "level-rules-q01", "text": "Which facts about levee hold for every one of them, which for a model, and which only for one unit?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifies an individual unit, and what should an agent do when it has only the kind?", "kind": "action" } ] } ] }, { "id": "standards-and-conformity", "name": "Standards and conformity", "description": "The standards a working example must meet and who attests it.", "findings": [ { "id": "conformity", "name": "Standards, marks and attestation", "description": "Which standard applies, who certifies, and what the mark means.", "questions": [ { "id": "conformity-q01", "text": "Which standards govern levee, issued by whom, and what does conformity actually assert?", "kind": "provenance" }, { "id": "conformity-q02", "text": "What may an agent conclude from a certification mark, and what may it not?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a levee 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 levee and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a levee, 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 levee, 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 levee 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 levee is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a levee, 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 levee, 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 levee is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 8, "layers": 17, "findings": 19, "questions": 51 } } } }