Glossary

A

App URL Access

A dashboard link that opens a read-only workspace view for a record when that view is available.

Approval Risk and decisions

A separate authority confirming an expectation or decision, tracked when it reduces risk.

Assigned By Me Delivery

A view of tasks where the current signed-in person assigned or requested the work.

Assigned To Me Delivery

A view of tasks assigned to any role the current signed-in person holds, plus tasks assigned to that person by name or email.

Assignee Role Delivery

An optional task field that directs work to a role without naming a specific person.

Assignor Delivery

The person recorded as assigning or requesting a task.

B

Benefit Item Cost and benefit

One item inside Benefits. It may have an amount or range, or it may be qualitative with no amount.

Benefits Cost and benefit

The expected value used during Weigh. Benefits may be quantified or qualitative.

Build Delivery

Turning committed requirements into tasks, working changes, and verification.

C

Cadence Run and support

How often recurring operational work is expected to happen, such as every month or every quarter.

Change Delivery

A record for a specific alteration to the running service. It keeps the change type, plan, execution, rollback, notice, veto, decision, result, recovery history, and optional Git commit references without controlling the operation.

Change Plan Delivery

The part of a Change record that explains what is changing, why, scope, timing, and notice.

Change Type Delivery

The classification of a Change as standard, normal, or emergency.

Checkpoint Risk and decisions

A confirmation point that reduces risk. It can be approved, formally accepted as risk by the Owner, or proceeded past with open risk visible.

Codex Delivery

A coding-capable model that may assist the Engineer. Codex is not a role.

Commitment Business context

An Owner record that says preparation is sufficient to commit requirements or expectations into Build, with any reservations kept visible.

Complete Engineering Delivery

The delivery part of DX Complete: build, check, validate, and put the change into use.

Component Run and support

One operational item in one Environment, such as an app, database, queue, storage location, or external service.

Condition Business context

Something that must be addressed before a Deferral can resolve into a Commitment.

Constraints Business context

Limits that affect the work, such as time, access, policy, budget, or risk.

Control Risk and decisions

A rule, check, or approval used to reduce risk.

D

Decision Risk and decisions

A recorded choice with entries kept in order. The latest decision entry is the current decision, while earlier entries remain visible.

Decision Entry Risk and decisions

One entry in a decision, such as an argument, note, or choice.

Decision Input Risk and decisions

A record that informed a decision. A decision can show what informed it, and a record can show which decisions used it.

Deferral Business context

An Owner record for not committing yet, with explicit conditions that make the path to a future Commitment clear.

Dependencies Business context

People, systems, data, or decisions the work depends on.

Deployment Delivery

Putting a release or change into use.

Dev Log Delivery

An internal code-history record that shows what landed in the workspace repository.

Dev Log Summary Delivery

A compact Dev Log entry that summarizes older commits while keeping the original details retrievable.

DX Complete Ticket Business context

A ticket that stays in the workspace where it was filed. It is used to raise a question, report, request, correction, or follow-up with DX Complete. The submitter, internal users in that workspace, and DX Complete internal support can see it; unrelated End Users cannot. It is not part of the End User support menu.

E

Elicit Business context

Turning expectations into requirements, dependencies, unknowns, and risk before estimating the work.

Emergency Change Delivery

A Change where normal notice or review is shortened because the situation is important and immediate.

End User Role

The person the service is for; uses the service and provides requests, feedback, corrections, and issue reports.

Engineer Role

The role that turns committed requirements into tasks and working changes, directly or by driving coding-capable tools.

Environment Run and support

A named operating context such as local, staging, or production. Components belong to one Environment so each context can be understood separately.

Estimate Cost and benefit

An itemized cost estimate used during Weigh, linked to the requirements or expectations it covers.

Estimate Line Item Cost and benefit

One cost item inside an Estimate, with a label, amount or range, one-time or recurring timing, and currency.

Estimate Refinement Cost and benefit

Using real results to improve future cost and benefit estimates.

Evidence Risk and decisions

Information that supports a decision, check, release, or measurement.

Execution Plan Delivery

The ordered practical steps inside a Change record for carrying out the change.

Expectation Business context

The result a person or group expects, including how success will be recognized, with approval tracked where needed.

External User Access

A workspace member whose only role is End User. External users are offered only their own Support Request actions and cannot see other End Users' records, DX Complete Tickets, internal Tasks, or Dev Log entries.

F

Feedback Run and support

A signal from a user, support interaction, service issue, or observed result.

G

Git Commit Reference Delivery

An optional commit identifier recorded on a Change result or recovery event to show what code state was used. DX Complete can match it to Dev Log entries when the commit is present.

Go Live Delivery

Putting a change into use after readiness is confirmed.

Greenfield Business context

Work that starts from a new idea rather than an existing service.

H

Handoff Delivery

The point where a phase has enough clarity to move into the next phase.

I

Incident Run and support

A specific service-impacting or potentially service-impacting occurrence with response history, current status, and severity derived from ordered entries.

Incident Entry Run and support

One ordered entry in an Incident, such as detected, update, severity, resolved, reopened, or note.

Informed By Risk and decisions

The relationship from a decision to the record that helped inform it.

Internal User Access

A workspace member with Owner, Engineer, Tester, Operator, or Support Agent role. Any one of those roles makes a multi-role user internal for access checks.

J

Journal Business context

A shared workspace record for useful notes that do not have a better dedicated home.

Journal Note Business context

A raw Journal entry with text, author, and time. It can be summarized later without being deleted.

Journal Summary Business context

A compact Journal entry that summarizes older notes and points back to them so details remain retrievable.

K

Known Error Run and support

