This document explains whether, what, and how much review any piece of PFN content must receive before it is finalized and shared. The policies addressed in this document are organized around PFN’s Content Types (Exploratory Content, Beta Content, and Shared Content) and Statement Types (Factual Claims, Analysis and Interpretation, and Beliefs and Values).
Capitalized terms that this document does not define have the meanings given in the PFN Glossary. If a term is defined both in the Glossary and in this document below, the definition here governs for purposes of this document. See Related Content below.
Content Types
PFN recognizes three general and mutually exclusive Content Types: Exploratory Content, Beta Content, and Shared Content. These apply to PFN’s policy content. They do not apply to PFN’s about and governing documents, which are identified in the PFN Document Map.
The author and the PFN Leader determine which Content Type applies to a Content Item, with the PFN Leader deciding. Beta Content requires designation by the PFN Leader. Content that is neither Exploratory Content nor Beta Content is Shared Content.
Exploratory Content. Content qualifies as Exploratory Content if it satisfies all of these requirements:
- Constitutes informal comments, discussions, brainstorming, ideation, outlines, lists, straw manning, steelmanning, and other early versions of an idea, a logical flow, a paragraph, or more, whether spoken or written.
- Is shared only within a Gated Audience.
- Is presented in a way that makes its exploratory, unverified, and unreviewed nature clear to those who encounter it. As the content becomes more developed (e.g., closer to final, publishable form), the exploratory nature of the content should be more explicit.
The goal is to allow Participants to “think out loud” with other Participants without concern about out-of-context understandings and unintended attribution.
Common examples of Exploratory Content include discussions, informal comments, brainstorming, research notes, article outlines, draft paragraphs and articles, and similar “early thinking” situations that Participants express in Gated Venues with small and larger groups, so long as the groups qualify as Gated Audiences. These and similar situations typically constitute efforts to explore and try out ideas, sources, experts, organizations, and data, to brainstorm early outlines and versions of content, and to develop possible solutions for various policy matters. The Gated Audience may be as small as an author and co-author, and may also include researchers and other primary contributors, working together to generate ideas and thinking that may turn into short articles or larger Solution Reports.
Similarly, Exploratory Content includes “under development” content shared within a larger Gated Audience via a Gated Venue, such as content shared with the Participants of one or more specified Network Groups via the PFN website in a manner accessible only to those Participants. In many cases, this Exploratory Content may be part of Network Group discussions, comments, suggestions and solution development.
In general, Exploratory Content does not have to be labeled as Exploratory, verified, or include Acknowledgements and Version History sections. Nevertheless, there may be specific situations (e.g., when the Exploratory Content is close to final, publishable form) when it would be both important and helpful to users for Exploratory Content to be explicitly labeled as Exploratory and for its Factual Claim and Analysis and Interpretation statements to be verified. The labeling can be done in various ways, such as in the content’s title, a label linked with the title, or a short explanation in the content’s excerpt, summary, or Acknowledgements section. Also, in some cases it may be important and helpful to users to disclose whether and how generative AI was used. See About Using Generative AI for more about PFN disclosure policies relating to generative AI.
With approval of the PFN Leader and the author, specific individuals may be treated as part of Gated Audience for a stated period and purpose. This may occur, for example, when an author wishes to share a draft version of an article (or parts of an article) for a specific time (e.g., two weeks) with one or a few specific individuals who are otherwise outside the Gated Audience to get reactions to and feedback on the draft. In such circumstances, the author should get the commitment of the individuals with whom the Exploratory Content is shared that they will not share the content, or any key or identifying information about the content, outside the restricted group of people.
Exploratory Content becomes Beta Content or Shared Content when PFN publishes it beyond a Gated Audience. At that point it must satisfy the policies below for that Content Type, and its Version History begins with that publication.
Beta Content. Content that is shared beyond a Gated Audience (and no longer qualifies as Exploratory Content) may qualify as Beta Content if it meets all of the following requirements:
- Is designated by the PFN Leader as Beta Content for a stated purpose recognized under this Policy.
- Is intended to provide PFN users, prospective Participants, current Participants, and others with examples hypothetically illustrating PFN webpages, articles, content, events, meetings, activities, policies, and processes.
- Is explicitly labeled as Beta Content so that users will easily encounter such label. In general, the Beta Content label should show on the front or first page of the content.
- Includes an Acknowledgements section as if the content were Shared Content and, in addition, that tells users how they can submit questions or concerns to PFN about the Beta Content.
- Cites only sources that have been verified as described under Factual Claims below (existence and citation accuracy only). Factual Claim statements and Analysis and Interpretation statements need not otherwise be verified, and the content need not be reviewed to assure clarity, consistency, and coherence.
- Includes a Version History section as if the content were Shared Content.
Common examples of Beta Content are PFN webpages and content that illustrate Network Group main webpages, Domains, Domain Overviews, policy topics encompassed by the Domains, Solution Reports, practices, and processes. Also, Beta Content may be produced with significant generative AI assistance and without human verification, but in this situation, the use of generative AI assistance should be disclosed in the Acknowledgements section.
PFN removes, modifies, or replaces Beta Content when the content it illustrates becomes available, or when the purpose for which the PFN Leader designated it has been met.
Shared Content. Content that does not qualify as Exploratory Content or Beta Content should satisfy these Shared Content policies:
- Factual Claim Statements, including each resource and reference citation, should be reviewed and verified for accuracy.
- Analysis and Interpretation Statements should be peer reviewed against PFN’s clear, consistent, and coherent standard. This requirement does not apply to Beliefs and Values.
- Shared Content should include Acknowledgements and Version History sections.
PFN content that requires verification or peer review generally requires verification review by at least one peer reviewer. Enough reviewers should be assigned to assure that every substantive part of the content has been reviewed by a qualified person. In any case, as a rule, at least two reviewers should be assigned to content that is to be published as a Solution Report and to other PFN content that is longer than 1200 words.
A peer reviewer examines the content closely, critically, and constructively, and is willing to be listed as a peer reviewer of the content in its entirety or of the specific part reviewed. A peer reviewer is not just an editor or a copy editor. The reviewer considers whether the Factual Claim statements and Analysis and Interpretations statements are correct, likely to be correct, or can reasonably be regarded as correct, setting aside differences in Beliefs and Values. A reviewer does not merely screen for content that is clearly or likely incorrect.
A peer reviewer should have the subject-matter knowledge needed to evaluate the part of the content being reviewed. A peer reviewer may be a PFN Participant, including a Participant in the same Network Group as the author, or a person from outside PFN whom the PFN Leader approves. A peer reviewer should not be an author of the content and should not have a competing interest in it that would undermine the review.
A peer reviewer may choose to consider the content’s Beliefs and Values, not for correctness, but rather for the reasonableness of the Beliefs and Values statements given the more general views and values that underlie the content.
Furthermore, a peer reviewer should review content for the effectiveness of the writing, organization, and communication, at the macro-organization level and the micro-organization level and at the section, paragraph, sentence, and phrase level. Is the content organized and written in a clear, consistent, and coherent manner? Is the content, or certain parts of the content, too hard to follow?
In some instances, a broad review or a review that makes significant substantive contributions may justify the author(s) extending author or contributor recognition to the reviewer, assuming the reviewer does not opt-out of such recognition.
Shared Content that does not satisfy these requirements is non-compliant. It does not become Exploratory Content or Beta Content. PFN brings it into compliance or withdraws it from publication.
If Shared Content contains a significant error, PFN will correct it as soon as practicable and will note the correction in the Version History. Where the error is material to the content’s conclusions, PFN will add a visible correction notice to the Content Item.
Statement Types
PFN recognizes three Statement Types: Factual Claims, Analysis and Interpretation, and Beliefs and Values. A single piece of content, no matter which Content Type, will typically contain more than one Statement Type. In general, the Content Type governs the requirements for Factual Claim Statements and Analysis and Interpretation Statements in the content. These standards do not establish that an Analysis and Interpretation Statement is correct, and they do not mean that every Participant who contributed to the content shares the Beliefs and Values it expresses.
Factual Claims. Factual Claims are statements capable of being true or false and of being checked against a source. Examples include statistics, dates, quotations, citations, statutory or regulatory text, and characterizations of what a study found. Here are the verification policies for Factual Claims:
- In Exploratory Content, verification is not required.
- In Beta Content, the existence and accuracy of each cited source and its citation information should be verified. Verification that the content accurately characterizes each cited source is not required. Additional verification of Factual Claims is not required.
- In Shared Content, each Factual Claim and every citation should be verified.
Analysis and Interpretation. Analysis and Interpretation Statements generally reflect reasoning drawn from factual claims. Examples include projections, correlation and causation claims, syntheses of evidence, and assessments of tradeoffs or likely impacts. Here are the primary verification policies for Analysis and Interpretation Statements:
- In Exploratory Content and Beta Content, verification of Analysis and Interpretation Statements is not required.
- In Shared Content, Analysis and Interpretation Statements should be reviewed against PFN’s clear, consistent, and coherent standard and against the writing and communication effectiveness standards set forth above. This review confirms that the reasoning holds together internally and fairly represents the evidence it draws on. It does not confirm that the conclusion is necessarily the correct one, since more than one conclusion may be reasonable and satisfy this standard.
Beliefs and Values. Belief and Value Statements reflect normative and similar claims that are based on values, ideologies, and beliefs. They often concern discussions about priorities and tradeoffs. Examples include judgments that one policy goal should outweigh another or that tradeoffs are acceptable or unacceptable.
Beliefs and Values do not need to be verified or evaluated for correctness, regardless of Content Type. In addition, a statement expressing a belief or value need not be attributed to a specific Participant by name, so long as it is clear that the statement expresses a belief or value, rather than a factual claim or analysis and interpretation, and that responsibility for the content, including its beliefs and values, rests with the Participants listed as authors, subject to the review and verification described above (see Content Types).
Related Content
PFN Content. About Beta Content · About Solution Reports · About Using Generative AI · PFN Content License · PFN Glossary · PFN Overview Infographic · Terms of Use.
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