Skip to content

§ 2, § 4.1, § 5.6 — Line-item dependencies and bonus lines (#23) - #70

Draft
Sirajmx wants to merge 2 commits into
mainfrom
spec/23-line-item-dependencies
Draft

Sirajmx wants to merge 2 commits into
mainfrom
spec/23-line-item-dependencies

Conversation

@Sirajmx

@Sirajmx Sirajmx commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Draft. Do not merge until the working group confirms the disposition of #23.

What this changes

A proposal can now say whether its line items may be bought separately (linked_execution, § 4.1), and a line item can say which other line items, or what spend on them, must be in the same commitment (requires, § 5.6.3). A bonus line item is a line item with requires and its own price, so every price stays self-contained. The § 2 "binding terms" hook now points at a real field. The Summary Representation carries has_requires and linked_execution, so screening agents don't recommend a line item that can't be bought on its own.

Related issue

Refs #23. Proposed to close OQ-5 (#6). The "same proposal and version" rule relies on the version rules proposed in #24.

Type

  • Editorial — no normative effect
  • Normative — changes what the spec requires
  • Breaking — would break an implementation already built to this draft
  • Examples / schema / docs only

Checklist

  • The body section is updated
  • Appendix A (field index) matches the body — two rows; scripts/check_appendix.py passes
  • Appendix B (fields by marker, and the counts) matches the body — seller-set 29 → 31; 71 → 73 fields
  • Any affected example in examples/ is updated and still parses — new line-item-ctv-bonus.yaml (§ 6.5); linked_execution: none in proposal.yaml
  • RFC 2119 keywords used deliberately — MUST / SHOULD / MAY are not synonyms
  • The no-inheritance rule (§ 2) still holds — requires references sibling ids; it inherits no values
  • Anything selectable declares available[] and included[]; anything settable declares bounds (§ 3.1, § 3.2) — no new selectable or settable fields
  • No confidential or commercially sensitive content

Knock-on effects


By opening this pull request I agree my contribution may be published under this
repository's licence, as set out in CONTRIBUTING.md.

A proposal can say its line items must be bought together
(linked_execution, § 4.1), and a line item can name the line items or
spend that must be in the same commitment (requires, § 5.6.3). A bonus
line is a line item with requires and its own price. The § 2 "binding
terms" hook now points at a field, and the Summary Representation
carries has_requires and linked_execution.

Adds a CTV bonus line example (§ 6.5) and linked_execution: none to the
proposal example.

Refs #23
The rule that a hold on a linked_execution: all proposal uses
hold_scope: proposal came from a comment on #23, not the change request
as filed. It moves to the PR description as a point for the working
group, so this PR carries only the filed change.

Refs #23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant