For use possibly with ongoing revisions.

Section purpose definitions — Abstract and Introduction

Drafted: 2026-05-13 Method: Mark's "define the section first, then make the content fit" applied to the Abstract and all Introduction subsections.

Each definition has three parts: a one-line purpose statement, the scope of what belongs in the section, and an explicit notes on what does not belong (so content has a clear home and overlaps are visible).

The heading for §1.1 is left as an open question — "About" matches W3C convention, "Understanding" matches Janina's framing in the meeting and Jeff's Notion comment. The purpose is the same either way; the choice is editorial.

“Status of This Document” is omitted from this exercise — it is standard W3C template content (process stage, working group, patent policy, comment deadlines) filled with specifics. It carries its own conventions and isn't being considered within this revision.

Abstract

Purpose. Summarizes the document — what the AMM is, what it does at a high level, how it's organized, and what the reader will find inside. Reader-facing scope statement, document-focused per Mark's Abstract/About chart.

Scope.

• A one- to two-sentence statement of what the AMM is and what it measures (the "what" of the document).
• A brief, non-enumerated mention of how the model is organized — seven dimensions, four maturity levels — without listing the dimension or level names.
• A short note on how the framework operates at a high level (evaluation of current capabilities, identification of gaps, planning for improvement).
• A line on scalability and adaptability — that it applies to organizations of any size and may be tailored to industry and operational context, with adaptable and extensible dimensions and proof points.
• A closing line on what the document contains (dimensions, levels, sample proof points, the experimental assessment spreadsheet).

Out of scope.

• The “what’s in it for me” (WIIFM) beat — what an organization gains from maturity assessment beyond conformance. That's §1.1 About-territory.
• The conformance-vs-maturity contrast — also §1.1 About-territory. This avoids looking at what the AMM is not
• Enumeration of dimension names or level names — those are §2 territory.
• How to actually run an assessment (workflow, steps) — that's §1.2 How to Use.