Generalizing AC Appeals and using this procedure for recall.

index.bs

@@ -1309,15 +1309,66 @@ Verifiable Random Selection Procedure</h5>
 			The incomplete terms are assigned in result order.
 	</ol>
 
+<h5 id="AB-TAG-recall">
+Recalling AB or TAG members</h5>
+
+<h6 id="individual-removal">
+Individual Removal</h6>
+
+	Individual participants of the [=Advisory Board=] or the [=Technical Architecture Group=]
+	can be <dfn export lt="remove|removal">removed</dfn> from those groups
+	if they are found by their peers
+	to be grossly neglecting their duties,
+	or to be acting in a way that seriously hampers the group's ability to function normally.
+
+	A chair of the [=AB=] or [=TAG=] <em class=rfc2119>must</em> hold a hearing
+	on the potential [=removal=] of a participant
+	if requested by at least three of the participants in the group.
+	After giving the individual in question
+	an opportunity to defend themselves,
+	a vote on the proposed [=removal=] is held.
+	If at least three quarters of the participants in the group,
+	excluding the individual who is the subject of such vote,
+	then vote in favor of the proposal,
+	the individual's seat on [=AB=] or [=TAG=] is [=vacated=] immediately.
+
+<h6 id="collective-removal">
+Collective removal</h6>
+
+	The [=Advisory Committee=] <em class=rfc2119>may</em>
+	hold a <dfn export>vote of no confidence</dfn>
+	in the [=Advisory Board=] or the [=Technical Architecture Group=].
+
+	An [=Advisory Committee representative=] initiates a [=vote of no confidence=]
+	by sending a request to the Team, and <em class=rfc2119>should</em> also share this request with the Advisory Committee.
+	The request <em class=rfc2119>must</em> identify which of the [=AB=] or [=TAG=] is targeted,
+	and <em class=rfc2119>should</em> also include the rationale.
+
+	Within one week, the [=Team=] <em class=rfc2119>must</em> initiate an [=Advisory Committee Override=]
+	on the proposal.
+
+	The conclusion of the [=Advisory Committee Override=] is final,
+	and cannot be the subject of a [=Formal Objection=] nor of an [=AC Appeal=]:
+	if the [=Advisory Committee Override=] proposal passes,
+	all seats on [=AB=] or [=TAG=] are [=vacated=] immediately;
+	if it fails, it cannot be invoked on the same body
+	sooner than 6-month since their previous invocation.
+
 <h5 id="AB-TAG-vacated">
 Elected Groups Vacated Seats</h5>
 
-	An [=Advisory Board=] or [=TAG=] participant's seat is vacated when:
+	An [=Advisory Board=] or [=TAG=] participant's seat is <dfn lt="vacated|vacant">vacated</dfn> when:
 
 	<ul>
 		<li>
 			the participant resigns, or
 
+		<li>
+			the participant is [=removed=], or
+
+		<li>
+			a [=vote of no confidence=] in the body they are part of is successful, or
+
 		<li>
 			an Advisory Board or TAG participant changes affiliations
 			such that the <a href="#AB-TAG-constraints">Advisory Board and TAG participation constraints</a> are no longer met,
@@ -1368,6 +1419,12 @@ Elected Groups Vacated Seats</h5>
 			and the maximum number corresponds to all unoccupied seats.
 			Except for the number of available seats and the length of the terms,
 			the <a href="#AB-TAG-elections">usual rules for Advisory Board and Technical Architecture Group Elections</a> apply.
+
+		<li>
+			If seats are vacated due to a successful [=vote of no confidence=],
+			the [=Team=] <em class=rfc2119>must</em> organize an election,
+			under the same condition as for individually vacated seats,
+			unless the next regularly scheduled election is fewer than three months away.
 	</ul>
 
 <h3 id="GAGeneral" oldids="ChapterGroups, WG-and-IG">
