Skip to content

feat(order): Get Order operation#274

Closed
richmolj wants to merge 8 commits intomainfrom
lr/get-order
Closed

feat(order): Get Order operation#274
richmolj wants to merge 8 commits intomainfrom
lr/get-order

Conversation

@richmolj
Copy link
Copy Markdown
Contributor

Description

Add synchronous GET endpoint for order retrieval, complementing the
existing webhook push mechanism. Both return the same current-state
snapshot shape - webhooks deliver proactively to avoid polling, GET
provides on-demand access for reconciliation and conversational use.

Authorization model:

  • Who - MUST authenticate (non-negotiable, any UCP mechanism)
  • What - MAY scope access (platform credentials -> own orders, buyer authorization -> buyer's orders, or custom policies). MAY omit or redact fields based on context or business policy.
  • When - MAY enforce data availability (retention, erasure)

Type of change

  • New feature (non-breaking change which adds functionality)

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings

…emoving minimum on shared amount

Restore minimum: 0 on amount.json and introduce signed_amount.json
for places that genuinely need negative values. Adjustment totals now
inline their schema with signed_amount refs, keeping total.json and
all other amount.json consumers non-negative.

Addresses review feedback from @igrigorik on #254.
…unt override

Align with the composition pattern in PR #261 (totals contract):
allOf total.json base + signed_amount.json override, rather than
inlining the schema.
Add synchronous GET endpoint for order retrieval, complementing the
existing webhook push mechanism. Both return the same current-state
snapshot shape - webhooks deliver proactively to avoid polling, GET
provides on-demand access for reconciliation and conversational use.

Authorization model:
  Who - MUST authenticate (non-negotiable, any UCP mechanism)
  What - MAY scope access (platform credentials -> own orders,
         buyer authorization -> buyer's orders, or custom policies)
         MAY omit or redact fields based on context or business policy
  When - MAY enforce data availability (retention, erasure)
@richmolj richmolj requested review from a team as code owners March 18, 2026 18:32
@richmolj richmolj changed the title feat(order): Get Order operation w/ platform-auth feat(order): Get Order operation Mar 18, 2026
@richmolj richmolj closed this Mar 18, 2026
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