npm - dxcomplete - Versions diffs - 0.1.0 - Mend

dxcomplete 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (121) hide show

package/.env.example +11 -0
package/README.md +215 -0
package/dist/cli.d.ts +2 -0
package/dist/cli.js +212 -0
package/dist/http/server.d.ts +7 -0
package/dist/http/server.js +236 -0
package/dist/http/service.d.ts +7 -0
package/dist/http/service.js +725 -0
package/dist/init.d.ts +13 -0
package/dist/init.js +128 -0
package/dist/install-manifest.d.ts +25 -0
package/dist/install-manifest.js +96 -0
package/dist/mcp/docs.d.ts +98 -0
package/dist/mcp/docs.js +438 -0
package/dist/mcp/server.d.ts +20 -0
package/dist/mcp/server.js +2345 -0
package/dist/package-root.d.ts +2 -0
package/dist/package-root.js +28 -0
package/dist/runtime/actor.d.ts +14 -0
package/dist/runtime/actor.js +42 -0
package/dist/runtime/auth.d.ts +162 -0
package/dist/runtime/auth.js +394 -0
package/dist/runtime/check.d.ts +7 -0
package/dist/runtime/check.js +16 -0
package/dist/runtime/config.d.ts +17 -0
package/dist/runtime/config.js +93 -0
package/dist/runtime/mongo.d.ts +9 -0
package/dist/runtime/mongo.js +56 -0
package/dist/runtime/records.d.ts +336 -0
package/dist/runtime/records.js +1463 -0
package/dist/runtime/workspace.d.ts +19 -0
package/dist/runtime/workspace.js +102 -0
package/dist/upgrade.d.ts +20 -0
package/dist/upgrade.js +246 -0
package/dist/validate.d.ts +10 -0
package/dist/validate.js +119 -0
package/dist/version.d.ts +3 -0
package/dist/version.js +12 -0
package/docs/codex-integration.md +29 -0
package/docs/cost-model.md +61 -0
package/docs/decision-basis.md +57 -0
package/docs/diagrams.md +31 -0
package/docs/glossary.md +147 -0
package/docs/index.md +60 -0
package/docs/model.md +110 -0
package/docs/open-questions.md +61 -0
package/docs/roles.md +42 -0
package/docs/taxonomy.md +96 -0
package/docs/workflows.md +60 -0
package/package.json +62 -0
package/scripts/check-env-surface.mjs +136 -0
package/scripts/check-public-copy.mjs +263 -0
package/scripts/check-service-boundary.mjs +63 -0
package/scripts/dogfood-work-order.mjs +506 -0
package/scripts/smoke-mcp-http.mjs +3572 -0
package/src/cli.ts +268 -0
package/src/http/server.ts +314 -0
package/src/http/service.ts +934 -0
package/src/init.ts +227 -0
package/src/install-manifest.ts +144 -0
package/src/mcp/docs.ts +557 -0
package/src/mcp/server.ts +3525 -0
package/src/package-root.ts +31 -0
package/src/runtime/actor.ts +61 -0
package/src/runtime/auth.ts +673 -0
package/src/runtime/check.ts +18 -0
package/src/runtime/config.ts +128 -0
package/src/runtime/mongo.ts +89 -0
package/src/runtime/records.ts +2303 -0
package/src/runtime/workspace.ts +155 -0
package/src/upgrade.ts +356 -0
package/src/validate.ts +139 -0
package/src/version.ts +16 -0
package/templates/github/workflows/dxcomplete.yml +16 -0
package/templates/next/pages/api/auth/callback/google.js +12 -0
package/templates/next/pages/api/dxcomplete/[...path].js +12 -0
package/templates/next/pages/api/dxcomplete.js +12 -0
package/templates/next/pages/api/mcp.js +12 -0
package/templates/next/vercel.json +18 -0
package/templates/process/README.md +38 -0
package/templates/process/controls.yml +113 -0
package/templates/process/cost-model.yml +71 -0
package/templates/process/decision-basis.yml +53 -0
package/templates/process/decisions/.gitkeep +1 -0
package/templates/process/diagrams/00-decision-basis.mmd +24 -0
package/templates/process/diagrams/00-overview.mmd +20 -0
package/templates/process/diagrams/01-intake-triage.mmd +20 -0
package/templates/process/diagrams/02-product-definition.mmd +14 -0
package/templates/process/diagrams/03-engineering-execution.mmd +15 -0
package/templates/process/diagrams/04-qa-verification.mmd +12 -0
package/templates/process/diagrams/05-product-validation.mmd +12 -0
package/templates/process/diagrams/06-change-release-control.mmd +16 -0
package/templates/process/diagrams/07-deployment-operations.mmd +16 -0
package/templates/process/diagrams/08-support-incident-management.mmd +16 -0
package/templates/process/diagrams/09-problem-improvement.mmd +14 -0
package/templates/process/diagrams/10-risk-control-management.mmd +14 -0
package/templates/process/diagrams/11-audit-evidence-capture.mmd +13 -0
package/templates/process/evidence/.gitkeep +1 -0
package/templates/process/risks/.gitkeep +1 -0
package/templates/process/roles.yml +96 -0
package/templates/process/taxonomy.yml +514 -0
package/templates/process/workflows.yml +210 -0
package/website/.well-known/oauth-authorization-server +22 -0
package/website/.well-known/oauth-protected-resource/api/dxcomplete/mcp +10 -0
package/website/.well-known/oauth-protected-resource/api/mcp +10 -0
package/website/README.md +12 -0
package/website/app.js +36 -0
package/website/flow.html +85 -0
package/website/glossary.html +280 -0
package/website/index.html +90 -0
package/website/objects.html +287 -0
package/website/outcomes.html +117 -0
package/website/phase-build.html +101 -0
package/website/phase-elicit.html +102 -0
package/website/phase-go-live.html +103 -0
package/website/phase-measure.html +93 -0
package/website/phase-operate.html +102 -0
package/website/phase-orient.html +92 -0
package/website/phase-weigh.html +98 -0
package/website/roles.html +52 -0
package/website/styles.css +1169 -0

package/website/objects.html ADDED Viewed

@@ -0,0 +1,287 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1" />
+    <title>Records | 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="./glossary.html">Glossary</a>
+        </nav>
+      </aside>
+      <main id="content" class="content" tabindex="-1">
+        <section class="doc-section doc-section--last">
+          <p class="section-kicker">Records</p>
+          <h1>Records</h1>
+          <p class="lede">Records are information DX Complete keeps so decisions, work, service issues, and measurements can be followed over time.</p>
+          <p>
+            Records are grouped by how they are usually used. Some records, especially Task and Decision, can appear in any phase when they help keep the work clear.
+          </p>
+          <p>
+            Shared records also have a short reference such as <strong>REQ-0001</strong>, so people can refer to them without reading the full system ID.
+          </p>
+          <section class="record-routing" aria-labelledby="record-routing-title">
+            <h2 id="record-routing-title">Choosing the right record</h2>
+            <p>
+              Use the clearest dedicated record first. Journal is for useful context only when the information has no better home.
+            </p>
+            <div class="record-fields" aria-label="Record routing guidance">
+              <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>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>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>
+              The simplest test is: will another record depend on this, satisfy it, or use it as an input? If yes, choose a dedicated record. If a Journal note later becomes important to decisions or work, promote it to the right record.
+            </p>
+          </section>
+          <div class="record-groups" aria-label="Records by use">
+            <section>
+              <span>Scope</span>
+              <h2>Set the need</h2>
+              <div class="record-list">
+                <details class="record-item">
+                  <summary><span class="record-name">Workspace</span><span class="record-summary">The container for one service and the work connected to it.</span></summary>
+                  <div class="record-fields" aria-label="Workspace fields">
+                    <div><span>Workspace name</span><b>Required</b><p>The name people use for this service space.</p></div>
+                    <div><span>Service scope</span><b>Required</b><p>What service or area the workspace contains.</p></div>
+                    <div><span>Mode</span><b>Optional</b><p>Whether the work is transformation, greenfield, limited disclosure, or mixed.</p></div>
+                    <div><span>Status</span><b>Optional</b><p>Whether the workspace is active, paused, closed, or being reviewed.</p></div>
+                    <div><span>Related workspaces</span><b>Optional</b><p>Other service spaces connected to this one.</p></div>
+                  </div>
+                </details>
+                <details class="record-item">
+                  <summary><span class="record-name">Statement</span><span class="record-summary">A person's own words before they are interpreted or translated.</span></summary>
+                  <div class="record-fields" aria-label="Statement fields">
+                    <div><span>Original words</span><b>Required</b><p>The request, concern, idea, direction, objection, or observation as expressed.</p></div>
+                    <div><span>Source</span><b>Required</b><p>Who or what the statement came from.</p></div>
+                    <div><span>Context</span><b>Optional</b><p>Where it came up and what was happening around it.</p></div>
+                    <div><span>Related expectation</span><b>Optional</b><p>The expectation restated from this statement.</p></div>
+                  </div>
+                </details>
+                <details class="record-item">
+                  <summary><span class="record-name">Journal</span><span class="record-summary">Shared workspace notes for useful context that has no dedicated record home.</span></summary>
+                  <div class="record-fields" aria-label="Journal fields">
+                    <div><span>Note</span><b>Required</b><p>Free-form context, preference, background, observation, or other relevant information.</p></div>
+                    <div><span>Author and time</span><b>Automatic</b><p>Who added the entry and when it was added.</p></div>
+                    <div><span>Label</span><b>Optional</b><p>A short free-form label to help filter or scan entries.</p></div>
+                    <div><span>Summary entry</span><b>Optional</b><p>A compact entry that points back to the notes it summarizes.</p></div>
+                    <div><span>Archive</span><b>Automatic</b><p>Older notes can leave the default view after they are summarized, while still remaining retrievable.</p></div>
+                    <div><span>Related records</span><b>Optional</b><p>Entries can be linked when they inform a decision, risk, requirement, or other record.</p></div>
+                  </div>
+                </details>
+                <details class="record-item">
+                  <summary><span class="record-name">Expectation</span><span class="record-summary">The result a person or group expects, including how success will be recognized.</span></summary>
+                  <div class="record-fields" aria-label="Expectation fields">
+                    <div><span>Expectation</span><b>Required</b><p>The restated result and success condition in plain language.</p></div>
+                    <div><span>Approval state</span><b>Required</b><p>Whether it is not decided yet, approved, not approved, or superseded.</p></div>
+                    <div><span>Approved by</span><b>Optional</b><p>The authority who approved the expectation when approval is needed.</p></div>
+                    <div><span>Review notes</span><b>Optional</b><p>Engineer input that should remain visible without blocking progress.</p></div>
+                    <div><span>Important flag</span><b>Optional</b><p>Highlights a review note without requiring an Owner response.</p></div>
+                    <div><span>Version history</span><b>Optional</b><p>Prior wording kept when the expectation changes.</p></div>
+                    <div><span>Related statement</span><b>Optional</b><p>The original statement that led to this expectation.</p></div>
+                    <div><span>Related requirement</span><b>Optional</b><p>The requirement meant to satisfy this expectation.</p></div>
+                  </div>
+                </details>
+                <details class="record-item">
+                  <summary><span class="record-name">Requirement</span><span class="record-summary">A commitment to make something true in a buildable and checkable way.</span></summary>
+                  <div class="record-fields" aria-label="Requirement fields">
+                    <div><span>Requirement</span><b>Required</b><p>What the team is committing to make true.</p></div>
+                    <div><span>Success criteria</span><b>Required</b><p>How people will know the requirement is satisfied.</p></div>
+                    <div><span>Related expectation</span><b>Optional</b><p>The expectation this requirement is meant to satisfy.</p></div>
+                    <div><span>Requirement detail</span><b>Optional</b><p>Extra behavior, edge cases, or check notes needed to build or verify the requirement.</p></div>
+                    <div><span>Review notes</span><b>Optional</b><p>Engineer input that should remain visible without blocking progress.</p></div>
+                    <div><span>Important flag</span><b>Optional</b><p>Highlights a review note without requiring an Owner response.</p></div>
+                    <div><span>Version history</span><b>Optional</b><p>Prior wording kept when the requirement changes.</p></div>
+                    <div><span>Priority</span><b>Optional</b><p>How important it is compared with other requirements.</p></div>
+                    <div><span>Related records</span><b>Optional</b><p>Links to risks, decisions, costs, benefits, or tasks.</p></div>
+                  </div>
+                </details>
+              </div>
+            </section>
+            <section>
+              <span>Weigh</span>
+              <h2>Decide whether to commit now or defer</h2>
+              <div class="record-list">
+                <details class="record-item">
+                  <summary><span class="record-name">Estimate</span><span class="record-summary">An itemized cost view for the scope being weighed.</span></summary>
+                  <div class="record-fields" aria-label="Estimate fields">
+                    <div><span>Line items</span><b>Required</b><p>The individual cost entries, each with amount, timing, period when recurring, and currency.</p></div>
+                    <div><span>Covered scope</span><b>Required</b><p>The requirements or expectations the Estimate covers.</p></div>
+                    <div><span>Roll-up</span><b>Required</b><p>Grouped cost totals that keep one-time, recurring, period, and currency separate.</p></div>
+                    <div><span>Version history</span><b>Automatic</b><p>Prior versions are kept when the Estimate changes.</p></div>
+                  </div>
+                </details>
+                <details class="record-item">
+                  <summary><span class="record-name">Benefits</span><span class="record-summary">The expected value for the scope being weighed.</span></summary>
+                  <div class="record-fields" aria-label="Benefits fields">
+                    <div><span>Benefit items</span><b>Required</b><p>The expected benefits, with amounts where they can be estimated and plain descriptions where they cannot.</p></div>
+                    <div><span>Covered scope</span><b>Required</b><p>The requirements or expectations the Benefits record covers.</p></div>
+                    <div><span>Roll-up</span><b>Automatic</b><p>Grouped totals for quantified benefits only.</p></div>
+                    <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">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">
+                    <div><span>Commitment</span><b>Required</b><p>What the Owner is committing to move forward.</p></div>
+                    <div><span>Committed items</span><b>Required</b><p>The requirements or expectations included in the Commitment.</p></div>
+                    <div><span>Reservations</span><b>Optional</b><p>Concerns the Owner is moving forward despite.</p></div>
+                    <div><span>Resolved deferral</span><b>Optional</b><p>The earlier Deferral this Commitment resolves.</p></div>
+                  </div>
+                </details>
+                <details class="record-item">
+                  <summary><span class="record-name">Deferral</span><span class="record-summary">An Owner record for not committing yet, with conditions for a future Commitment.</span></summary>
+                  <div class="record-fields" aria-label="Deferral fields">
+                    <div><span>Reason</span><b>Required</b><p>Why the Owner is not committing yet.</p></div>
+                    <div><span>Conditions</span><b>Required</b><p>What must be addressed before a future Commitment.</p></div>
+                    <div><span>Condition history</span><b>Optional</b><p>Notes and updates showing how the conditions changed over time.</p></div>
+                    <div><span>Status</span><b>Required</b><p>Whether the Deferral is open, resolved, or abandoned.</p></div>
+                  </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>
+                  <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>
+                </details>
+              </div>
+            </section>
+            <section>
+              <span>Work</span>
+              <h2>Act on the work</h2>
+              <div class="record-list">
+                <details class="record-item">
+                  <summary><span class="record-name">Task</span><span class="record-summary">Concrete work with an entry history and a current status from the latest status entry.</span></summary>
+                  <div class="record-fields" aria-label="Task fields">
+                    <div><span>Task</span><b>Required</b><p>The work to be done.</p></div>
+                    <div><span>Description</span><b>Required</b><p>The practical explanation of the work.</p></div>
+                    <div><span>Related requirement</span><b>Optional</b><p>The requirement the task supports, when the task implements a requirement.</p></div>
+                    <div><span>Status entries</span><b>Required</b><p>Status changes kept in order. The latest status entry is the current status.</p></div>
+                    <div><span>Assigned person</span><b>Optional</b><p>Who is doing or coordinating the work.</p></div>
+                    <div><span>Task entries</span><b>Optional</b><p>Comments, notes, and status changes that preserve how the task moved over time.</p></div>
+                  </div>
+                </details>
+                <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 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>
+                </details>
+              </div>
+            </section>
+            <section>
+              <span>Operate</span>
+              <h2>Know what exists</h2>
+              <div class="record-list">
+                <details class="record-item">
+                  <summary><span class="record-name">Environment</span><span class="record-summary">A named operating context such as local, staging, or production.</span></summary>
+                  <div class="record-fields" aria-label="Environment fields">
+                    <div><span>Name</span><b>Required</b><p>The name people use for this operating context.</p></div>
+                    <div><span>Description</span><b>Optional</b><p>What the environment is for and how people should understand it.</p></div>
+                    <div><span>Version history</span><b>Automatic</b><p>Prior versions are kept when the Environment changes.</p></div>
+                  </div>
+                </details>
+                <details class="record-item">
+                  <summary><span class="record-name">Component</span><span class="record-summary">One operational item that belongs to one Environment.</span></summary>
+                  <div class="record-fields" aria-label="Component fields">
+                    <div><span>Environment</span><b>Required</b><p>The operating context this Component belongs to.</p></div>
+                    <div><span>Kind</span><b>Required</b><p>A plain label such as app, database, storage, queue, service, or another useful term.</p></div>
+                    <div><span>Location details</span><b>Required</b><p>Where the Component lives, such as a URL, project, region, host, or route.</p></div>
+                    <div><span>Identifiers</span><b>Optional</b><p>Non-secret names such as database name, account, project, region, or username.</p></div>
+                    <div><span>Secret pointers</span><b>Optional</b><p>Where relevant secrets are stored and what they are called. Do not put credential values here.</p></div>
+                    <div><span>Notes</span><b>Optional</b><p>Useful operating context that belongs with this Component.</p></div>
+                    <div><span>Version history</span><b>Automatic</b><p>Prior versions are kept when the Component 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.
+              </p>
+            </section>
+            <section>
+              <span>Throughout</span>
+              <h2>Decide and follow up</h2>
+              <div class="record-list">
+                <details class="record-item">
+                  <summary><span class="record-name">Decision</span><span class="record-summary">A recorded choice with ordered entries and links to the records that informed it.</span></summary>
+                  <div class="record-fields" aria-label="Decision fields">
+                    <div><span>Matter</span><b>Required</b><p>The issue or choice being decided.</p></div>
+                    <div><span>Decision entries</span><b>Optional</b><p>Choices kept in order. The latest decision entry is the current decision.</p></div>
+                    <div><span>Argument entries</span><b>Optional</b><p>Arguments, facts, tradeoffs, or concerns that were visible at the time.</p></div>
+                    <div><span>Note entries</span><b>Optional</b><p>Other context that should remain with the decision.</p></div>
+                    <div><span>Decision inputs</span><b>Optional</b><p>The records that informed the choice.</p></div>
+                    <div><span>Next step</span><b>Optional</b><p>What should happen because of the choice.</p></div>
+                  </div>
+                </details>
+                <details class="record-item">
+                  <summary><span class="record-name">DX Complete Ticket</span><span class="record-summary">A private place to raise a question, report, request, correction, or follow-up with DX Complete.</span></summary>
+                  <div class="record-fields" aria-label="DX Complete Ticket fields">
+                    <div><span>Title</span><b>Required</b><p>A short name for the ticket.</p></div>
+                    <div><span>First entry</span><b>Required</b><p>The original question, report, request, correction, or follow-up.</p></div>
+                    <div><span>Follow-up entries</span><b>Optional</b><p>Later updates added without replacing what was first recorded.</p></div>
+                    <div><span>DX Complete replies</span><b>Optional</b><p>Responses addressed back to the person who raised the ticket.</p></div>
+                    <div><span>Archive</span><b>Optional</b><p>Hide the ticket from the active list when it no longer needs attention.</p></div>
+                    <div><span>Shared work</span><b>Optional</b><p>A requirement, task, risk, change, or decision can be created separately if follow-up is needed.</p></div>
+                    <div><span>Files</span><b>Not included</b><p>Tickets keep text entries; file or asset handling belongs elsewhere.</p></div>
+                  </div>
+                </details>
+              </div>
+            </section>
+            <section>
+              <span>Concepts</span>
+              <h2>Kept inside records</h2>
+              <div class="record-list">
+                <div class="record-item">
+                  <div class="record-fields" aria-label="Concepts kept inside records">
+                    <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>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>
+              </div>
+            </section>
+          </div>
+        </section>
+      </main>
+    </div>
+    <script src="./app.js?v=5"></script>
+  </body>
+</html>

