Published

Procurement

vr.wm-eco-007 · wm-eco-007-procurement

Describe one procurement proceeding from scoped demand and procedure choice through selection, review and contract handoff, with controlled evidence and disclosure.

World Models Society, people and institutions SOC.ECO.PRC2

Bundle → Layer → Finding → Questions Classifiers What it is Why it exists Distinguishing features What robots and AI may and may not do Moral aspects Owners Links to other meta-models Identity and identifiers Direct properties Recognition Capabilities and actions Hazards and failure modes Standards and interfaces Context of use Sources

Bundle → Layer → Finding → Questions Filled

7 bundles · 14 layers · 14 findings · 42 questions

Identity and procedure Procurement context for identity and procedure.

Process identity

Keep one procurement proceeding identifiable across revisions, lots and outcomes. Notice, release, submission and contract identifiers are distinct; a process need not end in an award.

Stable procurement identity

Keep one procurement proceeding identifiable across revisions, lots and outcomes. Notice, release, submission and contract identifiers are distinct; a process need not end in an award.

Which master namespace and identifier distinguish this procurement from its notices and releases? identity
Which related processes are earlier attempts, framework parents or call-offs rather than revisions of this process? relationship
What is the evidenced process state and which lot states remain different or unknown? state

Procedure and authority

Bind method choice to an adopted legal or private policy profile and a responsible procuring role. Direct awards and restricted or emergency procedures require explicit basis rather than fabricated competition.

Applicable procedure and authority

Which public or private profile and procurement method apply to this proceeding? classification
Who can approve this method and act for the buyer or procuring entity? authority
What justification and approval support any departure from the ordinary procedure? exception

Demand and awardable scope Procurement context for demand and awardable scope.

Need and funding context

Record the procurement purpose and scoped references to needs, budget and value assessments. This process does not appropriate funds, value assets or certify affordability.

Defined demand and funding references

Record the procurement purpose and scoped references to needs, budget and value assessments. This process does not appropriate funds, value assets or certify affordability.

What need and acceptance requirements define the proposed acquisition? requirement
What estimated value and funding evidence inform the procurement decision? measurement
Which delivery locations and contextual constraints affect the procurement scope? spatial

Lots and participation scope

Represent an undivided scope or identified lots with explicit bid coverage and award constraints. Item specifications stay externally mastered and physical measurements belong to those items.

Awardable scope and dependencies

Represent an undivided scope or identified lots with explicit bid coverage and award constraints. Item specifications stay externally mastered and physical measurements belong to those items.

How is the acquisition divided into lots or explicitly kept undivided? composition
Which combination limits or dependencies govern bidding and awards across lots? constraint
Which lot references connect each submission and proposed award to its actual scope? relationship

Solicitation and criteria Procurement context for solicitation and criteria.

Solicitation and clarifications

Link notices, invitations, enquiries and amendments to their recipients and rule versions. Publication is a separately evidenced action; private or restricted communications do not become public automatically.

Controlled solicitation versions

What solicitation or invitation was actually issued through which authorized channel? event
Which closing time and calendar govern submissions after any amendment? temporal
How were clarification answers and amendments distributed with appropriate confidentiality? access

Eligibility and award criteria

Separate participation qualifications, bid responsiveness and award criteria. Preserve the approved version, applicable method and authorized changes; numeric weights are not assumed for every procedure.

Declared assessment basis

Which eligibility requirements and evidence apply to each participant category? requirement
Which award criteria and decision method were disclosed or otherwise authorized? decision
What review checks the criteria version against the version actually used in evaluation? validation

Participants and submissions Procurement context for participants and submissions.

Participants and impartiality

Reference organizations, persons and joint participation without assuming legal personality or authority from a name. Record conflict and exclusion assessments with restricted access and a responsible decision maker.

Qualified participant roles

Who participates as bidder, consortium member, representative or evaluator? relationship
What evidence supports each qualification or exclusion assessment? evidence
How are conflicts of interest declared and managed without unnecessary personal disclosure? privacy

