TeamBrain Standard Artifact

TeamBrain Standard Artifact

Delivery Context Markdown (DCM)

One file. One source of truth. Zero drift.

1️⃣ What this artifact is

The Delivery Context Markdown (DCM) is the primary onboarding, execution, and reasoning artifact for a project.

It replaces:

• slide decks

• scattered documents

• tribal knowledge

• oral handoffs

The DCM is readable by humans and executable by AI.

2️⃣ What problem it solves

Enterprise teams fail most often because of:

• missing context

• unclear constraints

• misaligned assumptions

• slow onboarding

The DCM eliminates this by:

• bounding reasoning

• stabilizing decision-making

• accelerating time-to-productivity

3️⃣ Who produces it (non-negotiable)

The Sales Engineer / Engagement Lead must deliver this artifact.

If this artifact does not exist:

• onboarding is incomplete

• delivery risk is elevated

• assumptions are undocumented

No DCM → no “ready to start” project.

4️⃣ When it is created

• Before architect onboarding

• Before sprint zero

• Before any implementation decisions

It is refined over time, but never replaced.

5️⃣ What it explicitly contains (required sections)

1. Project Identity

• Project name

• Client / domain

• Business goal (plain English)

• Success definition

2. Delivery Posture (The Bounding Box)

• Delivery model (e.g., Wipro / Accenture-style)

• Constraints (security, access, timeline)

• Known non-goals

• Organizational realities

This section prevents solution drift.

3. Timeline & Pressure Points

• Key milestones

• Fixed deadlines

• External dependencies

• Risk windows

4. Team Reality

• Skill assumptions (new hires vs experts)

• Access limitations

• Tooling constraints

• Approval chains

5. Architecture Guardrails

• Approved technologies

• Forbidden approaches

• Known legacy constraints

• Cloud / infra posture

6. Execution Expectations

• Definition of “done”

• Quality bars

• Non-functional expectations

• Operational ownership

7. Open Questions (Tracked, Not Hidden)

• Known unknowns

• Pending decisions

• Assumptions requiring validation

6️⃣ How TeamBrain uses this artifact

TeamBrain treats the DCM as:

• Identity anchor (who is reasoning)

• Context boundary (what is allowed)

• Constraint validator (what must not be violated)

Every response is evaluated against this artifact.

7️⃣ Why this beats PowerPoint & Excel

Traditional Artifacts

Delivery Context Markdown

Static

Living

Presentation-oriented

Execution-oriented

Human-only

Human + AI

Drifts over time

Self-correcting

Requires meetings

Enables autonomy

8️⃣ The 10-Day Productivity Guarantee

A valid DCM must allow:

• a new engineer

• with no tribal knowledge

• to deliver meaningful work

• within 10 days

If it cannot do this, the artifact is incomplete.

9️⃣ Ownership & Governance

• Owned by: Delivery Lead / Architect

• Updated by: Team, via pull requests

• Versioned in: Source control

• Referenced in: All major decisions

10️⃣ The rule (this is the hard line)

If it’s not in the Delivery Context Markdown, it’s not real.

11️⃣ Why this matters (final note)

This artifact:

• scales judgment

• preserves intent

• reduces dependency on heroes

• turns onboarding into execution

It is the cognitive foundation of TeamBrain.