§ 2, § 4.1.4, § 5.6.3 — Packages: line items sold only together, in place of requires and linked_execution

.github/ISSUE_TEMPLATE/change-request.yml

@@ -46,7 +46,7 @@ body:
         - "5.7 — Guarantees"
         - "5.8 — Transaction eligibility"
         - "5.9 — Execution"
-        - "5.10 — External references and settlement"
+        - "5.10 — External references, agreement, and billing"
         - "6 — Examples"
         - "Appendix A / B — Field index"
         - "Whole document / more than one section"

.github/ISSUE_TEMPLATE/comment.yml

@@ -34,7 +34,7 @@ body:
         - "5.7 — Guarantees"
         - "5.8 — Transaction eligibility"
         - "5.9 — Execution"
-        - "5.10 — External references and settlement"
+        - "5.10 — External references, agreement, and billing"
         - "6 — Examples"
         - "7 — Why this split"
         - "8 — Open questions"
@@ -47,7 +47,7 @@ body:
     attributes:
       label: Field(s) involved
       description: Comma-separated, if your comment is about specific fields.
-      placeholder: "pricing[].floor, transaction_mechanism"
+      placeholder: "pricing[].min_rate, transaction_mechanism"
   - type: textarea
     id: comment
     attributes:
@@ -63,9 +63,8 @@ body:
         A specific case where the draft as written produces the wrong outcome or
         cannot express what you need. This is what makes a comment actionable.
       placeholder: >-
-        A seller offering the same inventory as both PG and PMP cannot express a
-        different floor per mechanism, because pricing[] sits above
-        transaction_mechanism.
+        A [seller, buyer, or agent] doing [a specific case] can't express [what it
+        needs], because [the field or rule in the draft].
   - type: dropdown
     id: perspective
     attributes:

.github/ISSUE_TEMPLATE/config.yml

@@ -8,6 +8,6 @@ contact_links:
   - name: Read the comment process first
     url: https://github.com/IABTechLab/OpenProposal/blob/main/docs/comment-process.md
     about: Timeline, dispositions, and what happens to your comment.
-  - name: The seven open questions
+  - name: The open questions
     url: https://github.com/IABTechLab/OpenProposal/blob/main/docs/open-questions.md
     about: Where the working group is genuinely undecided. Highest-value place to comment.

.github/ISSUE_TEMPLATE/editorial.yml

@@ -12,7 +12,7 @@ body:
     id: location
     attributes:
       label: Where
-      placeholder: "spec/openproposal-3.0.md § 5.6, Appendix A row for `hold_status`"
+      placeholder: "spec/openproposal-3.0.md § 5.6, Appendix A row for `hold_terms`"
     validations:
       required: true
   - type: textarea

.github/labels.yml

@@ -10,7 +10,7 @@
   description: Proposes specific normative wording
 - name: open-question
   color: "d93f0b"
-  description: Relates to one of the 7 open questions in § 8
+  description: Relates to one of the open questions in § 8
 - name: implementation-feedback
   color: "0e8a16"
   description: From someone who built against the draft

.github/workflows/validate.yml

@@ -67,3 +67,24 @@ jobs:
           python-version: "3.12"
       - name: Check every field in the body appears in Appendix A
         run: python3 scripts/check_appendix.py
+
+  examples-match-spec:
+    name: Examples match the tables
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install pyyaml
+      - run: python3 scripts/check_examples.py
+
+  pricing-fixtures:
+    name: Pricing arithmetic vectors
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: python3 scripts/check_pricing_fixtures.py

CONTRIBUTING.md

@@ -16,15 +16,15 @@ GitHub account may file an issue or a pull request.
   thread rather than opening a duplicate, so the disposition covers one
   discussion, not five.
 - Check [docs/open-questions.md](docs/open-questions.md). If your point lands on
-  one of the seven questions the draft explicitly asks, comment there.
+  one of the questions the draft explicitly asks, comment there.
 
 ## 2. Pick the right route
 
 | Route | Use it for | Where it lands |
 | :--- | :--- | :--- |
 | **Comment** issue | Something is unclear, wrong, internally inconsistent, or missing. You are not proposing wording. | Triaged, dispositioned, logged |
 | **Change request** issue | You are proposing specific normative wording, a new field, a changed marker, or a removal. | Triaged, dispositioned, logged |
-| **Open question** comment | You are answering one of the 7 questions in § 8. | Feeds the resolution of that question |
+| **Open question** comment | You are answering one of the questions in § 8. | Feeds the resolution of that question |
 | **Implementation feedback** issue | You built against the draft and hit something. **This is the most valuable kind of comment we receive.** | Triaged with priority |
 | **Pull request** | You want to supply the exact diff for a change already discussed. | Reviewed against its issue |
 | **Discussion** | You have a question, or want to think out loud before filing. | No disposition; not part of the formal record |
@@ -40,10 +40,8 @@ them, but the short version:
 
 - **Cite the section.** `§ 5.6.1 commitment`, not "the commitment bit".
 - **Say what breaks.** A concrete scenario — a seller, a buyer, a field, and the
-  wrong outcome — beats a general objection. "A seller offering the same
-  inventory as both PG and PMP cannot express different floors per mechanism,
-  because `pricing[]` sits above `transaction_mechanism`" is actionable. "The
-  pricing model is too simple" is not.
+  wrong outcome — beats a general objection such as "the pricing model is too
+  simple".
 - **Say what you'd do instead**, even roughly. A rejected alternative is more
   useful to the working group than an unanswered complaint.
 - **Declare your interest.** Tell us whether you are commenting as a buyer,

README.md

@@ -15,7 +15,7 @@ server.
 | :--- | :--- |
 | **Current draft** | [`spec/openproposal-3.0.md`](spec/openproposal-3.0.md) |
 | **Comment period opens** | 2026-09-22 |
