dxcomplete 0.1.0 → 0.2.0

package/website/glossary.html

@@ -23,6 +23,7 @@
           <a class="nav-link" href="./flow.html">Flow</a>
           <a class="nav-link" href="./objects.html">Records</a>
           <a class="nav-link" href="./roles.html">Roles</a>
+          <a class="nav-link" href="./operating-guide.html">Operating Guide</a>
           <a class="nav-link" href="./glossary.html">Glossary</a>
         </nav>
       </aside>
@@ -45,10 +46,10 @@
             <a href="#h">H</a>
             <a href="#i">I</a>
             <a href="#j">J</a>
-            <span aria-disabled="true">K</span>
+            <a href="#k">K</a>
             <a href="#l">L</a>
             <a href="#m">M</a>
-            <span aria-disabled="true">N</span>
+            <a href="#n">N</a>
             <a href="#o">O</a>
             <a href="#p">P</a>
             <a href="#q">Q</a>
@@ -83,8 +84,10 @@
             <section id="c" class="glossary-letter">
               <h2>C</h2>
               <dl class="glossary-list">
-                <div><dt>Change <span>Delivery</span></dt><dd>A record for a specific alteration to the running service. It keeps the plan, execution, rollback, notice, veto, emergency, decision, result, and recovery history without controlling the operation.</dd></div>
+                <div><dt>Cadence <span>Run and support</span></dt><dd>How often recurring operational work is expected to happen, such as every month or every quarter.</dd></div>
+                <div><dt>Change <span>Delivery</span></dt><dd>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.</dd></div>
                 <div><dt>Change Plan <span>Delivery</span></dt><dd>The part of a Change record that explains what is changing, why, scope, timing, and notice.</dd></div>
+                <div><dt>Change Type <span>Delivery</span></dt><dd>The classification of a Change as standard, normal, or emergency.</dd></div>
                 <div><dt>Checkpoint <span>Risk and decisions</span></dt><dd>A confirmation point that reduces risk. It can be approved, formally accepted as risk by the Owner, or proceeded past with open risk visible.</dd></div>
                 <div><dt>Codex <span>Delivery</span></dt><dd>A coding-capable model that may assist the Engineer. Codex is not a role.</dd></div>
                 <div><dt>Commitment <span>Business context</span></dt><dd>An Owner record that says preparation is sufficient to commit requirements or expectations into Build, with any reservations kept visible.</dd></div>
@@ -113,7 +116,7 @@
               <h2>E</h2>
               <dl class="glossary-list">
                 <div><dt>Elicit <span>Business context</span></dt><dd>Turning expectations into requirements, dependencies, unknowns, and risk before estimating the work.</dd></div>
-                <div><dt>Emergency Change <span>Delivery</span></dt><dd>A change where normal notice is shortened or skipped because both importance and immediacy are recorded.</dd></div>
+                <div><dt>Emergency Change <span>Delivery</span></dt><dd>A Change where normal notice or review is shortened because the situation is important and immediate.</dd></div>
                 <div><dt>End User <span>Role</span></dt><dd>The person the service is for; uses the service and provides requests, feedback, corrections, and issue reports.</dd></div>
                 <div><dt>Engineer <span>Role</span></dt><dd>The role that turns committed requirements into tasks and working changes, directly or by driving coding-capable tools.</dd></div>
                 <div><dt>Environment <span>Run and support</span></dt><dd>A named operating context such as local, staging, or production. Components belong to one Environment so each context can be understood separately.</dd></div>
@@ -136,6 +139,7 @@
             <section id="g" class="glossary-letter">
               <h2>G</h2>
               <dl class="glossary-list">
+                <div><dt>Git Commit Reference <span>Delivery</span></dt><dd>An optional commit identifier recorded on a Change result or recovery event to show what code state was used for that execution attempt or rollback. DX Complete records the reference as provided and does not validate it.</dd></div>
                 <div><dt>Go Live <span>Delivery</span></dt><dd>Putting a change into use after readiness is confirmed.</dd></div>
                 <div><dt>Greenfield <span>Business context</span></dt><dd>Work that starts from a new idea rather than an existing service.</dd></div>
               </dl>
@@ -151,7 +155,8 @@
             <section id="i" class="glossary-letter">
               <h2>I</h2>
               <dl class="glossary-list">
-                <div><dt>Incident <span>Run and support</span></dt><dd>An event that affects, or may affect, the service and needs a response.</dd></div>
+                <div><dt>Incident <span>Run and support</span></dt><dd>A specific service-impacting or potentially service-impacting occurrence with response history, current status, and severity derived from ordered entries.</dd></div>
+                <div><dt>Incident Entry <span>Run and support</span></dt><dd>One ordered entry in an Incident, such as detected, update, severity, resolved, reopened, or note.</dd></div>
                 <div><dt>Informed By <span>Risk and decisions</span></dt><dd>The relationship from a decision to the record that helped inform it.</dd></div>
               </dl>
             </section>