package/website/outcomes.html ADDED Viewed

@@ -0,0 +1,117 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1" />
+    <title>Outcomes | 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="./glossary.html">Glossary</a>
+        </nav>
+      </aside>
+      <main id="content" class="content" tabindex="-1">
+        <section class="doc-section">
+          <p class="section-kicker">Outcomes</p>
+          <h1>Why DX Complete exists</h1>
+          <p class="lede">
+            DX Complete gives teams a shared way to decide what is worth doing, control how it changes, run it safely, and learn from the result.
+          </p>
+          <p>
+            The process is meant to reduce unclear decisions, hidden cost, disconnected handoffs, and unsupported changes.
+          </p>
+        </section>
+        <section class="doc-section">
+          <h2 class="section-heading">What improves</h2>
+          <div class="outcome-grid" aria-label="DX Complete outcomes">
+            <section>
+              <span>01</span>
+              <h3>Consistent operation</h3>
+              <p>Teams use the same phases, records, roles, and handoffs to manage work and service signals.</p>
+            </section>
+            <section>
+              <span>02</span>
+              <h3>Clearer decisions</h3>
+              <p>Goals, requirements, estimates, risks, and decisions stay connected.</p>
+            </section>
+            <section>
+              <span>03</span>
+              <h3>Budget clarity</h3>
+              <p>Current cost is attempted, future cost is estimated, and actual cost is captured when available.</p>
+            </section>
+            <section>
+              <span>04</span>
+              <h3>Controlled change</h3>
+              <p>Expectations, requirements, tasks, checks, releases, and deployments can be followed.</p>
+            </section>
+            <section>
+              <span>05</span>
+              <h3>Review and compliance support</h3>
+              <p>Important decisions, checks, approvals, releases, and measurements have a place to be recorded.</p>
+            </section>
+            <section>
+              <span>06</span>
+              <h3>Measured improvement</h3>
+              <p>Measured results can improve future assumptions about cost, value, risk, and effort.</p>
+            </section>
+          </div>
+        </section>
+        <section class="doc-section">
+          <h2 class="section-heading">Transformation value</h2>
+          <p>
+            Transformation work improves an existing way of operating. DX Complete helps compare the current state with the expected future state, then compare the delivered result when data is available.
+          </p>
+          <p>
+            This can show whether the change reduced cost, reduced effort, reduced risk, increased capacity, or improved service quality.
+          </p>
+          <div class="outcome-compare" aria-label="Transformation comparison">
+            <div>
+              <span>Before</span>
+              <strong>Current cost and friction</strong>
+              <p>What the existing process, service, support load, risk, delay, or manual effort costs today.</p>
+            </div>
+            <div>
+              <span>Planned</span>
+              <strong>Expected cost and value</strong>
+              <p>What the proposed change is expected to cost and what improvement it is expected to create.</p>
+            </div>
+            <div>
+              <span>After</span>
+              <strong>Measured improvement</strong>
+              <p>What changed after launch, including actual cost and benefit when those signals are available.</p>
+            </div>
+          </div>
+        </section>
+        <section class="doc-section doc-section--last">
+          <h2 class="section-heading">What good looks like</h2>
+          <div class="outcome-list" aria-label="Expected results">
+            <div><strong>People know why work is happening.</strong><p>The goal, problem, and requirement set are clear enough to discuss and decide.</p></div>
+            <div><strong>Cost is visible enough to make a responsible choice.</strong><p>Incomplete data is allowed, but unknowns and assumptions are visible.</p></div>
+            <div><strong>Change is traceable from idea to operation.</strong><p>Records show how a request became requirements, tasks, checks, change history, release, deployment, and support history.</p></div>
+            <div><strong>Service learning feeds future work.</strong><p>User support signals, incidents, actual cost, and measured value can improve the next decision.</p></div>
+          </div>
+        </section>
+      </main>
+    </div>
+    <script src="./app.js?v=5"></script>
+  </body>
+</html>