-| **Comment period closes** | 2026-10-22 |
+| **Comment period closes** | 2026-11-10 |
 | **Announcement** | [IAB Tech Lab introduces AAMP 3.0 with OpenProposal](https://iabtechlab.com/press-releases/iab-tech-lab-introduces-aamp-3-0-with-openproposal/) |
 | **Short link** | [iabtechlab.com/AAMPv3](https://iabtechlab.com/AAMPv3) (points to this repository) |
 | **How to comment** | [CONTRIBUTING.md](CONTRIBUTING.md) |
@@ -56,7 +56,7 @@ Pick the route that matches what you have to say:
 | :--- | :--- |
 | Flag something unclear, wrong, or missing | [Open a **Comment**](https://github.com/IABTechLab/OpenProposal/issues/new?template=comment.yml) |
 | Propose specific normative wording | [Open a **Change request**](https://github.com/IABTechLab/OpenProposal/issues/new?template=change-request.yml), or send a pull request against `spec/openproposal-3.0.md` |
-| Answer one of the 7 open questions | Comment on that question's [tracking issue](docs/open-questions.md) |
+| Answer one of the open questions | Comment on that question's [tracking issue](docs/open-questions.md) |
 | Report what happened when you tried to implement it | [Open **Implementation feedback**](https://github.com/IABTechLab/OpenProposal/issues/new?template=implementation-feedback.yml) |
 | Ask a question rather than raise an issue | Use [Discussions](https://github.com/IABTechLab/OpenProposal/discussions) |
 
@@ -69,15 +69,15 @@ in [docs/disposition-log.md](docs/disposition-log.md). See
 
 Three things to understand before the field tables make sense:
 
-1. **No inheritance.** Every line item is fully self-contained. A field never
+1. **No inheritance.** Every term of a line item is on the line item. A field never
    takes its value from the parent proposal or a sibling line item.
 2. **Every field carries exactly one mutability marker** (§ 3) — `immutable`,
-   `seller-set`, `selectable`, `settable`, `supplied`, `requestable` or
-   `derived`. The marker is what tells a buying agent whether it can act
-   unilaterally.
-3. **Composition is constraint satisfaction, not negotiation.** Of 71 fields,
-   only 3 require a round trip with the counterparty. That ratio is the design
-   claim the draft is asking you to test.
+   `seller-set`, `selectable`, `settable`, `supplied`, `requestable`, `derived`,
+   `lifecycle`, `recorded`, `asserted` or `mixed`. The marker is what tells a
+   buying agent whether it can act unilaterally.
+3. **Composition is constraint satisfaction, not negotiation.** Only `requestable`
+   fields require a round trip with the counterparty to resolve. Appendix B has the
+   count. That ratio is the design claim the draft is asking you to test.
 
 ## Downstream standards
 
@@ -89,8 +89,8 @@ OpenRTB 2.6). See § 1.1.
 
 Machine-readable schemas are coming. They are not published with this first
 draft, because the comment period is still deciding questions that shape
-them. They will follow the first revision, after the comment period closes on
-2026-10-22. Until then, [`examples/`](examples/) is the best reference for
+them. They will follow the first revision, after the comment period closes.
+Until then, [`examples/`](examples/) is the best reference for
 shape. See [schema/README.md](schema/README.md).
 
 ## Contributors and governance

docs/comment-process.md

@@ -8,14 +8,14 @@ or a documented decision not to change it.
 | Phase | Dates | What happens |
 | :--- | :--- | :--- |
 | **1. Comment period opens** | 2026-09-22 | Draft frozen at a tagged version. Announcement published. Issues open. |
-| **2. Comment period** | 2026-09-22 → 2026-10-22 (30 days) | Anyone may file. Maintainers triage and label within 5 business days of filing, but do not resolve. |
-| **3. Comment period closes** | 2026-10-22 | No new comments enter the formal record. Later issues are labelled `post-comment` and considered for the following draft. |
+| **2. Comment period** | 2026-09-22 → 2026-11-10 | Anyone may file. Maintainers triage and label within 5 business days of filing, but do not resolve. |
+| **3. Comment period closes** | 2026-11-10 | No new comments enter the formal record. Later issues are labelled `post-comment` and considered for the following draft. |
 | **4. Adjudication** | `TBD` → `TBD` | Working group works the queue. Every open comment gets a disposition. |
 | **5. Disposition published** | `TBD` | [disposition-log.md](disposition-log.md) published in full. Commenters notified on their issue. |
 | **6. Revised draft** | `TBD` | New draft tagged. Either ratification or a second comment period, depending on how much moved. |
 
 > **Maintainers: phases 4–6 are still `TBD`.** Fill them before the comment
-> period closes on 2026-10-22.
+> period closes.
 
 ## Dispositions
 
@@ -59,7 +59,7 @@ Triage labels, applied on filing:
 | :--- | :--- |
 | `comment` | General comment on the draft |
 | `change-request` | Proposes specific normative wording |
-| `open-question` | Relates to one of the 7 questions in § 8 |
+| `open-question` | Relates to one of the questions in § 8 |
 | `implementation-feedback` | From someone who built against the draft |
 | `editorial` | Typo, formatting, broken link — no normative effect |
 | `normative` | Changes what the spec requires |

docs/disposition-log.md

@@ -3,7 +3,7 @@
 The formal record of every comment filed during the OpenProposal 3.0 public
 comment period, and what was decided.
 
-**Status: comment period open (2026-09-22 → 2026-10-22). No dispositions yet.**
+**Status: comment period open (2026-09-22 → 2026-11-10). No dispositions yet.**
 
 This file is updated as comments are adjudicated and published in full at the
 end of the period. See [comment-process.md](comment-process.md) for what each