@@ -165,6 +170,13 @@
               </dl>
             </section>
 
+            <section id="k" class="glossary-letter">
+              <h2>K</h2>
+              <dl class="glossary-list">
+                <div><dt>Known Error <span>Run and support</span></dt><dd>A Problem state showing an underlying cause is known even if the full improvement is not complete.</dd></div>
+              </dl>
+            </section>
+
             <section id="l" class="glossary-letter">
               <h2>L</h2>
               <dl class="glossary-list">
@@ -176,11 +188,20 @@
             <section id="m" class="glossary-letter">
               <h2>M</h2>
               <dl class="glossary-list">
+                <div><dt>Maintenance Schedule <span>Run and support</span></dt><dd>A recurring operational hygiene record with cadence, start date, rationale, and due state derived from linked completed Changes or Tasks.</dd></div>
                 <div><dt>Measure <span>Cost and benefit</span></dt><dd>Compare expected and actual cost or benefit when data is available.</dd></div>
+                <div><dt>Measured At <span>Cost and benefit</span></dt><dd>The date or time when a value metric baseline or actual value was measured.</dd></div>
                 <div><dt>Measurement <span>Cost and benefit</span></dt><dd>Comparing expected and actual cost or benefit when data is available.</dd></div>
               </dl>
             </section>
 
+            <section id="n" class="glossary-letter">
+              <h2>N</h2>
+              <dl class="glossary-list">
+                <div><dt>Normal Change <span>Delivery</span></dt><dd>The default Change type for an assessed alteration to the running service.</dd></div>
+              </dl>
+            </section>
+
             <section id="o" class="glossary-letter">
               <h2>O</h2>
               <dl class="glossary-list">
@@ -195,7 +216,8 @@
             <section id="p" class="glossary-letter">
               <h2>P</h2>
               <dl class="glossary-list">
-                <div><dt>Problem <span>Run and support</span></dt><dd>An underlying or repeated issue that may need deeper improvement work.</dd></div>
+                <div><dt>Problem <span>Run and support</span></dt><dd>An underlying or recurring cause evidenced by one or more Incidents, with investigation, root-cause, known-error, and resolution history.</dd></div>
+                <div><dt>Problem Entry <span>Run and support</span></dt><dd>One ordered entry in a Problem, such as identified, investigation, root cause, known error, resolved, reopened, or note.</dd></div>
                 <div><dt>Proceeding Past an Open Checkpoint <span>Risk and decisions</span></dt><dd>Moving forward while an approval, readiness concern, or other checkpoint is still open. The risk remains visible and is not formally accepted.</dd></div>
                 <div><dt>Product Validation <span>Delivery</span></dt><dd>Confirming that the completed work achieves the intended outcome.</dd></div>
               </dl>
@@ -221,10 +243,13 @@
                 <div><dt>Requirement Set <span>Business context</span></dt><dd>The group of requirements being estimated, committed, built, or stopped together.</dd></div>
                 <div><dt>Reservation <span>Business context</span></dt><dd>A concern recorded inside a Commitment when the Owner moves forward despite it.</dd></div>
                 <div><dt>Review Note <span>Delivery</span></dt><dd>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.</dd></div>
-                <div><dt>Risk <span>Risk and decisions</span></dt><dd>Something uncertain that could affect value, delivery, service, or compliance.</dd></div>
+                <div><dt>Risk <span>Risk and decisions</span></dt><dd>Something uncertain that could affect value, delivery, service, compliance, or operations. Current risk state comes from ordered entries.</dd></div>
                 <div><dt>Risk Acceptance <span>Risk and decisions</span></dt><dd>An Owner decision to own an open risk on the project's behalf. It is different from simply proceeding past an open checkpoint.</dd></div>
+                <div><dt>Risk Entry <span>Risk and decisions</span></dt><dd>One ordered entry in a Risk, such as identified, assessment, treatment, monitor note, closed, or reopened.</dd></div>
+                <div><dt>Risk Treatment <span>Risk and decisions</span></dt><dd>The chosen response to a Risk: accept, mitigate, transfer, or avoid. Formal acceptance is Owner-only.</dd></div>
                 <div><dt>Roll-up <span>Cost and benefit</span></dt><dd>Grouped totals from quantified cost or benefit items, keeping one-time amounts, recurring amounts, periods, and currencies distinct.</dd></div>
                 <div><dt>Rollback Plan <span>Delivery</span></dt><dd>The part of a Change record that explains how to reverse or recover if the change fails or should not remain in use.</dd></div>
+                <div><dt>Root Cause <span>Run and support</span></dt><dd>The underlying cause recorded in a Problem when investigation identifies why one or more incidents occurred.</dd></div>
               </dl>
             </section>
 
@@ -232,10 +257,12 @@
               <h2>S</h2>
               <dl class="glossary-list">
                 <div><dt>Secret Pointer <span>Run and support</span></dt><dd>A reference to where a secret is stored and what it is called. It should not contain the secret value.</dd></div>
