Here is the proposed text for anyone who finds reading a diff inconvenient:

-----

12. Integration of Extensions during CR

Extensions to any of the Working Groups deliverables may proceed as separate extension specifications. At times, such extension specifications may advance more rapidly than the spec they extend (for example, extensions to the HTML spec itself may advance more rapidly). In some such cases, it may be desirable to integrate the extension back into the core specification.

1. Publish a First Public Working Draft of the extension spec
To be eligible for integration, an extension specification must be created in the first place, and must reach at least First Public Working Draft maturity level.

2. Satisfy CR exit criteria of the base spec
If an extension specification is to be nominated for integration into a base specification, it must first meet the CR exit criteria for the base specification. That is, every feature in the extension spec must demonstrate the level of interoperability that would be required for a feature in the base spec.

3. Nominate by the deadline
On entry to CR of any Working Groupspecification, the Chairs will identify a deadline prior to the end of CR for integration of extensions. A Working Group member may enter a nomination for integration at any time prior to the deadline. A nomination for integration must include:
  1. The name and URL of the extension specification to be integrated.
  2. The name and URL of the base specification it is to be integrated into.
  3. Rationale for integration.
  4. Evidence showing that the extension specification satisfies the CR exit criteria for the base specification.
  5. Instructions for textual integration for the editors of the base spec. These need not be detailed, but editors of the base specification may ask for more detail if required.

4. Call for Consensus
If a Working Group member enters a nomination by the deadline, and it contains all of the above required elements, the chairs will put out a Call for Consensus. If the Call for Consensus passes, then editors of the base specification will integrate the extension according to instructions. If objections are raised, objectors should cite rationale, and are encouraged to identify ways in which their objection may be addressed. If there are objections which cite rationale and are not resolved in a satisfactory manner, the Call for Consensus fails, and the extension will not be integrated. It may still be proposed for a future version using the usual issue process.

5. Integration
As with any other working group decision, editors will apply integration decisions within a week.

Oops, that text is for the wrong bug. Please disregard. It was meant for bug 18997.

Created attachment 1189 [details]
Patch applying the above policy (relative to the patch for bug 18997)

Here's the actual proposed text for this:

13. Removing some at-risk features early in CR

Working Group members may request early removal of features that the WG has approved to be on the list of at-risk features for a specification in (or soon to be in) Candidate Recommendation.

1. Marking as at risk
To be eligible to be dropped early, the feature must be approved by the Working Group to be on the list of at-risk features prior to CR.

2. Nominating for early removal.
If an at-risk feature does not have a thorough test suite, and also does not have even a single reasonably complete implementation, it may be nominated for early removal. Nominations for early removal may be entered before entering CR, or up to 3 months after entering CR.

3. Chair review
Chairs will review nominations to ensure that requests for early removal are reasonable.

4. Opportunity to present an implementation or tests
If a nomination is reviewed and approved, advocates of the feature have up to 3 months from the date of the request to present a thorough test suite or a reasonably complete implementation.

5. Early removal
If no one presents a thorough test suite or a reasonably complete implementation by the date 3 months after the request is made, then such features will be removed early. Such features may still be pursued in standalone specifications, and may be reintegrated into the core specification if they meet the CR exit criteria and have WG consensus.

(In reply to comment #3)
> Created attachment 1189 [details]
> Patch applying the above policy (relative to the patch for bug 18997)

Applied:

http://dev.w3.org/html5/decision-policy/decision-policy-v3.html#cr-remove-early