Working vocabularyM
Working vocabulary
These definitions identify the meanings used throughout the manual. A particular workflow may prescribe a narrower field or state meaning; its contract governs that use.
| Term | Meaning in this manual |
|---|---|
| Accepted basis | The applicable requirements, decisions, commitments, and identified material under which an undertaking proceeds. |
| Acceptance | An attributable human act concerning identified content, scope, and purpose. Its authority and effect follow the governing arrangement. |
| Actual state | The work that exists and what it does, including incomplete, unmerged, or unverified contributions. |
| Agency | The ability to act within an undertaking. Its exercise does not by itself confer authority to accept responsibility for the result. |
| Agent instance | A model operating with instructions, supplied context, available tools, and actual host permissions. |
| Agent Type | A responsibility category: 0 for alignment and coordination, 1 for managing an undertaking, and 2 for bounded execution without further delegation. It is neither a model tier nor a measure of actual delegation depth. |
| Artifact | An identifiable output or record. Its existence, adequacy, and acceptance are separate questions. |
| Basis amendment | An authorised change to the applicable commitments or decisions, with its scope and consequences preserved. |
| Brief | The run-specific objective, basis, context, permissions, expected result, and checks for an assignment. Its form is proportionate to the work. |
| Candidate | The identified version of a contribution or product submitted to a particular examination, integration, or acceptance. |
| Claim | An assertion whose grounds and standing can be examined. Maintained production claims concern obligations and relationships the project needs to preserve. |
| Completion | Fulfilment of stated conditions at an identified scope. Node, undertaking, Deliverable, and project completion have different extents. |
| Computer Use | Harness capability through which an agent observes an application and operates supported controls in an authorised environment. |
| Context | Material actually supplied to an agent instance, including instructions, conversation, sources, and tool results. |
| Deferred work | An identified obligation with no present allocation in the current local work graph or another owned undertaking. Its record preserves the commitment, missing allocation, needed owner or precursor, and responsibility for reconsideration. |
| Deliverable | An identified unit of committed output, with a scope, responsibility, and basis for assessment. It can require many bounded assignments. |
| Dependency | A relationship with stated meaning under which one contribution requires or bears upon another. A prerequisite identifies the required input and the point at which it is needed. |
| Evidence | Retained observations or examinations supporting a claim, tied to the subject and conditions actually examined. |
| Graph, local work | The executable route for a selected undertaking: nodes, prerequisites, ownership, results, evidence, and recovery. It can span many sessions. |
| Graph, project DAG | A directed acyclic graph of project production relationships for a stated objective and edge meaning. Pending dependencies can remain within it. |
| Handoff | A record explaining a position and its remaining consequences to a successor. Its extent follows the information needed for continuation and the requirements of the chosen method. |
| Harness | The environment through which an agent receives context, invokes tools, and performs actions. |
| Integration | The work of combining contributions and examining their relationships in an identified receiving candidate. |
| Judgment | The human’s situated consideration of purpose, evidence, consequences, and the commitments for which they will answer. |
| Lifecycle state | A Deliverable’s governed production and change-control condition, distinct from the project’s percentage-labelled stage. |
| Memory | A terse deliverable-local run index: stable run ID/date, work performed here, and pointers to the PR, central evidence, decisions and transfers. Preserve historical entries; local memory neither duplicates ruling substance nor changes central authority. |
| Other | A contributor whose work the responsible person receives and examines before relying upon it; includes human and artificial contributors. |
| Package | A defined partition of project scope containing Deliverables under the adopted decomposition rules. |
| PRD / DBM | Product requirements document / design basis memorandum. In their respective domains they carry the examined basis from conception into project definition. |
| Product | The intended usable result and associated outcomes. It may persist through several projects. |
| Project | The organised undertaking through which participants develop, examine, and deliver a result or reach another explicit conclusion. |
| Reckoning | The artificial agent’s computational organisation and use of information through interpretation, inference, comparison, selection, generation, and checking. |
| Reconciliation | Examination and treatment of differences among commitments, produced work, evidence and records. The bounded development method is one planned closeout stage after implementation/evidence integration; later authorized undertakings address later changes. |
| Recorded state | The account available in project files, graphs, reports, and other retained records. It must be compared with actual work and the accepted basis. |
| Unfulfilled obligation | A difference between the required contribution and what actual work and evidence support. Executable treatment belongs in the owning work graph; it is not a separate deliverable task list. |
| Role | A responsibility in the collaboration. It is distinct from the assignment’s subject and from model capability or reasoning effort. |
| Scope change | Amendment of accepted decomposition, with the decision, its effects, and the resulting state carried through the responsible work and records. |
| Scope of Work | The Deliverable’s production contract, relating purpose, outputs, requirements, evaluation, methods, and governing choices. |
| Session | A period of interaction with an agent. Its end need not complete the undertaking. |
| Stage gate | A human assessment of whether the accumulated work supports the proposed transition. |
| Steering | Human direction of the present objective, limits, priorities, approach, execution strategy, and continuation or decision points. |
| Undertaking | A bounded contribution whose result and remaining obligations can be assessed. |
| Validation | Examination of suitability for intended use. This general systems-engineering use does not redefine a formal professional-practice act of the same name. |
| Verification | Examination against specified requirements or declared checks. |
| Warrant | Grounds offered in support of a claim, available for examination beyond the model’s confidence or the fluency of its output. |
| Workflow | Reusable method or coordination guidance selected within the active role, assignment, and actual permissions. |
The definitions condense the account developed in Chapters 1–6. They supply a reading aid without creating new workflow fields or states.