{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-11T21:25:36Z", "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": 2, "engine": "claude", "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-05T23:50:00Z", "ingestedAt": "2026-10-05T20:46:32+00:00", "fields": [ "agent_conduct", "ethics", "owners" ] }, "revisions": [ { "at": "2026-10-06T22:54:45+00:00", "engine": "codex", "fields": [ "agent_conduct", "definition", "distinguishing_features", "ethics", "failure_modes_and_hazards", "owners", "purpose", "visual_identification" ], "answering_review": "d2e6a69ec750a3f8fe5b0c9999f84fed1f93c20032c5e7bf6a3e3a05c84e83e1" } ], "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:31+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q5260617", "registryId": "vr.tr.dependency-q5260617", "name": "dependency", "version": "0.2.0-wave.2", "entryKind": "thing", "family": "Thing Registry", "domain": [ "XCT.REL" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q5260617/", "model": { "registry_id": "vr.tr.dependency-q5260617", "name": "dependency", "purpose": "Let an agent explain and map project-task prerequisites, identify scheduling risks and distinguish required task order from unrelated uses of dependency.", "definition": "A prerequisite relationship between project tasks in which one task requires another task to be completed before it can begin.", "what_it_is_for": "Modelling what relies on what.", "affordances": [ "explain kinds of dependency", "model dependencies in software, data and projects", "analyse dependency risks", "separate other senses" ], "distinguishing_features": [ "The relationship runs from a prerequisite task to a dependent task.", "The prerequisite task must finish before the dependent task can begin.", "The relationship constrains a project schedule.", "Task dependencies can be represented in a directed graph." ], "appearance": "Not physical; arrows in dependency graphs and conditions in rules.", "visual_identification": [ "A project schedule links a prerequisite task to a dependent task.", "The link indicates that the prerequisite must finish before the dependent task begins.", "Tasks appearing together or near each other do not by themselves establish a dependency." ], "physical_properties": [], "families_and_kinds": [ "software and package dependencies", "functional dependencies in databases", "task dependencies in scheduling", "logical, causal and conditional dependencies", "dependency of legal status on facts" ], "related_models": [ { "relation": "is a kind of", "target": "relation", "why": "category" }, { "relation": "is related to", "target": "bridge", "why": "critical links in dependency graphs" }, { "relation": "is related to", "target": "open-source software", "why": "software dependencies" }, { "relation": "is related to", "target": "cause", "why": "causal dependency" } ], "identifiers": [], "standards_and_regulation": [ "Package management and software bill of materials standards", "Database normalisation theory", "Project scheduling standards" ], "failure_modes_and_hazards": [ "Circular prerequisites can prevent dependent tasks from starting.", "Hidden or missing prerequisites can cause scheduling failures.", "Treating a preferred task order as a required dependency can unnecessarily constrain a schedule." ], "in_scope": [], "out_of_scope": [], "characteristics": [], "agent_conduct": { "may": [ "Map and report prerequisites between project tasks it is authorized to read.", "Flag circular, missing or hidden task dependencies before a schedule change is made." ], "must_not": [ "Remove or change a task prerequisite without checking its effect on dependent tasks.", "Present coinciding tasks or a preferred task order as a verified prerequisite relationship.", "Hide a known task dependency that puts a project schedule at risk.", "Invent task prerequisites without supporting project information." ], "requires_human": [ "Changing dependencies in shared project schedules.", "Resolving disputed prerequisites that affect team commitments." ] }, "ethics": { "considerations": [ "Hidden task dependencies can pass delays and burdens to teams that did not choose the risk.", "Unsupported claims about task prerequisites can assign blame or credit wrongly." ], "affected_parties": [ "People responsible for prerequisite and dependent tasks are affected.", "Project managers and schedule maintainers are affected.", "Teams working on shared schedules are affected." ] }, "owners": { "steward": "Nobody owns the relation; the responsible project owner answers for the dependencies recorded in the project plan.", "master_systems": [] } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q5260617: dependency", "url": "https://www.wikidata.org/wiki/Q5260617", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Dependency (project management)", "url": "https://en.wikipedia.org/wiki/Dependency_%28project_management%29", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "understand", "name": "Understand", "description": "What dependency means.", "rationale": "Concept.", "layers": [ { "id": "concept", "name": "Concept", "description": "The relation.", "findings": [ { "id": "concept-finding", "name": "Concept", "description": "Concept.", "questions": [ { "text": "What does it mean for one thing to depend on another in this context, and in which direction does the relation run?", "kind": "definition" }, { "text": "How does dependency differ from correlation or association?", "kind": "definition" } ] } ] }, { "id": "senses", "name": "Senses", "description": "Other senses.", "findings": [ { "id": "senses-finding", "name": "Senses", "description": "Other senses.", "questions": [ { "text": "Is a dependent territory, economic dependency, substance dependence or a relation meant?", "kind": "boundary" }, { "text": "Which entry fits?", "kind": "action" } ] } ] } ] }, { "id": "model", "name": "Model", "description": "Modelling dependencies.", "rationale": "Graphs and rules.", "layers": [ { "id": "graph", "name": "Graph", "description": "Dependency graphs.", "findings": [ { "id": "graph-finding", "name": "Graph", "description": "Graphs.", "questions": [ { "text": "How can the dependencies in this system be modelled as a graph, and are there cycles?", "kind": "action" }, { "text": "What order does a topological sort give?", "kind": "action" } ] } ] }, { "id": "conditions", "name": "Conditions", "description": "Conditional dependencies.", "findings": [ { "id": "conditions-finding", "name": "Conditions", "description": "Conditions.", "questions": [ { "text": "How does a status such as copyright depend on facts like publication date and formalities, and how can such rules be expressed?", "kind": "definition" }, { "text": "Which facts must be established?", "kind": "action" } ] } ] } ] }, { "id": "domains", "name": "Domains", "description": "By domain.", "rationale": "Software, data, projects.", "layers": [ { "id": "software", "name": "Software", "description": "Software dependencies.", "findings": [ { "id": "software-finding", "name": "Software", "description": "Software.", "questions": [ { "text": "What are the dependencies of this software, and how are versions and licences managed?", "kind": "provenance" }, { "text": "Which vulnerabilities do dependencies introduce?", "kind": "provenance" } ] } ] }, { "id": "data", "name": "Data", "description": "Data and schedule dependencies.", "findings": [ { "id": "data-finding", "name": "Data", "description": "Data and schedules.", "questions": [ { "text": "What are functional dependencies in a database, and how do they drive normalisation?", "kind": "definition" }, { "text": "How are task dependencies used in project schedules and critical path analysis?", "kind": "definition" } ] } ] } ] }, { "id": "manage", "name": "Manage", "description": "Risk and change.", "rationale": "Practice.", "layers": [ { "id": "risk", "name": "Risk", "description": "Dependency risk.", "findings": [ { "id": "risk-finding", "name": "Risk", "description": "Risk.", "questions": [ { "text": "Which dependencies are critical single points of failure, and how can they be mitigated?", "kind": "action" }, { "text": "How is dependency drift managed?", "kind": "action" } ] } ] }, { "id": "change", "name": "Change", "description": "Changing dependencies.", "findings": [ { "id": "change-finding", "name": "Change", "description": "Change.", "questions": [ { "text": "How does a change in one component propagate through dependencies?", "kind": "action" }, { "text": "Which tools analyse impact?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Should software dependency be a separate entry?", "How should dependency tooling be linked?", "How should other senses be split?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }