> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://tieback.io/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tieback.io/docs/_mcp/server.

# Foundations: Completion

> The completion page for the free tieback Academy DPP Foundations path: what the six modules covered, what they deliberately left out, and where to go next.

## What You Have Completed

DPP Foundations took you from no assumed knowledge of Digital Product Passports to a defensible
first position on one product. Module 1 established the definition and the four layers. Module 2
placed your organisation in the value chain and named which duties attach to which role. Module 3
covered what a passport has to contain and who owns which attribute. Module 4 covered how a
passport actually works once it exists: identifiers, carriers, resolution and persistence. Module 5
covered how a delegated act turns a framework obligation into a specific one, and what to do while
the detail is still unwritten. Module 6 put all five to work on a single product and produced a
readiness position, a sequence of first actions, and a five sentence brief.

This is a course completion, not a professional certification. It confirms you have done the work
in six modules, not that you hold a qualification.

## What You Can Now Do

* Define a Digital Product Passport accurately and tell it apart from a label, a QR campaign, a page or a PDF.
* Decide whether and where your organisation carries a duty, without guessing at scope.
* Say what a passport has to contain and which attributes in your organisation currently have no owner.
* Explain how a passport works in practice, from data carrier to resolved record, and why persistence matters after a sale.
* Read regulatory timing correctly and separate what is already settled from what is still pending detail.
* Produce a first readiness position for one product, sequence your first three actions, and brief a decision maker on it in five sentences.

## What Foundations Did Not Cover

Foundations is deliberately narrow. It did not cover field level schema work: mapping your own data
to a fixed attribute list is product group specific and was left for later paths. It did not cover
vendor implementation: choosing or configuring any particular platform. It did not cover the detail
of supplier contracting: what clauses to put in an agreement, as opposed to when to approach a
supplier and with what kind of request. And it did not cover audit or enforcement practice: how a
market authority actually checks a passport once one exists. All four are real, substantial bodies
of work, and none of them can be done honestly before the readiness work this path covers.

## Where To Go Next

The [Knowledge Base](/docs/knowledge-base/digital-product-passports/overview) is where the
canonical articles behind every Foundations module live, and it goes considerably further than the
Academy lessons drawn from it. The [framework registry](/docs/knowledge-base/frameworks/overview)
lists every tieback framework used across the path, including the two used in this module, with
full descriptions. Later Academy paths build directly on Foundations: they assume you can already
define a passport, place your organisation in the value chain, and state a readiness position, and
they take each of the four gaps named above further than this path does.

## Related Docs

* [DPP Foundations](/docs/academy/foundations)
* [Module 6 overview](/docs/academy/foundations/module-6)
* [Digital Product Passports](/docs/knowledge-base/digital-product-passports/overview)
* [tieback Frameworks](/docs/knowledge-base/frameworks/overview)