A Problem state showing an underlying cause is known even if the full improvement is not complete.

L

Limited Disclosure Business context

A situation where some information is unavailable or cannot be shared.

Locator Run and support

Location information for a Component, such as a URL, project, region, host, or route.

M

Maintenance Schedule Run and support

A recurring operational hygiene record with cadence, start date, rationale, and due state derived from linked completed Changes or Tasks.

Measure Cost and benefit

Compare expected and actual cost or benefit when data is available.

Measured At Cost and benefit

The date or time when a value metric baseline or actual value was measured.

Measurement Cost and benefit

Comparing expected and actual cost or benefit when data is available.

N

Normal Change Delivery

The default Change type for an assessed alteration to the running service.

O

Operate Run and support

Run the service, support users, and respond to issues.

Operational Registry Run and support

The inventory of Environments and Components. It shows what exists and where it lives without monitoring, diagnosing, storing secret values, or replacing operating procedures.

Operator Role

The role that releases, deploys, monitors, runs the service, and manages users, permissions, settings, provisioning, and run-side security.

Outcome Business context

The result the work is meant to create or improve.

Owner Role

The role that sets authority, priority, outcome direction, requirements, product validation direction, budget commitment, escalation direction, and formal risk acceptance.

P

Problem Run and support

An underlying or recurring cause evidenced by one or more Incidents, with investigation, root-cause, known-error, and resolution history.

Problem Entry Run and support

One ordered entry in a Problem, such as identified, investigation, root cause, known error, resolved, reopened, or note.

Proceeding Past an Open Checkpoint Risk and decisions

Moving forward while an approval, readiness concern, or other checkpoint is still open. The risk remains visible and is not formally accepted.

Product Validation Delivery

Confirming that the completed work achieves the intended outcome.

Q

QA Verification Delivery

Checking that completed work meets the requirements and success criteria.

R

Readable ID Business context

A short record reference such as RQM-0001. It helps people refer to a record without reading the full system ID.

Readiness Checks Delivery

The checks used before Go Live to confirm that a change is prepared, supportable, and safe enough to put into use.

Record Business context

Information kept so decisions, work, service issues, and measurements can be followed over time.

Record Link Business context

A relationship from one record to another. Links can be added or removed when the relationship changes or was recorded incorrectly.

Release Delivery

A set of changes prepared to be put into use.

Requirement Delivery

A commitment to make something true in a buildable and checkable way.

Requirement Detail Delivery

Optional behavior, edge cases, or check notes kept with a requirement.

Requirement Set Business context

The group of requirements being estimated, committed, built, or stopped together.

Reservation Business context

A concern recorded inside a Commitment when the Owner moves forward despite it.

Review Note Delivery

A free-text note on an expectation or requirement. It may be marked important, but it does not block progress or require an Owner response.

Risk Risk and decisions

Something uncertain that could affect value, delivery, service, compliance, or operations. Current risk state comes from ordered entries.

Risk Acceptance Risk and decisions

An Owner decision to own an open risk on the project's behalf. It is different from simply proceeding past an open checkpoint.

Risk Entry Risk and decisions

One ordered entry in a Risk, such as identified, assessment, treatment, monitor note, closed, or reopened.

Risk Treatment Risk and decisions

The chosen response to a Risk: accept, mitigate, transfer, or avoid. Formal acceptance is Owner-only.

Roll-up Cost and benefit

Grouped totals from quantified cost or benefit items, keeping one-time amounts, recurring amounts, periods, and currencies distinct.

Rollback Plan Delivery

The part of a Change record that explains how to reverse or recover if the change fails or should not remain in use.

Root Cause Run and support

The underlying cause recorded in a Problem when investigation identifies why one or more incidents occurred.

RQM Business context

Requirement. Historical text may reference REQ-NNNN from before the rename; numbering is unchanged. RQM is not a request, Support Request, or DX Complete Ticket.

S

Secret Pointer Run and support

A reference to where a secret is stored and what it is called. It should not contain the secret value.

Standard Change Delivery

A low-risk, pre-understood, repeatable Change type.

Statement Business context

A person's own words before they are interpreted or translated.

Success Criteria Delivery

The conditions used to decide whether completed work satisfies the need.

Support Agent Role

The role that helps users, captures signals, and routes questions, feedback, and issues to the right follow-up.

Support Request Run and support

A support record for a reported user experience, question, request, or issue. The filer and internal users can see it; unrelated End Users cannot. End Users can submit, read, follow up on, reopen, and see unread replies for their own Support Requests.

Support Request Entry Run and support

One ordered entry in a Support Request, such as raised, triage, update, escalated, resolved, reopened, or note.

T

Task Delivery

An internal work-order record with entries kept in order. The latest status entry is the current task status.

Task Entry Delivery

One entry in a task, such as a comment, note, or status change.

Tester Role

The role that checks completed work against requirements and success criteria.

Transformation Business context

Improving an existing service or way of working.

U

Unknowns Business context

Important questions that are not answered yet.

V

Value Metric Cost and benefit

One before-and-after measure inside Value Realization, with a baseline, optional actual value, unit, direction, and measured dates.

Value Realization Cost and benefit

A record that compares baseline and actual value metrics after work or operation when measurement is available.

Version History Risk and decisions

Prior versions kept when an expectation or requirement changes, so current wording can be understood without losing what came before.

Veto Risk and decisions

A serious recorded objection to a Change by the Owner or Engineer. It does not mechanically stop the Operator, but proceeding over it creates a strong accountability record.

W

Weigh Business context

The phase where cost, value, risk, and confidence are compared before recording a Commitment or Deferral.

Workspace Business context

The container for one service and the work connected to it.