Submission and custody

Distinguish receipt, timeliness, admissibility and opening. Sealing and opening controls depend on the procedure; opening never transfers ownership by implication. Replacement and withdrawal require traceable versions.

Submission receipt and access evidence

What receipt evidence identifies the submitted version and its claimed arrival time? event
Which custody policy governs access and what evidence supports any authorized opening? security
How are late, replaced or withdrawn submissions preserved and assessed under the applicable rule? lifecycle

Evaluation and outcomes Procurement context for evaluation and outcomes.

Evaluation and exceptions

Keep submitted content, assessment inputs, criterion results and authorized decisions separable. Calculated ranks are advisory; missing evidence, abnormal values and suspected misconduct require review rather than automatic exclusion.

Evidence-backed assessment record

Which authorized evaluators assessed which submissions against which criteria version? process
What scores or comparisons follow from the recorded inputs and calculation method? measurement
Which inconsistencies or integrity concerns remain unresolved before a decision? quality

Award and contract handoff

Record awards, non-awards and cancellation with reasons, notices and optional contract references. An award need not map to one bid or one contract; announcing it is not contract formation or permission to spend.

Authorized outcome and separate contract

What authorized outcome applies to each lot and participant? decision
What notification evidence and profile-specific waiting conditions qualify the outcome? temporal
Which resulting contract references have been confirmed and which handoffs remain pending? relationship

Review and securities Procurement context for review and securities.

Challenges and correction

Track requests for review and their impact assertions through references to the competent forum or case. A complaint is not proof of suspension, and a local closure does not exhaust remedies.

Review status without assumed legal effect

Track requests for review and their impact assertions through references to the competent forum or case. A complaint is not proof of suspension, and a local closure does not exhaust remedies.

Which body and applicable rule govern a procurement challenge? authority
What evidence establishes whether the challenged action is suspended, corrected or still effective? state
How does the review outcome affect procurement revisions or a separately identified new process? lifecycle

Tender and performance securities

Record whether a security is required and link evidence of its terms and status. A tender security and a performance guarantee have different purposes; this model neither issues an instrument nor enforces or releases it.

Conditional security assurance references

Which tender or performance security is required by the applicable profile and at what stage? constraint
What instrument evidence supports the claimed amount, issuer and validity? evidence
Which authorized source establishes an extension, release or claim against the security? event

Disclosure and exchange Procurement context for disclosure and exchange.

Disclosure and record continuity

Separate confidential working records, participant views and public disclosure. Stewardship does not extinguish bidder rights. Retention, legal holds and lawful disposal must be profiled for every copy.

Controlled views and retention

Who is accountable for the procurement file and what separate rights remain over submitted material? ownership
Which recipient-specific view is authorized for this disclosure or audit request? access
What retention schedule and holds govern disposition of each procurement record and copy? retention

Provenance and exchange

Create lineage-aware projections with versioned bindings and explicit losses. A public release is not the whole file and a schema-valid message does not prove a lawful procurement.

Traceable projections and acceptance gaps

Create lineage-aware projections with versioned bindings and explicit losses. A public release is not the whole file and a schema-valid message does not prove a lawful procurement.

Which source revisions and transformations support each published or exchanged assertion? provenance
What pinned exchange profile preserves the selected view and reports mapping losses? interoperability
Which checks and unresolved failures qualify this projection for its intended use? validation

Classifiers Filled

Family: World Models
Category: Society, people and institutions
Entry kind: entity
Navigation path: NAV.SOC.ECO.PRC2
Domain: SOC.ECO.PRC2
Industry: Cross-industry
Tags: procurementsoc.eco.prc2
Also called: O7

What it is Filled

The root is a persistent procurement proceeding, not an entire procurement department, a single event, an exchange message or the resulting contract. Competition and noncompetitive selection are profile variants. Locally indexed lots, submissions and outcomes do not take ownership of external party, contract, instrument or dispute masters.

In scope