+                <div><dt>Standard Change <span>Delivery</span></dt><dd>A low-risk, pre-understood, repeatable Change type.</dd></div>
                 <div><dt>Statement <span>Business context</span></dt><dd>A person's own words before they are interpreted or translated.</dd></div>
                 <div><dt>Success Criteria <span>Delivery</span></dt><dd>The conditions used to decide whether completed work satisfies the need.</dd></div>
                 <div><dt>Support Agent <span>Role</span></dt><dd>The role that helps users, captures signals, and routes questions, feedback, and issues to the right follow-up.</dd></div>
-                <div><dt>Support Ticket <span>Run and support</span></dt><dd>A user request, question, or issue report.</dd></div>
+                <div><dt>Support Request <span>Run and support</span></dt><dd>A shared support record for a reported user experience, question, request, or issue that needs workspace-visible follow-up.</dd></div>
+                <div><dt>Support Request Entry <span>Run and support</span></dt><dd>One ordered entry in a Support Request, such as raised, triage, update, escalated, resolved, reopened, or note.</dd></div>
               </dl>
             </section>
 
@@ -259,6 +286,8 @@
             <section id="v" class="glossary-letter">
               <h2>V</h2>
               <dl class="glossary-list">
+                <div><dt>Value Metric <span>Cost and benefit</span></dt><dd>One before-and-after measure inside Value Realization, with a baseline, optional actual value, unit, direction, and measured dates.</dd></div>
+                <div><dt>Value Realization <span>Cost and benefit</span></dt><dd>A record that compares baseline and actual value metrics after work or operation when measurement is available.</dd></div>
                 <div><dt>Version History <span>Risk and decisions</span></dt><dd>Prior versions kept when an expectation or requirement changes, so current wording can be understood without losing what came before.</dd></div>
                 <div><dt>Veto <span>Risk and decisions</span></dt><dd>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.</dd></div>
               </dl>

package/website/index.html

@@ -28,6 +28,7 @@
           <a class="nav-link" href="./flow.html">Flow</a>
           <a class="nav-link" href="./objects.html">Records</a>
           <a class="nav-link" href="./roles.html">Roles</a>
+          <a class="nav-link" href="./operating-guide.html">Operating Guide</a>
           <a class="nav-link" href="./glossary.html">Glossary</a>
         </nav>
       </aside>
@@ -40,7 +41,7 @@
             A practical way to decide what is worth doing, deliver it with control, run it safely, and learn from the results.
           </p>
           <p>
-            The documentation is split into outcomes, flow, records, roles, and terms. Outcomes explain why the process exists. Flow explains what happens over time. Records explain what gets captured. Roles explain who is responsible. The glossary defines shared language.
+            The documentation is split into outcomes, flow, records, roles, operating guidance, and terms. Outcomes explain why the process exists. Flow explains what happens over time. Records explain what gets captured. Roles explain who is responsible. The Operating Guide explains how each role uses the records. The glossary defines shared language.
           </p>
 
           <div class="phase-map" aria-label="DX Complete broad phases">

package/website/objects.html

@@ -23,6 +23,7 @@
           <a class="nav-link" href="./flow.html">Flow</a>
           <a class="nav-link" href="./objects.html">Records</a>
           <a class="nav-link" href="./roles.html">Roles</a>
+          <a class="nav-link" href="./operating-guide.html">Operating Guide</a>
           <a class="nav-link" href="./glossary.html">Glossary</a>
         </nav>
       </aside>
@@ -47,8 +48,13 @@
               <div><span>Desired result</span><b>Use Statement, Expectation, or Requirement</b><p>Use these when the information says what should be true, what success looks like, or what must be made buildable.</p></div>
               <div><span>Choice</span><b>Use Decision</b><p>Use Decision when alternatives were considered and a choice should remain visible.</p></div>
               <div><span>Action</span><b>Use Task</b><p>Use Task when someone needs to do or coordinate work.</p></div>
-              <div><span>Service event or risk</span><b>Use Change or Risk</b><p>Use the matching record when the information is controlled history, service change, uncertainty, or exposure.</p></div>
+              <div><span>Run-side alteration</span><b>Use Change</b><p>Use Change for a discrete alteration to the running service, with plan, execution, rollback, risk, and event history.</p></div>
+              <div><span>User support follow-up</span><b>Use Support Request</b><p>Use Support Request for a shared user-facing question, request, or issue that needs follow-up.</p></div>
+              <div><span>Uncertainty or exposure</span><b>Use Risk</b><p>Use Risk when something uncertain could affect value, delivery, service, or compliance.</p></div>
               <div><span>Infrastructure state</span><b>Use Environment or Component</b><p>Use the Operational Registry for what exists, where it lives, and which secret locations matter.</p></div>