@@ -2887,24 +2944,50 @@ Appeal by Advisory Committee Representatives</h3>
 
 	An [=Advisory Committee representative=] initiates an [=appeal=] by sending a request to the [=Team=],
 	and should also share this request with the [=Advisory Committee=].
-	The request should say “I appeal this Decision”
+	The request <em class=rfc2119>should</em> say “I appeal this Decision”
 	and identify the decision,
-	and may also include their rationale for appealing the decision.
+	and <em class=rfc2119>may</em> also include their rationale for the [=appeal=].
 
 	Note: See [[DECISION-APPEAL inline]] for a recommendation
 	on how to communicate an appeal request to the [=Team=] and the [=AC=].
 
-	Within one week the [=Team=] <em class="rfc2119">must</em> announce the appeal process
+	Within one week, the [=Team=] <em class="rfc2119">must</em> initiate the [=appeal=]
+	in the form of an [=Advisory Committee Override=]
+	on the proposal to overturn the decision.
+
+	The conclusion of the [=Advisory Committee Override=] is final;
+	the same decision cannot be appealed more than once.
+
+	If the [=Advisory Committee Override=]
+	approves the proposal to overturn the decision,
+	those who had initiated the proposal <em class=rfc2119>may</em> revise it
+	to address the causes of rejection
+	and follow the ordinary applicable process
+	to submit the revised proposal.
+
+<h3 id="ac-override">
+Advisory Committee Override</h3>
+
+	An <dfn export>Advisory Committee Override</dfn> is an exceptional two-step procedure
+	used to resolve certain matters where neither the usual [=consensus=]
+	process nor its [[#addressing-fo|escalation path]] is sufficient.
+
+	Note: Currently, this only applies to [=AC Appeals=]
+	and [=votes of no confidence=] in the [=AB=] or [=TAG=].
+
+	First, the [=Team=] <em class="rfc2119">must</em> announce the proposal for an [=Advisory Committee Override=]
 	to the [=Advisory Committee=]
 	and provide a mechanism for [=Advisory Committee representatives=]
-	to respond with a statement of positive support for this appeal.
+	to respond with a statement of positive support for holding a vote.
 	The archive of these statements <em class="rfc2119">must</em> be [=member-only=].
+
 	If, within <span class="time-interval">one week</span> of the Team's announcement,
-	5% or more of the [=Advisory Committee=] support the appeal request,
-	the Team <em class="rfc2119">must</em> organize an appeal vote
+	5% or more of the [=Advisory Committee=] support holding the vote,
+	the Team <em class="rfc2119">must</em> organize a vote
 	asking the [=Advisory Committee=]
-	“Do you approve of the Decision?”
-	together with links to the decision and the appeal support.
+	whether they approve of the Advisory Committee Override proposal,
+	including details of the proposal
+	and links to support for holding the vote.
 
 	The ballot <em class="rfc2119">must</em> allow for three possible responses:
 	“Approve”,
@@ -2917,24 +3000,19 @@ Appeal by Advisory Committee Representatives</h3>
 	(including explicit “abstain” ballots) 
 	by [=Advisory Committee Representatives=]:
 	* if fewer than 5% participate,
-		the vote fails.
+		the proposal is rejected.
 	* if at least 5% but no more than 15% participate,
 		and the number of “Approve” ballots exceeds three times (3x) the number of “Reject” ballots,
-		the vote passes.
+		the proposal is approved.
 	* if more than 15% but fewer than 20% participate,
 		and the number of “Approve” ballots exceeds twice (2x) the number of “Reject” ballots,
-		the vote passes.
+		the proposal is approved.
 	* if 20% or more participate,
 		and the number of “Approve” ballots exceeds the number of “Reject” ballots,
-		the vote passes.
+		the proposal is approved.
 
-	If the vote passes,
-	the decision is overturned.
-	Following such rejection,
-	those who had initiated the proposal may revise it
-	to address the causes of rejection
-	and follow the ordinary applicable process
-	to submit the revised proposal.
+	Otherwise,
+	the proposal is rejected.
 
 <h2 id="Reports">
 W3C Technical Reports</h2>