package/website/phase-build.html ADDED Viewed

@@ -0,0 +1,101 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1" />
+    <title>Build | 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="./glossary.html">Glossary</a>
+        </nav>
+      </aside>
+      <main id="content" class="content" tabindex="-1">
+        <section class="doc-section">
+          <p class="section-kicker">Phase 04</p>
+          <h1>Build</h1>
+          <p class="lede">
+            Build turns committed requirements into tasks, working changes, and verification.
+          </p>
+          <p>
+            Read the workflow from top to bottom. Each column shows the role leading that step.
+          </p>
+          <div class="lane-workflow lane-workflow--four" aria-label="Build phase workflow">
+            <div class="lane-head">Owner</div>
+            <div class="lane-head">Engineer</div>
+            <div class="lane-head">Engineer</div>
+            <div class="lane-head">Tester</div>
+            <div class="lane-cell"><div class="work-step">Confirms committed requirements and success criteria.</div></div>
+            <div class="lane-cell"><div class="work-step">Adds requirement detail, breaks work into tasks, and guides the approach.</div></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"><div class="work-step">Builds assigned work.</div></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"><div class="work-step">Checks completed work against requirements.</div></div>
+            <div class="lane-cell"><div class="work-step work-step--choice">Does the result fit the intended outcome?</div></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"><div class="work-step">Fixes gaps when checks do not pass.</div></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"><div class="work-step">Prepares the change for go-live review.</div></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"></div>
+          </div>
+        </section>
+        <section class="doc-section doc-section--last">
+          <div class="phase-summary">
+            <section>
+              <h2>Records</h2>
+              <ul>
+                <li>Requirement</li>
+                <li>Task</li>
+                <li>Decision</li>
+                <li>Risk</li>
+              </ul>
+            </section>
+            <section>
+              <h2>Important choices</h2>
+              <ul>
+                <li>Is the requirement detailed enough to build and check?</li>
+                <li>Does the work meet the requirements?</li>
+                <li>Does the result still fit the intended outcome?</li>
+                <li>Is the change ready for go-live review?</li>
+              </ul>
+            </section>
+            <section>
+              <h2>Handoff</h2>
+              <p>Build ends when the change is ready to be reviewed for Go Live.</p>
+            </section>
+          </div>
+          <div class="phase-nav">
+            <a href="./phase-weigh.html">Previous: Weigh</a>
+            <a href="./flow.html">All phases</a>
+            <a href="./phase-go-live.html">Next: Go Live</a>
+          </div>
+        </section>
+      </main>
+    </div>
+    <script src="./app.js?v=5"></script>
+  </body>
+</html>