Identity, procedure authority, demand and funding references, lots and criteria
Solicitation, participant roles, qualification, submission custody and evaluation evidence
Outcomes, cancellation, notifications, conditional waiting rules, challenge references and security evidence
Record stewardship, retention and recipient-scoped exchange through the procurement lifecycle

Out of scope

Contract performance, invoicing, payment, inventory and logistics execution
Party registries, valuation engines, guarantee issuance or enforcement and judicial case management
Automatic supplier exclusion, award approval, contract signature, public posting or legal deadline computation
Detailed operational guidance for controlled items or dangerous goods; only restriction and authorization policy references may be carried

Why it exists Filled

Describe one procurement proceeding from scoped demand and procedure choice through selection, review and contract handoff, with controlled evidence and disclosure.

Distinguishing features Derived, awaiting review

Unlike Registry record plane: standalone-mm is a registry classification; entity denotes the persistent proceeding in the research schema.
Unlike Commercial Contract: Award, formation and performance are different facts. Zero or multiple contracts may be referenced; no contract lifecycle is absorbed.
Unlike Legacy O7 and unreviewed supplement: Retain tendering concepts but reject universal competition, sealing, standstill, one-to-one award relations and ownership transfer at opening. Private rules require their own profile.
Unlike External standards: OCDS and UBL cover wider contracting or exchange scopes. Selected alignments do not expand this root or establish conformance.
Unlike Stewardship and review: Custodian, contributor rights, access authorization, review forum and review case remain distinct. Legacy S1 and A19 aliases require explicit successor selection.

Note: Derived from boundary notes against neighbouring models.

What robots and AI may and may not do Derived, awaiting review

Must not

Restricted or dangerous subjects carry only policy and authorization references, never operational acquisition instructions.
Local disposal cannot cancel a procurement, erase an external master or annul a contract; no perpetual personal-data audit retention is assumed.
Deny protected content access unless recipient, purpose, stage and scope are authorized; public metadata does not open the full procurement file.

May

Resolve a process reference: Proposed operation, not implemented. Resolve exact namespace and identifier; similarity never authorizes merging procurements.
Record solicitation evidence: Proposed operation, not implemented. Append an existing notice or amendment reference with audience and version; do not publish or transmit it.
Record submission receipt evidence: Proposed operation, not implemented. Index an existing receipt and custody assertion without opening protected content or accepting the bid.
Prepare an evaluation view: Proposed operation, not implemented. Assemble authorized assessment inputs and unresolved differences. This proposed function performs no ranking, exclusion or award decision.
Record an outcome and handoff link: Proposed operation, not implemented. Reference an existing authorized outcome and any confirmed contract; do not award, notify, sign or spend.
Record review or security evidence: Proposed operation, not implemented. Append an externally authorized review or security event with its stated scope; do not suspend procurement, issue a guarantee or make a claim.
Prepare an authorized procurement projection: Proposed operation, not implemented. Build a local recipient-scoped export with pinned mapping and a loss report; no upload, notification or disclosure expansion.

Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.

Moral aspects Derived, awaiting review

Persistent proceeding and separately scoped child identifiers; aliases need evidence.

Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.

Owners Filled

Steward

Accountable procuring role and procurement file custodian with evidenced authority

Roles

Procurement custodian: Maintain qualified identity and controlled record continuity
Authorized procurement officer: Record evidenced events within mandate and procedure profile
Evaluation reviewer: Assess authorized inputs and record reasons without bypassing approval
Award authority: Provide independently evidenced outcome decisions within delegation
Records and access officer: Approve disclosure scope, retention, holds and disposition
Bidder or representative: Supply evidence and access only the permitted participant view
Review liaison: Link competent forum and case evidence without deciding legal effects

Links to other meta-models Filled

references

