diff --git a/index.bs b/index.bs
index 2cbf0e15..52fc224d 100644
--- a/index.bs
+++ b/index.bs
@@ -5322,6 +5322,93 @@ Process Evolution
the [[COC|Code of Conduct]] in the Positive Work Environment Community Group,
and the Process in the W3C Process Community Group.
+
+Process Experimentation
+
+ The Advisory Board may authorize Process Experiments.
+ An Authorized Process Experiment modifies or replaces
+ one or more provisions of an operative policy for the authorized duration and scope of the experiment.
+
+ Authorized Process Experiments may be conducted over the Process Document
+ subject to the scope limitations defined below.
+
+
+Notification
+
+ The Advisory Boards must notify the Membership and public
+ of its decision to authorize a Process Experiment
+ no less than three weeks before the planned start of the experiment.
+ Provided the experiment remains within scope limitations,
+ the authorization itself is not subject to the usual Formal Objection mechanisms,
+ but it is subject to Advisory Committee Appeal.
+ The usual Process safeguards (objections, appeals),
+ to the extent they are not themselves modified by the experiment,
+ remain in place for decisions made during the course of an experiment.
+
+ Notification of a Process Experiment Authorization must:
+
+ * Describe what problem(s) the experiment seeks to address.
+ * Include hypotheses for how the experiment will address these problems
+ and what success would look like.
+ * Identify the policy provisions that are temporarily suspended during the experiment,
+ and include the language that temporarily replaces those provisions.
+ * Identify explicitly the parties affected by the experiment.
+ When an experiment is designed to affect a limited audience
+ (e.g., one Working Group),
+ the Advisory Board must socialize the experiment with them
+ before issuing the the formal notification.
+ When an experiment affects a large audience
+ (e.g., all Working Groups),
+ the Advisory Board must provide rationale for the more expansive scope.
+ * Specify an end date that may not be more than 1 year after the start date of the experiment.
+
+
+Scope limitations
+
+ Authorized Process Experiments must not:
+
+ * Extend to policies included by reference in the Process Document.
+ * Alter the rules that give the Advisory Board the authority to conduct experiments
+ or permanently change a policy.
+ * Alter patent policy commitments.
+ * Have retroactive effect.
+
+
+Extensions
+
+ An Authorized Process Experiment expires automatically on its specified end date
+ but may be extended at most one time for up to one year.
+ If the Advisory Board wishes to extend an experiment:
+
+ * the Advisory Board must issue a [=Process Experiment Report=]
+ * the extension must be approved by majority vote of the Advisory Committee
+ by a ballot open for two weeks at a minimum.
+
+
+Process Experiment Reports
+
+ Upon conclusion or termination of a Process Experiment and prior to any extension,
+ the Advisory Board must share a Process Experiment Report
+ with the Membership and public.
+
+ A Process Experiment Report must:
+
+ * Describe at a high level what happened, what was learned, and what evidence was gathered.
+ * Indicate whether the hypotheses in the Process Experiment Authorization were supported,
+ and what unexpected events occurred.
+ * Advise whether the experiment be extended, modified, or proposed for permanent adoption,
+ or should no further action be taken.
+
+
+Experiment outcomes
+
+ Not all experiments will be deemed successful or lead to permanent changes to the Process Document.
+ The validity of actions or decisions taken as part of an authorized Process Experiment
+ does not depend on the outcome of the experiment.
+
+ An Authorized Process Experiment does not amend the operational policy permanently;
+ making any change permanent requires the usual approval process.
+
Appendix A: Retired Terminology