package/website/phase-elicit.html ADDED Viewed

@@ -0,0 +1,102 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1" />
+    <title>Elicit | 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="./glossary.html">Glossary</a>
+        </nav>
+      </aside>
+      <main id="content" class="content" tabindex="-1">
+        <section class="doc-section">
+          <p class="section-kicker">Phase 02</p>
+          <h1>Elicit</h1>
+          <p class="lede">
+            Elicit turns expectations into requirements and gathers enough detail to estimate the work.
+          </p>
+          <p>
+            Read the workflow from top to bottom. Each column shows the role leading that step.
+          </p>
+          <div class="lane-workflow lane-workflow--four" aria-label="Elicit phase workflow">
+            <div class="lane-head">End User</div>
+            <div class="lane-head">Owner</div>
+            <div class="lane-head">Engineer</div>
+            <div class="lane-head">Operator / Support Agent</div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"><div class="work-step">Reviews confirmed or open expectations.</div></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"><div class="work-step">Answers questions and confirms what satisfaction would mean.</div></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"><div class="work-step">Drafts requirements from expectations.</div></div>
+            <div class="lane-cell"><div class="work-step">Identifies delivery dependencies, requirement detail, likely constraints, and review notes.</div></div>
+            <div class="lane-cell"><div class="work-step">Adds run, support, access, and readiness concerns.</div></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"><div class="work-step work-step--choice">Enough detail to estimate and commit?</div></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"><div class="work-step">Answers gaps when more detail is needed.</div></div>
+            <div class="lane-cell"><div class="work-step">Prepares the requirement set and visible open risks for Weigh.</div></div>
+            <div class="lane-cell"></div>
+            <div class="lane-cell"></div>
+          </div>
+        </section>
+        <section class="doc-section doc-section--last">
+          <div class="phase-summary">
+            <section>
+              <h2>Records</h2>
+              <ul>
+                <li>Expectation</li>
+                <li>Requirement</li>
+                <li>Risk</li>
+                <li>Decision</li>
+                <li>DX Complete Ticket</li>
+              </ul>
+            </section>
+            <section>
+              <h2>Important choices</h2>
+              <ul>
+                <li>Is enough known to estimate responsibly?</li>
+                <li>Which requirements need more confirmation or review notes?</li>
+                <li>Which unknowns can wait, and which must be answered now?</li>
+                <li>Does the request need to be narrowed before commitment?</li>
+              </ul>
+            </section>
+            <section>
+              <h2>Handoff</h2>
+              <p>Elicit ends when requirements are clear enough to compare cost, value, risk, and confidence, or the open risk is visible.</p>
+            </section>
+          </div>
+          <div class="phase-nav">
+            <a href="./phase-orient.html">Previous: Orient</a>
+            <a href="./flow.html">All phases</a>
+            <a href="./phase-weigh.html">Next: Weigh</a>
+          </div>
+        </section>
+      </main>
+    </div>
+    <script src="./app.js?v=5"></script>
+  </body>
+</html>