Skip to content

Overview

The Software Delivery Profile is an extension of the CDS Core Model for commitments whose execution runtime is software delivery.

CDS Core is universal: it defines how to move from Meaning Discovery → Intent Refinement → Commitment Formalization. The Software Delivery Profile adds the minimum additional structure needed to ensure commitments are executable in real software delivery environments — where constraints surface late, dependencies are indirect, and “delivery” can accidentally become the place where intent is discovered too late.

What this profile is

This profile is:

  • A set of software-specific additions to CDS artifacts (Meaning Handshake, Intent Package, Commitment Envelope).
  • A set of software-specific quality checks (“profile gates”) that prevent predictable delivery failures.
  • A mapping from the Commitment Envelope into a software delivery runtime (e.g., a delivery framework such as 3SF).

It keeps CDS Core intact. It does not introduce a new lifecycle.

Why software delivery needs a profile

Software delivery commitments fail in characteristic ways:

  • Hidden constraints appear late (security, compliance, data, privacy, architecture limits).
  • Dependencies are often indirect (access, environments, other internal teams, procurement workflows).
  • Semantic drift accumulates (business terms evolve while systems fossilize).
  • Evidence is vague (shipping is mistaken for value).
  • Decision rights are unclear (changes become escalation-by-default).
  • Work starts before commitment is real (execution begins with undefined intent).

The Software Delivery Profile pulls these realities upstream so they become part of intent and commitment formation — rather than surprises paid for during execution.

When to use this profile

Use the Software Delivery Profile when:

  • the commitment involves building, changing, integrating, migrating, or operating software systems
  • delivery spans multiple teams, organizations, or vendors
  • constraints and approvals are likely to be significant
  • the work is high-stakes (production risk, compliance risk, reputational risk)
  • you expect uncertainty and change, and need governance that can handle it

You may not need this profile for:

  • low-risk internal tooling
  • small reversible changes with single-team ownership
  • situations where constraints and dependencies are already fully known and stable

Relationship to 3SF (runtime mapping)

The Software Delivery Profile is designed to hand off into a software delivery runtime. If you use 3SF, the mapping is direct:

  • CDS Commitment Envelope becomes a runtime input contract
  • 3SF operates as the execution runtime, maintaining coherence across:
    • Client ↔ Vendor ↔ Product
    • Engagement ↔ Delivery ↔ Value

This profile ensures the Commitment Envelope contains what a delivery runtime actually needs: decision rights, constraints, evidence expectations, dependency obligations, and change protocol — so delivery can execute rather than continuously renegotiate.

What changes vs CDS Core

What stays the same

  • The CDS lifecycle and its three steps
  • The purpose and boundaries of each step
  • The core artifacts (same names, same intent)

What gets extended

  • Meaning Discovery gains software-context fields (dependencies, semantics, operational reality).
  • Intent Refinement gains delivery-grade intent elements (NFRs, reversibility, feasibility probes).
  • Commitment Formalization gains runtime-ready commitment elements (governance, acceptance evidence, operational posture).

What you will find in this section

This section is structured as extensions to the CDS lifecycle:

  • Meaning Discovery (Software Delivery additions)
  • Intent Refinement (Software Delivery additions)
  • Commitment Formalization (Software Delivery additions)

Each profile page includes:

  • software-specific purpose and focus
  • additions to the core artifact schema
  • profile-specific quality checks
  • common failure patterns and recovery moves

How to apply the profile

Start with CDS Core pages. Then apply this profile as a lens:

  1. Run Meaning Discovery and produce a Meaning Handshake.
  2. Apply the Software Delivery additions to capture delivery-relevant reality.
  3. Run Intent Refinement and produce an Intent Package.
  4. Apply the Software Delivery additions to make intent delivery-grade.
  5. Run Commitment Formalization and produce a Commitment Envelope.
  6. Apply the Software Delivery additions so the envelope is runtime-ready.
  7. Hand off the Commitment Envelope into your delivery runtime (e.g., 3SF).