WM-ORG-001 - Candidate party master for buyers, procuring entities, bidders and issuers; verify and pin before use. Local roles do not replace organization identity.
WM-PER-001 - Candidate person master for individual bidders, representatives and evaluators; identities and personal rights remain separate.
WM-ECO-006 - Optional resulting commercial contract master. Replace legacy mandatory composition and one-to-one assumption with evidenced handoff references; performance and payment stay outside.
WM-ECO-002 - Candidate valuation master for estimates or currency conversion evidence; no local valuation engine.
WM-POL-009 - Optional court or arbitration case for a challenge; administrative review may use a different record and is not forced into litigation.
WM-POL-010 - Candidate forum identity and competence reference, separate from an individual review case; legacy A19 is ambiguous.
WM-POL-013 - Candidate registry mandate only when a disclosure profile requires it. Legacy public-register alias does not prove every tender needs this binding.
WM-XCT-001 - Candidate stewardship policy binding. Custody and opening do not transfer ownership; rights and policy evidence remain required.
WM-XCT-002 - Candidate access grant or consent binding; procurement access may depend on other legal bases and is not presumed to rest on consent.
WM-XCT-004 - Candidate access-audit record link; procurement event facts remain local while generic access audit semantics stay external.

aligned

OCDS 1.1.5 - Selected public-data concepts; lots and bid details require pinned extensions. No complete schema mapping or disclosure authorization follows.
UBL 2.3 - Selected pre-award message roles and contract handoff only; no implemented XML binding or conformance claim.
UNCITRAL Model Law 2011 - Policy-level conceptual comparison, not enacted law or a jurisdictional compliance claim; full legal verification remains open.
PROV-O 2013-04-30 - Evidence attribution and revision links without truth or legal-effect certification.

neighbor

Registry record plane - standalone-mm is a registry classification; entity denotes the persistent proceeding in the research schema.
Commercial Contract - Award, formation and performance are different facts. Zero or multiple contracts may be referenced; no contract lifecycle is absorbed.
Legacy O7 and unreviewed supplement - Retain tendering concepts but reject universal competition, sealing, standstill, one-to-one award relations and ownership transfer at opening. Private rules require their own profile.
External standards - OCDS and UBL cover wider contracting or exchange scopes. Selected alignments do not expand this root or establish conformance.
Stewardship and review - Custodian, contributor rights, access authorization, review forum and review case remain distinct. Legacy S1 and A19 aliases require explicit successor selection.

What else AI and robots need to interact with it Incomplete

Sources Filled

Open Contracting Data Standard: Release Reference - Open Contracting Partnership
Open Contracting Data Standard: Record Reference - Open Contracting Partnership
Universal Business Language Version 2.3 - OASIS
UNCITRAL Model Law on Public Procurement (2011): official overview - United Nations Commission on International Trade Law
Integrity in public procurement - Organisation for Economic Co-operation and Development
PROV-O: The PROV Ontology - World Wide Web Consortium
RFC 3339: Date and Time on the Internet: Timestamps - Internet Engineering Task Force
Guide to Enactment of the UNCITRAL Model Law on Public Procurement - United Nations Commission on International Trade Law

Open questions

Verify full primary texts, source versions and adopted jurisdiction or private-policy profiles, including exceptions and disclosure or records rules.
Build pinned nested schemas and exchange mappings with fixtures for no award, direct award, multi-lot outcomes, withdrawn bids, contested receipt, confidential review, lawful disposal and security expiry.
Restore independent external review and close all substantive holds before considering canonical or publishable-draft promotion.
Independent external review is waived; local self-audit cannot replace it.
Direct HTTP checks are unperformed under the sandbox restriction. Full UNCITRAL texts, current legal versions, licensing and applicability remain unverified.
Detailed private-sector and jurisdiction profiles, controlled-item restrictions, tax, competition and data-protection rules require qualified review.
No executable scoring, cryptographic bid custody, calendar, debarment screening or guarantee verification implementation is supplied.
OCDS extensions, UBL schemas, nested answer schemas, pinned neighbor bindings and adversarial instance tests are incomplete.

Machine files

Card as JSON Specification AGENTS.md Source Card backlog vercy.card/1

Provenance

world-models research · reviewable-draft

Built from: models/wm-eco-007-procurement/spec.yaml