{ "model": { "rank": 3767, "code": "thing-q191733", "model_id": "vr.tr.pulse", "name": "pulse", "purpose": "Enable an agent to recognise a pulse as a bounded temporal excursion, assess how reliably it has been identified and measured, and decide whether to detect, compare, isolate or modify it.", "family": "Thing Registry", "category": "Cross-cutting context", "status": "research-draft", "kind": "thing", "plane": "XCT", "domain": "XCT.QLT", "industry": "", "version": "", "url": "/models/thing/q191733/", "tier": 2, "score": 82, "payload": { "layer": "wikidata", "aliases": [ "Pulse wave velocity", "anacrotic pulse" ], "aliasCount": 2, "merged": 2, "knownIn": 82, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.pulse-food", "source": { "dataset": "wikidata", "item": "Q191733", "url": "https://www.wikidata.org/wiki/Q191733", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T15:06:18Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 25.9, "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: 01a07c66-d099-7492-a6a6-285be2cbeb1e\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: pulse\nSense to describe: (none recorded)\nDomain code: XCT.STA\nAlso known as: (none)\n\n\nContext for this batch of 801 things:\n# Batch 004: 1001 registered", "usd": 0, "recall": true }, "codex": { "seconds": 71, "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: 01a07c66-d090-7c23-af46-79ae50374250\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: pulse\nRegistry id: vr.tr.pulse\nPlane / domain: XCT / XCT.STA\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext for " } } }, "metaModel": { "id": "THING-Q191733", "registryId": "vr.tr.pulse", "name": "pulse", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "XCT.STA" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q191733/", "model": { "registry_id": "vr.tr.pulse", "name": "pulse", "purpose": "Enable an agent to recognise a pulse as a bounded temporal excursion, assess how reliably it has been identified and measured, and decide whether to detect, compare, isolate or modify it.", "definition": "In the signal and physical-process sense assumed here, a pulse is a temporally localized excursion of a quantity from a baseline, characterized by its amplitude, duration and waveform.", "scope_statement": "This model provisionally covers pulse as an abstract temporal pattern: a finite-duration excursion of a specified quantity from a stated baseline, including its waveform, boundaries and relationship to other pulses; the registry lacks a definition, so this interpretation requires confirmation.", "in_scope": [ "The quantity that exhibits the pulse and its reference baseline", "Criteria that distinguish a pulse from noise, a sustained change or an oscillation", "Pulse onset, termination, duration, amplitude and waveform", "Individual pulses and their membership in pulse sequences", "Observation limits and uncertainty in pulse identification", "Conditions for detecting, comparing, generating or modifying a pulse" ], "out_of_scope": [ "Complete models of the physical carriers, devices or media that produce pulses", "Cardiovascular physiology and clinical interpretation of an arterial pulse", "Musical pulse as an organising beat", "Edible seeds called pulses", "Continuous oscillation and sustained state changes except where needed to distinguish them from pulses", "Messages or commands encoded by pulses beyond the pulse-to-meaning relationship" ], "distinguishing_features": [ "A candidate has an identifiable onset and termination under an explicit boundary rule; an indefinitely maintained step does not qualify under this scope.", "A candidate departs from a specified baseline in a named quantity; a timestamped event alone does not establish a pulse waveform.", "An individual pulse can be isolated by an explicit segmentation rule; a continuous oscillation is not automatically a sequence of pulses.", "A pulse need not repeat; recurrence belongs to its relationship with other pulses.", "Calling a fluctuation a pulse requires a stated criterion for distinguishing it from background variation, including an unresolved classification when the evidence is insufficient." ], "characteristics": [ { "name": "Pulsed quantity", "kind": "category", "unit_or_values": "Named observable or modelled quantity with its applicable unit", "why_it_matters": "Identifies what changes and prevents comparisons between unrelated amplitudes." }, { "name": "Baseline reference", "kind": "relation", "unit_or_values": "Reference value or time-varying baseline estimate, with estimation interval and method", "why_it_matters": "Pulse amplitude and boundaries depend on the reference against which the excursion is recognised." }, { "name": "Temporal boundaries", "kind": "measurement", "unit_or_values": "Onset and termination in a declared time coordinate, with boundary rule and uncertainty", "why_it_matters": "Makes the pulse identifiable as a bounded occurrence." }, { "name": "Pulse width", "kind": "measurement", "unit_or_values": "Time units; specify threshold crossings, full width at half maximum or another declared convention", "why_it_matters": "Widths obtained using different conventions may describe different portions of the same waveform." }, { "name": "Amplitude and polarity", "kind": "measurement", "unit_or_values": "Signed deviation or positive and negative extrema in the pulsed quantity's unit, relative to baseline", "why_it_matters": "Distinguishes upward, downward and multiphasic excursions without assuming that every pulse has one positive peak." }, { "name": "Waveform form", "kind": "category", "unit_or_values": "Declared shape description, including number of phases, asymmetry and any ringing or secondary peaks", "why_it_matters": "Supports comparison and determines whether apparent subevents belong to one pulse." }, { "name": "Sequence membership", "kind": "relation", "unit_or_values": "Isolated pulse or linked sequence with pulse index and adjacent onset intervals", "why_it_matters": "Separates properties of one pulse from repetition rate and regularity." }, { "name": "Observation status", "kind": "state", "unit_or_values": "Resolved, ambiguous, partially observed, clipped or unresolved overlap; allow multiple applicable states", "why_it_matters": "Limits which measurements and actions the evidence supports." } ], "affordances": [ "Detect candidate pulses using a declared baseline, threshold and boundary rule.", "Segment a waveform into pulse candidates while retaining ambiguous merges and splits.", "Measure and compare pulse shapes using compatible units and conventions.", "Associate pulses with a sequence and estimate recurrence where enough observations exist.", "Specify a target pulse waveform and check whether a linked generator can produce it.", "Evaluate how filtering, resampling or shaping changes pulse identity and measured properties." ] }, "sources": [], "structure": { "bundles": [ { "id": "pulse-identity", "name": "Pulse identity", "description": "Establishes which sense of pulse is intended and what makes an excursion count as one instance.", "rationale": "The registry provides no definition, and the name spans meanings that cannot safely share one recognition rule.", "layers": [ { "id": "sense-and-observable", "name": "Sense and observable", "description": "Anchors the provisional temporal-pattern interpretation to a specific quantity.", "findings": [ { "id": "intended-pulse-sense", "name": "Intended pulse sense", "description": "Record the evidence for interpreting pulse as a bounded excursion and identify what quantity exhibits it.", "questions": [ { "text": "Does the originating registry record mean a temporal excursion, an arterial pulse, a musical beat or another sense?", "kind": "definition", "id": "intended-pulse-sense-q01" }, { "text": "Which registry source or domain reference supports the selected sense and pulsed quantity?", "kind": "provenance", "id": "intended-pulse-sense-q02" } ] } ] }, { "id": "excursion-membership", "name": "Excursion membership", "description": "Defines the baseline and finite-duration criterion used to recognise one pulse.", "findings": [ { "id": "pulse-versus-other-change", "name": "Pulse versus other change", "description": "Make pulse membership conditional on an explicit rule for departure, termination and separation from background variation.", "questions": [ { "text": "What baseline and departure criterion distinguish a candidate pulse from ordinary background variation?", "kind": "definition", "id": "pulse-versus-other-change-q01" }, { "text": "What termination rule distinguishes the pulse from a step, drift or an excursion cut off by the observation window?", "kind": "boundary", "id": "pulse-versus-other-change-q02" } ] } ] } ] }, { "id": "pulse-waveform", "name": "Pulse waveform", "description": "Describes the temporal extent and shape of an individual pulse under stated measurement conventions.", "rationale": "Amplitude and duration alone can hide differences in polarity, phases, tails and boundary conventions that matter to pulse use.", "layers": [ { "id": "onset-width-and-tail", "name": "Onset, width and tail", "description": "Identifies which parts of the waveform define its timing and duration.", "findings": [ { "id": "timing-convention", "name": "Timing convention", "description": "Record the rule used for onset, termination and width, including how gradual edges or long tails are handled.", "questions": [ { "text": "Which threshold or waveform feature defines onset and termination, and how are repeated crossings treated?", "kind": "measurement", "id": "timing-convention-q01" }, { "text": "Is reported duration a threshold width, full width at half maximum or another measure, and what uncertainty accompanies it?", "kind": "measurement", "id": "timing-convention-q02" } ] } ] }, { "id": "amplitude-and-phases", "name": "Amplitude and phases", "description": "Captures signed magnitude and internal waveform structure.", "findings": [ { "id": "pulse-shape-description", "name": "Pulse shape description", "description": "Describe extrema and phases without assuming a rectangular, positive or single-peaked pulse.", "questions": [ { "text": "What are the pulse's signed extrema relative to baseline, and in which quantity and unit are they measured?", "kind": "measurement", "id": "pulse-shape-description-q01" }, { "text": "Are secondary peaks, opposite-polarity phases and ringing part of this pulse or separate pulses under the selected convention?", "kind": "boundary", "id": "pulse-shape-description-q02" } ] } ] } ] }, { "id": "pulse-observation-and-separation", "name": "Pulse observation and separation", "description": "Assesses whether the available record resolves a pulse and supports separating it from nearby excursions.", "rationale": "Sampling, clipping and overlap can change the apparent number, width and amplitude of pulses.", "layers": [ { "id": "recording-resolution", "name": "Recording resolution", "description": "Relates observed pulse features to the acquisition and processing that produced the record.", "findings": [ { "id": "observed-versus-inferred-waveform", "name": "Observed versus inferred waveform", "description": "Distinguish features directly supported by observations from features inferred through processing or reconstruction.", "questions": [ { "text": "What sampling interval, sensor response and processing history produced the recorded pulse?", "kind": "provenance", "id": "observed-versus-inferred-waveform-q01" }, { "text": "Which pulse features remain measurable given noise, clipping, missing samples and the available temporal resolution?", "kind": "measurement", "id": "observed-versus-inferred-waveform-q02" } ] } ] }, { "id": "overlap-and-recurrence", "name": "Overlap and recurrence", "description": "Separates decisions about individual pulse boundaries from properties of a pulse sequence.", "findings": [ { "id": "individual-pulse-assignment", "name": "Individual pulse assignment", "description": "Record how overlapping or repeated excursions are assigned to individual pulses and linked into sequences.", "questions": [ { "text": "What evidence supports treating adjacent peaks as distinct pulses rather than phases or ringing of one pulse?", "kind": "boundary", "id": "individual-pulse-assignment-q01" }, { "text": "If the pulse belongs to a sequence, what onset intervals and missing-detection uncertainty support a repetition-rate or regularity estimate?", "kind": "measurement", "id": "individual-pulse-assignment-q02" } ] } ] } ] }, { "id": "pulse-use-and-transformation", "name": "Pulse use and transformation", "description": "Connects pulse descriptions to detection decisions, generation targets and waveform transformations.", "rationale": "An agent needs to know which pulse properties an operation must preserve and which decisions require evidence from a neighbouring model.", "layers": [ { "id": "detection-and-comparison", "name": "Detection and comparison", "description": "Defines usable criteria for accepting a pulse candidate or comparing pulses.", "findings": [ { "id": "pulse-decision-criteria", "name": "Pulse decision criteria", "description": "Tie detection and comparison to explicit tolerances and a stated purpose.", "questions": [ { "text": "What amplitude, width, shape and separation criteria permit accepting a candidate as a pulse for this task?", "kind": "action", "id": "pulse-decision-criteria-q01" }, { "text": "Which baseline, timing and normalisation conventions must be aligned before two pulses can be compared?", "kind": "measurement", "id": "pulse-decision-criteria-q02" } ] } ] }, { "id": "generation-and-shaping", "name": "Generation and shaping", "description": "Specifies intended waveform changes and links execution constraints to the relevant carrier or device model.", "findings": [ { "id": "pulse-transformation-contract", "name": "Pulse transformation contract", "description": "Record the target pulse, allowed deviations and properties that generation or transformation must preserve.", "questions": [ { "text": "When generating, filtering, resampling or shaping this pulse, which timing, amplitude and phase properties must remain within what tolerances?", "kind": "action", "id": "pulse-transformation-contract-q01" }, { "text": "Which linked device or medium model determines whether the requested pulse can be produced and what effects it may have?", "kind": "boundary", "id": "pulse-transformation-contract-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 answer assumes the general signal or physical-process meaning. Physiological pulse, musical pulse and edible pulses require different models.", "The listed kinds overlap: waveform shape, polarity and repetition are separate classification dimensions.", "Pulse width is convention-dependent; full width at half maximum and threshold-crossing definitions need not give identical results." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of pulse 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": [ "Rectangular pulse", "Gaussian pulse", "Unipolar pulse", "Bipolar pulse", "Single pulse", "Pulse train" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of pulse 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": [ "IEEE Std 181, issued by IEEE, standardizes terminology and measurement definitions for transitions, pulses and related waveforms." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of pulse 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": [ "Representing information through pulse timing, amplitude or width.", "Timing and synchronization in electronic systems.", "Estimating distance through pulse travel time in radar, lidar and sonar.", "Controlling average delivered power through pulse-width modulation.", "Probing system responses with brief excitation signals." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of pulse this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Pulse duration or width", "typical_range": "Application-dependent; the reference levels used to define width must be stated.", "unit": "s" }, { "quantity": "Peak amplitude", "typical_range": "Application-dependent and measured relative to a specified baseline.", "unit": "Unit of the pulsed quantity, such as V, A, Pa or W" }, { "quantity": "Rise time and fall time", "typical_range": "Application-dependent; measurement thresholds must be stated.", "unit": "s" }, { "quantity": "Pulse repetition frequency", "typical_range": "Applies to repeated pulses; application-dependent.", "unit": "Hz" }, { "quantity": "Duty cycle", "typical_range": "0-100% for a periodic rectangular pulse train, with the endpoints representing limiting cases.", "unit": "%" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of pulse 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": [ "Limited measurement bandwidth can distort the apparent amplitude, width and transition times.", "Ringing, overshoot and reflections can produce unintended peaks or false detections.", "Timing jitter can impair synchronization and travel-time measurements.", "Overlapping pulses can become difficult to distinguish individually.", "High peak power can damage equipment or create exposure hazards even when average power is modest." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of pulse 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": "impulse", "difference": "An ideal mathematical impulse has zero duration and finite integral; a physical pulse has nonzero duration." }, { "name": "step", "difference": "A step establishes a new sustained level; a pulse is localized in time." }, { "name": "wave", "difference": "A wave describes a disturbance with spatial and temporal behavior; a pulse can be a localized wave packet or simply a time-dependent signal." }, { "name": "transient", "difference": "A transient is any temporary response or departure from steady behavior; it need not form a distinct pulse." }, { "name": "arterial pulse", "difference": "An arterial pulse is a physiological pressure disturbance associated with cardiac activity, a specific physical phenomenon rather than the general signal concept." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of pulse this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which sense of pulse does vr.tr.pulse denote, and what does its placement in XCT / XCT.STA establish about that sense?", "Does an existing Vercy world model already own this concept, requiring a registry link instead of a separate publication?", "Which domain references should govern pulse boundaries, especially for long tails, baseline shifts and multiphasic excursions?", "Should pulse trains and recurrence statistics belong to this model or to a neighbouring sequence or signal model?", "Which domain-specific quantities, such as time-integrated amplitude, are necessary for intended tasks, and when do they have a justified physical interpretation?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 15, "questions": 23 } }, "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 pulse, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a pulse as a bounded temporal excursion, assess how reliably it has been identified and measured, and decide whether to detect, compare, isolate or modify it.", "characteristics": { "substance": "abstract", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Pulse wave velocity, anacrotic pulse.", "2 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 82 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 pulse, and on what evidence are they told apart?" ], "whatItIsMadeOf": "an abstraction with no physical instance", "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": [ "Pulse wave velocity", "anacrotic pulse" ] } ], "standing": "Described in 82 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 2 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 pulse from another, and a pulse 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 pulse, 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 pulse, 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 pulse 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 pulse, 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 pulse, 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 pulse 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 pulse 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 pulse, 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 pulse, 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 pulse 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 pulse from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a pulse, 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 pulse, 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 pulse 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 pulse 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 pulse between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a pulse, 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 pulse, 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 pulse 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 pulse, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a pulse 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 pulse, 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 pulse, 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 pulse 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 pulse 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 pulse 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 pulse 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 pulse 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 pulse?", "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 pulse?", "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 pulse 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 pulse and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a pulse, 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 pulse, 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 pulse 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 pulse is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a pulse, 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 pulse, 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 pulse is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 5, "layers": 10, "findings": 12, "questions": 32 } } } }