# procure (10-procure.org)

To obtain or acquire something, often with care or effort. People say it when they mean to get supplies, find rare items, or secure something through a formal process.

## What a model may hear
- database row locking (SQL and transaction systems): assume the user wants SELECT FOR UPDATE or a pessimistic lock to reserve a record
- remote procedure call (distributed systems and gRPC): treat it as a request to invoke a procedure on another machine, possibly serializing arguments
- procurement workflow automation (enterprise software and ERP): trigger purchase-order flows, vendor approval chains, or contract lifecycle steps
- memory or resource acquisition (systems programming and OS kernels): interpret as a request to allocate or reserve hardware resources

## Where people and models part ways
- Says: "procure the latest report"
  Means: find and download the most recent file
  May be taken as: lock the database row containing report metadata, blocking other users
  Say instead: "find and download the latest report file"
- Says: "procure a list of customers"
  Means: get or generate a customer list
  May be taken as: initiate a formal procurement workflow for a vendor list purchase
  Say instead: "generate or retrieve a list of customers"
- Says: "procure more memory"
  Means: get additional RAM for the computer
  May be taken as: attempt a kernel-level resource reservation or RPC to a memory service
  Say instead: "add more RAM to this machine or increase the memory limit"

## Tips
- Use 'get,' 'find,' or 'download' instead when you simply want to obtain a file or information.
- Specify 'purchase order' or 'vendor approval' if you actually mean corporate procurement.
- Say 'lock the record' or 'reserve the row' if you mean database locking.
- Add 'for me' or 'please find' to signal a human request, not a system command.
- Avoid 'procure' in code-related contexts; it overlaps with technical acquisition patterns.

## Often confused with
- acquire: less likely to trigger database or ERP systems
- fetch: strongly tied to HTTP and web requests, not procurement workflows
- obtain: more neutral, fewer technical lock or RPC associations
- purchase: explicitly commercial, avoids systems programming senses
- secure: adds safety connotation, may trigger security or encryption contexts
- source: emphasizes origin, less likely to invoke transaction locking