About Domain Overviews

Last Updated: October 6, 2026
Contents

Each Network Group is focused on a policy topic area (“Domain”), which is described in a Domain Overview document. Examples of Domains include Artificial Intelligence & Robotics, Government Structure & Processes, Retirement & Aging, and Socio-Economic Levels & Mobility.

This document describes the general policies relating to what a Domain Overview should cover and how it should be structured.

Capitalized terms that this document does not define have the meanings given in the PFN Glossary. See Related Content below.

General Features

A Domain Overview should address what the Domain means, what policy topics are encompassed and what topics are not, what the boundaries are between Domains, and what other key matters are important to defining and understanding the Network Group’s area of substantive focus.

A Domain Overview should also set out the specific policy topics that relate to the Domain and that the Network Group wants to spotlight. PFN expects a Domain to cover roughly 15 to 20 specific policy topics, though some Domains will have fewer and some more. There are many examples of possible topics within the Retirement & Aging Domain, including Social Security, 401(k) plans, pension plans, taxation, retirement income, and retirement expenses.

The Domain Overview should present a Domain’s definition and its policy topics as neutrally as possible. PFN’s recognition of a Domain and its policy topics typically means that some PFN Participants view them as policy matters to be examined. Nevertheless, it is not a signal that PFN believes any policy solutions or directions are needed or desirable. A Network Group will consider possible policy solutions reflecting preferred viewpoints separately and downstream from the Domain Overview.

While most Domains cover a broad general policy area, some may have a narrow focus and stand independent of other Domains. There may be instances when the PFN Leader recognizes a Network Group and Domain on a current legislative or regulatory proposal or on a particular policy vision or solution that a Participant has developed and wants to develop further.

Some Domains may be narrowly defined and positioned as subordinate to other, broader Domains. Consider again Retirement & Aging as a broad Domain with numerous policy topics, including Social Security, and Social Security on its own as a narrower Domain with its own set of more specific policy topics.

The meaning and scope of a particular Domain may substantively overlap with one or more other Domains. One Domain may encompass a policy topic that is contained within, overlaps with, or otherwise relates to another Domain and its topics. Two or more Domains may encompass topics that are the same or substantially the same, and different Network Groups may define the same policy topic in different ways, in the contexts of their different Domains.

The Domain Overview should not present possible policy solutions within the Domain, beyond referring to them when they are inherent to a Domain’s policy topic description. It also should not serve as a prescriptive roadmap for, or a tracking report of, a Network Group’s activities.

The Network Group responsible for a Domain makes its own decisions, in coordination with the PFN Leader and other Network Groups as appropriate, about the definition of the Domain and its policy topics and about the development and upkeep of the Domain Overview. The Network Group Leader and the PFN Leader approve a Domain Overview before it is published or updated.

PFN expects that Network Groups will want to modify their Domain Overview documents as they move forward and their priorities change. When that occurs, PFN issues updated versions. PFN Participants can access all substantively distinct versions of a Network Group’s Domain Overview via the PFN website.

A published Domain Overview is Shared Content under PFN’s content policies, which means its factual claims and citations are verified and its analysis is peer reviewed. It is also published under the PFN Content License, so anyone may republish or adapt it with credit. See About PFN Content and Statement Types and the PFN Content License.

Domain Overview Structure

A Network Group should consider the following sections for its Domain Overview. If a particular section is not appropriate for a particular Domain, that section may be skipped. If a particular Domain Overview calls for an additional section, that section may be added.

Front Matter

Each Network Group’s Domain Overview should begin with an introductory paragraph, without a section heading, that gives a general definition of what the Domain means in plain terms. More specifics should go in the following section.

Meaning and Scope

This section typically includes one to three paragraphs. The first paragraph builds on the front matter by providing more information and detail about what the Domain means, such as the general subject matter, the activities and institutions it involves, and the kinds of questions people raise about it.

The second paragraph, if needed, describes the Domain’s boundaries, to help explain how broadly or narrowly PFN uses the term. This paragraph may include broad exclusions from the Domain. More specific topic exclusions should be noted in the following section.

The third paragraph, if needed, sets out any additional meaning and scope information worth flagging, such as differences, disagreements, or uncertainties.

Topics

This section lists policy topics that many view as contained within, overlapping with, or otherwise relating to the Domain and that are commonly raised in discussions about it or are topics that the Network Group wants to prioritize. The list may include parent topics, sub-topics, adjacent topics, and others. The list should not be exhaustive, and some topics in one Domain may overlap or be shared with other Domains. PFN expects a Domain to encompass roughly 15 to 20 specific policy topics, though some will have fewer and some more.

Each policy topic should be described in one to three neutral, descriptive sentences addressing what the topic means, its scope, why it’s useful, and the range of views people may hold about it. It’s not necessary to provide a lot of detail.

This section closes, if applicable, by noting key topics that may arise in connection with the Domain but are not primarily addressed by this Network Group. Where a policy topic is covered by multiple Domains, the Network Groups responsible should work together to share or allocate responsibilities. If they do not agree, the PFN Leader decides.

Why It Matters

This section generally describes the primary reasons PFN and the Network Group believe this Domain and its policy topics warrant the attention of a PFN Network Group. Common factors may include scale, trajectory, irrevocability, neglect, importance, opportunities, and threats. Significant current public or governmental interest in the Domain or its policy topics are also possible factors. This section may also point out key ongoing structural facts relating to the Domain and its policy topics.

Other Considerations

This section (or sections), if needed, should describe other important considerations or matters that relate to the Domain and don’t fit neatly into any of the preceding sections.

Back Matter

The Domain Overview should close with Endnotes, Related Content, Acknowledgements, and Version History, each included only if there is content for it.

PFN Content. About Beta Content · About Network Groups · About PFN Content and Statement Types · About Solution Reports · PFN Content License · PFN Glossary.

Acknowledgements

Contributors. Harry Conaway (PFN Leader) is the author and writer of this content and is solely responsible for its substance.

Disclosures. Claude (Opus 5.5, Anthropic) was used to assist in editing this content. All substantive and writing decisions were made by the author and writer noted in the Contributors section above.

PFN Content Type. This content is classified as PFN about and governing content, and thus is not subject to PFN’s Content and Statement Types policy for substantive policy content.

Version History

Current Version. To be added