+              <div><span>Recurring operations</span><b>Use Maintenance Schedule</b><p>Use Maintenance Schedule for recurring service hygiene, such as scheduled checks, reviews, rotations, or maintenance duties.</p></div>
+              <div><span>Measured value</span><b>Use Value Realization</b><p>Use Value Realization when actual before-and-after value can be compared.</p></div>
+              <div><span>User question or report</span><b>Use DX Complete Ticket</b><p>Use a ticket first when a user raises a question, report, request, correction, or follow-up with DX Complete.</p></div>
               <div><span>Useful context</span><b>Use Journal</b><p>Use Journal for relevant background, preference, observation, or context that does not fit a dedicated record.</p></div>
             </div>
             <p>
@@ -143,6 +149,15 @@
                     <div><span>Version history</span><b>Automatic</b><p>Prior versions are kept when Benefits change.</p></div>
                   </div>
                 </details>
+                <details class="record-item">
+                  <summary><span class="record-name">Value Realization</span><span class="record-summary">Measured before-and-after value for expectations, requirements, or commitments.</span></summary>
+                  <div class="record-fields" aria-label="Value Realization fields">
+                    <div><span>Value metrics</span><b>Required</b><p>One or more measures with a baseline, unit, direction, and optional actual value.</p></div>
+                    <div><span>Covered scope</span><b>Required</b><p>The expectations, requirements, or commitments the measurement relates to.</p></div>
+                    <div><span>Comparison</span><b>Automatic</b><p>Measured metrics show improvement, regression, no change, or an open measurement gap.</p></div>
+                    <div><span>Version history</span><b>Automatic</b><p>Prior versions are kept when metrics change.</p></div>
+                  </div>
+                </details>
                 <details class="record-item">
                   <summary><span class="record-name">Commitment</span><span class="record-summary">An Owner record that moves requirements or expectations into Build.</span></summary>
                   <div class="record-fields" aria-label="Commitment fields">
@@ -162,14 +177,14 @@
                   </div>
                 </details>
                 <details class="record-item">
-                  <summary><span class="record-name">Risk</span><span class="record-summary">Something uncertain that could affect value, delivery, service, or compliance.</span></summary>
+                  <summary><span class="record-name">Risk</span><span class="record-summary">Something uncertain that could affect value, delivery, service, compliance, or operations.</span></summary>
                   <div class="record-fields" aria-label="Risk fields">
-                    <div><span>Risk</span><b>Required</b><p>The uncertainty or exposure.</p></div>
-                    <div><span>Impact</span><b>Required</b><p>What could happen if the risk occurs.</p></div>
-                    <div><span>Likelihood</span><b>Optional</b><p>How likely the risk seems.</p></div>
-                    <div><span>Response</span><b>Optional</b><p>How the risk should be reduced, accepted, avoided, or watched.</p></div>
-                    <div><span>Checkpoint</span><b>Optional</b><p>The open confirmation or check that creates this risk.</p></div>
-                    <div><span>Responsible person</span><b>Optional</b><p>Who is responsible for watching or handling it.</p></div>
+                    <div><span>Topic</span><b>Required</b><p>The uncertainty or exposure being tracked.</p></div>
+                    <div><span>Risk entries</span><b>Required</b><p>Identification, assessment, treatment, monitoring, closure, and reopening entries kept in order.</p></div>
+                    <div><span>Current status</span><b>Automatic</b><p>Whether the risk is open or closed, derived from the latest status entry.</p></div>
+                    <div><span>Current assessment</span><b>Optional</b><p>The latest likelihood and impact assessment.</p></div>
+                    <div><span>Current treatment</span><b>Optional</b><p>The latest response: accept, mitigate, transfer, or avoid.</p></div>
+                    <div><span>Acceptance boundary</span><b>Required</b><p>Formal risk acceptance belongs to the Owner.</p></div>
                   </div>
                 </details>
               </div>
@@ -193,11 +208,43 @@
                 <details class="record-item">
                   <summary><span class="record-name">Change</span><span class="record-summary">A record for a specific alteration to the running service.</span></summary>
                   <div class="record-fields" aria-label="Change fields">
+                    <div><span>Change type</span><b>Required</b><p>Whether the change is standard, normal, or emergency.</p></div>
                     <div><span>Change plan</span><b>Required</b><p>What is changing, why, scope, timing, and notice.</p></div>
                     <div><span>Execution plan</span><b>Required</b><p>The ordered steps for carrying out the change.</p></div>
                     <div><span>Rollback plan</span><b>Required</b><p>How to reverse or recover if the change should not remain in use.</p></div>
-                    <div><span>Risk and impact</span><b>Required</b><p>The expected risk, service impact, and open concerns.</p></div>
-                    <div><span>Events</span><b>Optional</b><p>Notice, veto, emergency, decision, result, recovery, notes, and revisions kept in order.</p></div>
+                    <div><span>Risk and impact</span><b>Required</b><p>The expected risk, service impact, open concerns, and downstream impact: what else may be affected and what depends on what is changing.</p></div>
+                    <div><span>Events</span><b>Optional</b><p>Notice, veto, decision, result, recovery, notes, and revisions kept in order. Result and recovery events can include optional Git commit references.</p></div>
+                    <div><span>Boundary</span><b>Required</b><p>Use Change for run-side service alteration, not ordinary build work.</p></div>
+                  </div>
+                </details>
+                <details class="record-item">
+                  <summary><span class="record-name">Incident</span><span class="record-summary">A specific service-impacting or potentially service-impacting occurrence.</span></summary>
+                  <div class="record-fields" aria-label="Incident fields">
+                    <div><span>Description</span><b>Required</b><p>What happened or may be happening.</p></div>
+                    <div><span>Incident entries</span><b>Required</b><p>Detection, updates, severity changes, resolution, reopening, and notes kept in order.</p></div>
+                    <div><span>Current status</span><b>Automatic</b><p>Whether the Incident is open or resolved, derived from entries.</p></div>
+                    <div><span>Current severity</span><b>Optional</b><p>The latest recorded severity.</p></div>
+                    <div><span>Affected Components</span><b>Optional</b><p>The operational items affected by the occurrence.</p></div>
+                  </div>
+                </details>
+                <details class="record-item">
+                  <summary><span class="record-name">Problem</span><span class="record-summary">An underlying or recurring cause evidenced by one or more Incidents.</span></summary>
+                  <div class="record-fields" aria-label="Problem fields">
+                    <div><span>Description</span><b>Required</b><p>The cause or pattern being investigated.</p></div>
+                    <div><span>Related Incidents</span><b>Required</b><p>The Incidents that provide evidence for the Problem.</p></div>
+                    <div><span>Problem entries</span><b>Required</b><p>Identification, investigation, root cause, known error, resolution, reopening, and notes kept in order.</p></div>
+                    <div><span>Current status</span><b>Automatic</b><p>The latest Problem state derived from entries.</p></div>
+                    <div><span>Current root cause</span><b>Optional</b><p>The latest recorded root cause.</p></div>
+                  </div>
+                </details>
+                <details class="record-item">
+                  <summary><span class="record-name">Support Request</span><span class="record-summary">A shared support record for a user-facing question, request, or issue.</span></summary>
+                  <div class="record-fields" aria-label="Support Request fields">
+                    <div><span>Reporter</span><b>Required</b><p>The person, role, or channel that reported the experience.</p></div>
+                    <div><span>Reported experience</span><b>Required</b><p>What the user reported, requested, asked, or experienced.</p></div>
+                    <div><span>Support entries</span><b>Required</b><p>Raised, triage, update, escalation, resolution, reopening, and notes kept in order.</p></div>
+                    <div><span>Current status</span><b>Automatic</b><p>The latest support state derived from entries.</p></div>
+                    <div><span>Escalated Incident</span><b>Optional</b><p>An Incident linked when the support request becomes an operational occurrence.</p></div>
                   </div>
                 </details>
               </div>
@@ -227,6 +274,16 @@
                     <div><span>Version history</span><b>Automatic</b><p>Prior versions are kept when the Component changes.</p></div>
                   </div>
                 </details>
+                <details class="record-item">
+                  <summary><span class="record-name">Maintenance Schedule</span><span class="record-summary">Recurring operational hygiene with cadence and due state.</span></summary>
+                  <div class="record-fields" aria-label="Maintenance Schedule fields">
+                    <div><span>Name and kind</span><b>Required</b><p>What recurring operational duty this schedule represents.</p></div>
+                    <div><span>Cadence</span><b>Required</b><p>How often the work should happen.</p></div>
+                    <div><span>Start date</span><b>Required</b><p>The first date used to calculate when the work is due.</p></div>
+                    <div><span>Due state</span><b>Automatic</b><p>Next due date and overdue state are derived from cadence and linked completed Changes or Tasks.</p></div>
+                    <div><span>Version history</span><b>Automatic</b><p>Prior versions are kept when the schedule changes.</p></div>
+                  </div>
+                </details>
               </div>
               <p>
                 The Operational Registry is inventory only. It does not monitor, diagnose, store secret values, keep event history, or replace operating procedures.
@@ -272,7 +329,7 @@
                     <div><span>Constraints, dependencies, and unknowns</span><b>Concept</b><p>These are normally captured in requirements, risks, decisions, review notes, or task details.</p></div>
                     <div><span>Verification and validation</span><b>Concept</b><p>Checks and outcomes can be captured in task details, change history, decisions, or linked notes.</p></div>
                     <div><span>Release, deployment, controls, and evidence</span><b>Concept</b><p>These are currently represented through Change events, risks, decisions, and supporting notes.</p></div>
-                    <div><span>Support, incidents, problems, and feedback</span><b>Concept</b><p>Operational signals can be handled through tickets, risks, tasks, changes, decisions, or new requirements.</p></div>
+                    <div><span>Support, incidents, problems, and feedback</span><b>Concept</b><p>Operational signals can be handled through tickets, incidents, problems, risks, tasks, changes, decisions, or new requirements.</p></div>
                     <div><span>Measurement and estimate refinement</span><b>Concept</b><p>Actual cost or benefit observations can update estimates, benefits, risks, decisions, or future work.</p></div>
                   </div>
                 </div>

package/website/operating-guide.html

@@ -0,0 +1,165 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1" />
+    <title>Operating Guide | DX Complete</title>
+    <link rel="stylesheet" href="./styles.css?v=5" />
+  </head>
+  <body>
+    <a class="skip-link" href="#content">Skip to content</a>
+    <header class="topbar">
+      <div class="topbar__brand">
+        <span class="brand-mark" aria-hidden="true">DX</span>
+        <span><strong>DX Complete</strong><small>Plan, deliver, run, measure</small></span>
+      </div>
+    </header>
+    <div class="layout">
+      <aside class="sidebar" aria-label="Documentation pages">
+        <div class="sidebar__eyebrow">Pages</div>
+        <nav>
+          <a class="nav-link" href="./index.html">Start here</a>
+          <a class="nav-link" href="./outcomes.html">Outcomes</a>
+          <a class="nav-link" href="./flow.html">Flow</a>
+          <a class="nav-link" href="./objects.html">Records</a>
+          <a class="nav-link" href="./roles.html">Roles</a>
+          <a class="nav-link" href="./operating-guide.html">Operating Guide</a>
+          <a class="nav-link" href="./glossary.html">Glossary</a>
+        </nav>
+      </aside>
+      <main id="content" class="content" tabindex="-1">
+        <section class="doc-section doc-section--last">
+          <p class="section-kicker">Operating guide</p>
+          <h1>How roles use DX Complete</h1>
+          <p class="lede">
+            DX Complete is easiest to use when each person knows which records belong to their part of the work.
+          </p>
+          <p>
+            This guide shows the normal record choices by role. It is not meant to make every activity heavier. Use the smallest record that keeps the work understandable.
+          </p>
+
+          <section class="record-groups" aria-label="Role operating guidance">
+            <section>
+              <span>Owner</span>
+              <h2>Direction, value, and authority</h2>
+              <p>
+                The Owner sets direction, weighs value against cost and risk, records Commitment or Deferral, validates outcomes, and formally accepts risk when the project should own it.
+              </p>
+              <div class="record-fields" aria-label="Owner record use">
+                <div><span>Usually uses</span><b>Records</b><p>Statement, Expectation, Benefits, Value Realization, Commitment, Deferral, Decision, and Risk.</p></div>
+                <div><span>Watch for</span><b>Boundary</b><p>Do not turn every comment into a requirement. Do not use approval language for End User feedback.</p></div>
+              </div>
+            </section>
+
+            <section>
+              <span>Engineer and Codex assistance</span>
+              <h2>Build from requirements</h2>
+              <p>
+                The Engineer turns committed requirements into tasks and working changes. Coding-capable tools such as Codex may assist the Engineer, but they are not separate DX Complete roles.
+              </p>
+              <div class="record-fields" aria-label="Engineer record use">
+                <div><span>Default path</span><b>Task</b><p>Use Requirement to Task for normal build work.</p></div>
+                <div><span>When needed</span><b>Decision</b><p>Use Decision for meaningful design choices or tradeoffs.</p></div>
+                <div><span>When exposed</span><b>Risk</b><p>Use Risk when uncertainty could affect value, delivery, service, or compliance.</p></div>
+                <div><span>When running service changes</span><b>Change</b><p>Use Change only when the work becomes a discrete alteration to the running service.</p></div>
+              </div>
+            </section>
+
+            <section>
+              <span>Tester</span>
+              <h2>Verification evidence</h2>
+              <p>
+                The Tester checks completed work against requirements and success criteria, then keeps the evidence visible in the record that best matches what was learned.
+              </p>
+              <div class="record-fields" aria-label="Tester record use">
+                <div><span>Normal evidence</span><b>Task</b><p>Use Task entries for verification notes tied to build work.</p></div>
+                <div><span>Requirement feedback</span><b>Review note</b><p>Use review notes when the check reveals useful input on a requirement.</p></div>
+                <div><span>Uncertainty</span><b>Risk</b><p>Use Risk when a test result exposes uncertainty or possible harm.</p></div>
+                <div><span>Boundary</span><b>No default Change</b><p>Do not create a Change record merely because testing is happening.</p></div>
+              </div>
+            </section>
+
+            <section>
+              <span>Operator and administration</span>
+              <h2>Run the service safely</h2>
+              <p>
+                The Operator manages run-side change, incidents, problems, operational inventory, rollout and rollback planning, monitoring, users, permissions, settings, provisioning, and run-side security.
+              </p>
+              <div class="record-fields" aria-label="Operator record use">
+                <div><span>Service change</span><b>Change</b><p>Use Change for a discrete alteration to the running service, with execution and rollback plans.</p></div>
+                <div><span>Service occurrence</span><b>Incident</b><p>Use Incident for a specific service-impacting or potentially service-impacting occurrence.</p></div>
+                <div><span>Underlying cause</span><b>Problem</b><p>Use Problem for an underlying or recurring cause evidenced by incidents.</p></div>
+                <div><span>Inventory</span><b>Environment</b><p>Use Environment for named operating contexts such as local, staging, or production.</p></div>
+                <div><span>Inventory detail</span><b>Component</b><p>Use Component for environment-specific apps, databases, queues, storage, external services, and other operational items.</p></div>
+                <div><span>Recurring hygiene</span><b>Maintenance Schedule</b><p>Use Maintenance Schedule for recurring checks, reviews, rotations, or maintenance duties.</p></div>
+                <div><span>Boundary</span><b>Secrets</b><p>Record where secrets are stored and what they are called, not the secret values.</p></div>
+              </div>
+            </section>
+
+            <section>
+              <span>Support Agent</span>
+              <h2>Route user signals</h2>
+              <p>
+                The Support Agent helps users, captures questions and reports, and routes signals into shared follow-up only when a shared record is needed.
+              </p>
+              <div class="record-fields" aria-label="Support Agent record use">
+                <div><span>Shared follow-up</span><b>Support Request</b><p>Use Support Request for a user-facing question, report, request, or issue that needs shared follow-up.</p></div>
+                <div><span>Private DX Complete contact</span><b>DX Complete Ticket</b><p>Use DX Complete Ticket for private questions, reports, requests, corrections, or follow-ups with DX Complete itself.</p></div>
+                <div><span>Promote when needed</span><b>Records</b><p>Promote to Statement, Requirement, Task, Incident, Problem, Risk, Decision, Change, or Journal only when the signal has that meaning.</p></div>
+                <div><span>Boundary</span><b>Restraint</b><p>Do not create process records just because a user said something. Create them when the signal has work, risk, decision, or service-control meaning.</p></div>
+              </div>
+            </section>
+
+            <section>
+              <span>End User</span>
+              <h2>Input, not operation</h2>
+              <p>
+                The End User uses the service and provides requests, feedback, corrections, and issue reports. Another role captures that input when it belongs in DX Complete.
+              </p>
+              <div class="record-fields" aria-label="End User record boundary">
+                <div><span>Input becomes</span><b>Signal</b><p>Statement, report, request, correction, feedback signal, or ticket.</p></div>
+                <div><span>Boundary</span><b>No approval</b><p>End User feedback is not authority approval unless that person is also acting in an authority role.</p></div>
+              </div>
+            </section>
+          </section>
+
+          <section class="record-groups" aria-label="Record routing">
+            <section>
+              <span>Routing</span>
+              <h2>Choosing the right record</h2>
+              <div class="record-fields" aria-label="Record routing by situation">
+                <div><span>Normal build work</span><b>Task</b><p>Use Task for concrete work someone needs to do.</p></div>
+                <div><span>Meaningful choice</span><b>Decision</b><p>Use Decision when alternatives were considered and the choice should remain legible.</p></div>
+                <div><span>Uncertainty or exposure</span><b>Risk</b><p>Use Risk when something uncertain could affect value, delivery, service, or compliance.</p></div>
+                <div><span>Run-side alteration</span><b>Change</b><p>Use Change for a discrete alteration to the running service.</p></div>
+                <div><span>Service occurrence</span><b>Incident</b><p>Use Incident for a specific service-impacting occurrence that needs response history.</p></div>
+                <div><span>Underlying cause</span><b>Problem</b><p>Use Problem when one or more incidents point to a deeper or recurring cause.</p></div>
+                <div><span>User support follow-up</span><b>Support Request</b><p>Use Support Request for a shared user-facing support thread.</p></div>
+                <div><span>Operational inventory</span><b>Registry</b><p>Use Environment and Component for what exists, where it lives, and which secret locations matter.</p></div>
+                <div><span>Recurring operations</span><b>Maintenance Schedule</b><p>Use Maintenance Schedule for recurring service hygiene.</p></div>
+                <div><span>Measured value</span><b>Value Realization</b><p>Use Value Realization for before-and-after metrics tied to expectations, requirements, or commitments.</p></div>
+                <div><span>Useful context</span><b>Journal</b><p>Use Journal only when the context has no better dedicated record home.</p></div>
+                <div><span>Private DX Complete contact</span><b>Ticket</b><p>Use DX Complete Ticket for private communication with DX Complete.</p></div>
+              </div>
+              <p>
+                The simplest test is: will anything reference or depend on this? If yes, use the dedicated record that can carry that relationship.
+              </p>
+            </section>
+
+            <section>
+              <span>ITSM boundary</span>
+              <h2>Use service records only when they fit</h2>
+              <p>
+                Change is the current first-class run-side control record. Use it for a specific alteration to the running service, with a change type, plan, execution path, rollback path, risk, and event history.
+              </p>
+              <p>
+                Incident is for a specific service-impacting or potentially service-impacting occurrence. Problem is for an underlying or recurring cause evidenced by incidents. Do not create service-control records merely because work is happening; use them when the service-control meaning fits.
+              </p>
+            </section>
+          </section>
+        </section>
+      </main>
+    </div>
+    <script src="./app.js?v=5"></script>
+  </body>
+</html>

package/website/outcomes.html

@@ -23,6 +23,7 @@
           <a class="nav-link" href="./flow.html">Flow</a>
           <a class="nav-link" href="./objects.html">Records</a>
           <a class="nav-link" href="./roles.html">Roles</a>
+          <a class="nav-link" href="./operating-guide.html">Operating Guide</a>
           <a class="nav-link" href="./glossary.html">Glossary</a>
         </nav>
       </aside>

package/website/phase-build.html

@@ -23,6 +23,7 @@
           <a class="nav-link" href="./flow.html">Flow</a>
           <a class="nav-link" href="./objects.html">Records</a>
           <a class="nav-link" href="./roles.html">Roles</a>
+          <a class="nav-link" href="./operating-guide.html">Operating Guide</a>
           <a class="nav-link" href="./glossary.html">Glossary</a>
         </nav>
       </aside>

package/website/phase-elicit.html

@@ -23,6 +23,7 @@
           <a class="nav-link" href="./flow.html">Flow</a>
           <a class="nav-link" href="./objects.html">Records</a>
           <a class="nav-link" href="./roles.html">Roles</a>
+          <a class="nav-link" href="./operating-guide.html">Operating Guide</a>
           <a class="nav-link" href="./glossary.html">Glossary</a>
         </nav>
       </aside>

package/website/phase-go-live.html

@@ -23,6 +23,7 @@
           <a class="nav-link" href="./flow.html">Flow</a>
           <a class="nav-link" href="./objects.html">Records</a>
           <a class="nav-link" href="./roles.html">Roles</a>
+          <a class="nav-link" href="./operating-guide.html">Operating Guide</a>
           <a class="nav-link" href="./glossary.html">Glossary</a>
         </nav>
       </aside>
@@ -80,7 +81,7 @@
               <ul>
                 <li>Are readiness checks complete?</li>
                 <li>Has notice been given, and is any veto recorded?</li>
-                <li>If this is an emergency, are both importance and immediacy clear?</li>
+                <li>If the change type is emergency, are importance and immediacy clear?</li>
                 <li>Is any open risk visible or formally accepted by the Owner?</li>
                 <li>Should the change proceed, be deferred, be cancelled, or need recovery?</li>
               </ul>

package/website/phase-measure.html

@@ -23,6 +23,7 @@
           <a class="nav-link" href="./flow.html">Flow</a>
           <a class="nav-link" href="./objects.html">Records</a>
           <a class="nav-link" href="./roles.html">Roles</a>
+          <a class="nav-link" href="./operating-guide.html">Operating Guide</a>
           <a class="nav-link" href="./glossary.html">Glossary</a>
         </nav>
       </aside>

package/website/phase-operate.html

@@ -23,6 +23,7 @@
           <a class="nav-link" href="./flow.html">Flow</a>
           <a class="nav-link" href="./objects.html">Records</a>
           <a class="nav-link" href="./roles.html">Roles</a>
+          <a class="nav-link" href="./operating-guide.html">Operating Guide</a>
           <a class="nav-link" href="./glossary.html">Glossary</a>
         </nav>
       </aside>

package/website/phase-orient.html

@@ -23,6 +23,7 @@
           <a class="nav-link" href="./flow.html">Flow</a>
           <a class="nav-link" href="./objects.html">Records</a>
           <a class="nav-link" href="./roles.html">Roles</a>
+          <a class="nav-link" href="./operating-guide.html">Operating Guide</a>
           <a class="nav-link" href="./glossary.html">Glossary</a>
         </nav>
       </aside>

package/website/phase-weigh.html

@@ -23,6 +23,7 @@
           <a class="nav-link" href="./flow.html">Flow</a>
           <a class="nav-link" href="./objects.html">Records</a>
           <a class="nav-link" href="./roles.html">Roles</a>
+          <a class="nav-link" href="./operating-guide.html">Operating Guide</a>
           <a class="nav-link" href="./glossary.html">Glossary</a>
         </nav>
       </aside>

package/website/roles.html

@@ -23,6 +23,7 @@
           <a class="nav-link" href="./flow.html">Flow</a>
           <a class="nav-link" href="./objects.html">Records</a>
           <a class="nav-link" href="./roles.html">Roles</a>
+          <a class="nav-link" href="./operating-guide.html">Operating Guide</a>
           <a class="nav-link" href="./glossary.html">Glossary</a>
         </nav>
       </aside>