# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T14:45:30Z", "synthesisSha256": "cfa760fba4190bd60d8d33cb74d1fc20537b4f3dd787357f0a546623e44ff712", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ECO-007", "registryId": "vr.wm-eco-007", "name": "Procurement", "version": "0.3.0", "previousVersions": [ { "version": "0.2.0-legacy", "url": "https://github.com/ver-cy/world-models/blob/feat/mega-model-registry/models/organizations/O7-procurement-and-tendering.md" } ], "entryKind": "entity", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ECO.PRC2" ], "tags": [ "procurement", "soc.eco.prc2" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-eco-007-procurement/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-eco-007", "model": { "registry_id": "vr.wm-eco-007", "model_id": "WM-ECO-007", "name": "Procurement", "entry_kind": "entity", "purpose": "Describe one procurement proceeding from scoped demand and procedure choice through selection, review and contract handoff, with controlled evidence and disclosure.", "scope_statement": "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" ], "boundary_notes": [ { "neighbor": "Registry record plane", "distinction": "standalone-mm is a registry classification; entity denotes the persistent proceeding in the research schema.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "Commercial Contract", "distinction": "Award, formation and performance are different facts. Zero or multiple contracts may be referenced; no contract lifecycle is absorbed.", "source_refs": [ "SRC-001", "SRC-003" ] }, { "neighbor": "Legacy O7 and unreviewed supplement", "distinction": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008" ] }, { "neighbor": "External standards", "distinction": "OCDS and UBL cover wider contracting or exchange scopes. Selected alignments do not expand this root or establish conformance.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "neighbor": "Stewardship and review", "distinction": "Custodian, contributor rights, access authorization, review forum and review case remain distinct. Legacy S1 and A19 aliases require explicit successor selection.", "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Open Contracting Data Standard: Release Reference", "organization": "Open Contracting Partnership", "url": "https://standard.open-contracting.org/latest/en/schema/reference/", "version_or_date": "1.1.5 as displayed on 2026-10-06; latest URL is mutable", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:44:08Z", "relevance": "Selected planning, tender, parties, award, contract and extension descriptions. Multiple awards, method rationale and scoped identifiers inform this authored structure; not an OCDS conformance claim." }, { "id": "SRC-002", "title": "Open Contracting Data Standard: Record Reference", "organization": "Open Contracting Partnership", "url": "https://standard.open-contracting.org/latest/en/schema/records_reference/", "version_or_date": "1.1.5 as displayed on 2026-10-06; latest URL is mutable", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:44:08Z", "relevance": "Compiled and versioned releases distinguish current projections from change history. Publication records are not the confidential procurement master." }, { "id": "SRC-003", "title": "Universal Business Language Version 2.3", "organization": "OASIS", "url": "https://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html", "version_or_date": "UBL 2.3 OASIS Standard", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:44:08Z", "relevance": "Selected pre-award process descriptions and document roles cover qualification, tender receipt, withdrawal, notifications, guarantee certificate and contract handoff. These are exchange alignments, not universal legal rules." }, { "id": "SRC-004", "title": "UNCITRAL Model Law on Public Procurement (2011): official overview", "organization": "United Nations Commission on International Trade Law", "url": "https://uncitral.un.org/en/texts/procurement/modellaw/public_procurement", "version_or_date": "Model Law adopted 2011-07-01; overview indexed on 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:44:08Z", "relevance": "Official indexed overview supports procedure diversity, transparency, competition, integrity and challengeability. Full legal text was not retrieved; no enacted jurisdictional rule is inferred." }, { "id": "SRC-005", "title": "Integrity in public procurement", "organization": "Organisation for Economic Co-operation and Development", "url": "https://www.oecd.org/en/topics/integrity-in-public-procurement.html", "version_or_date": "Undated topic page accessed 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:44:08Z", "relevance": "Selected discussion supports accountability, oversight and internal controls. Local conflict declarations and escalation questions are proposed safeguards, not a certified risk detector." }, { "id": "SRC-006", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:44:08Z", "relevance": "Attribution, derivation and revision relations support evidence lineage; provenance does not certify truth, authorization or legal validity." }, { "id": "SRC-007", "title": "RFC 3339: Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "July 2002, sections 4 and 5.6", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:44:08Z", "relevance": "Offset-qualified event timestamps; deadline calendars and periods need separate profiles." }, { "id": "SRC-008", "title": "Guide to Enactment of the UNCITRAL Model Law on Public Procurement", "organization": "United Nations Commission on International Trade Law", "url": "https://uncitral.un.org/sites/uncitral.un.org/files/media-documents/uncitral/en/guide-enactment-model-law-public-procurement-e.pdf", "version_or_date": "Guide adopted 2012; selected indexed page 99 and confidentiality commentary; full PDF unverified", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:44:08Z", "relevance": "Indexed commentary supports conditional tender-security requirements and protection of confidential information. Full retrieval returned 403 through the browser tool; detailed provisions remain unverified." } ], "structure": { "bundles": [ { "id": "bundle-governance", "name": "Identity and procedure", "description": "Procurement context for identity and procedure.", "rationale": "Authored concern grouping grounded in cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "layer-identity", "name": "Process identity", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "findings": [ { "id": "finding-identity", "name": "Stable procurement identity", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "questions": [ { "id": "q-identity-1", "text": "Which master namespace and identifier distinguish this procurement from its notices and releases?", "kind": "identity", "answer_data": [ "identity: master namespace, process ID, aliases, reconciliation evidence", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-identity-2", "text": "Which related processes are earlier attempts, framework parents or call-offs rather than revisions of this process?", "kind": "relationship", "answer_data": [ "links: target process ID, relationship type, profile, evidence", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-identity-3", "text": "What is the evidenced process state and which lot states remain different or unknown?", "kind": "state", "answer_data": [ "state: process state, lot states, basis, effective time, uncertainty", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-identity-1", "name": "identity", "description": "Candidate answer group: identity: master namespace, process ID, aliases, reconciliation evidence. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "data-identity-2", "name": "links", "description": "Candidate answer group: links: target process ID, relationship type, profile, evidence. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "data-identity-3", "name": "state", "description": "Candidate answer group: state: process state, lot states, basis, effective time, uncertainty. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-identity", "name": "Process identity register", "description": "Versioned local index of answers, evidence references and unresolved assessments; authoritative source records remain externally mastered.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with namespace and revision first; governed external URI next; otherwise opaque local UUID with reconciliation status. Use stable entry IDs and revision sequences.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-profile", "name": "Procedure and authority", "description": "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.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "findings": [ { "id": "finding-profile", "name": "Applicable procedure and authority", "description": "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.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "questions": [ { "id": "q-profile-1", "text": "Which public or private profile and procurement method apply to this proceeding?", "kind": "classification", "answer_data": [ "profile: jurisdiction, policy ID, version, effective date, method, category", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-profile-2", "text": "Who can approve this method and act for the buyer or procuring entity?", "kind": "authority", "answer_data": [ "authority: buyer reference, procuring entity reference, role, mandate evidence, limits", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-profile-3", "text": "What justification and approval support any departure from the ordinary procedure?", "kind": "exception", "answer_data": [ "exception: affected rule, grounds, approving role, evidence, expiry, unresolved review", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-profile-1", "name": "profile", "description": "Candidate answer group: profile: jurisdiction, policy ID, version, effective date, method, category. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "data-profile-2", "name": "authority", "description": "Candidate answer group: authority: buyer reference, procuring entity reference, role, mandate evidence, limits. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "data-profile-3", "name": "exception", "description": "Candidate answer group: exception: affected rule, grounds, approving role, evidence, expiry, unresolved review. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-profile", "name": "Procedure and authority register", "description": "Versioned local index of answers, evidence references and unresolved assessments; authoritative source records remain externally mastered.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with namespace and revision first; governed external URI next; otherwise opaque local UUID with reconciliation status. Use stable entry IDs and revision sequences.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-scope", "name": "Demand and awardable scope", "description": "Procurement context for demand and awardable scope.", "rationale": "Authored concern grouping grounded in cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-003" ], "layers": [ { "id": "layer-need", "name": "Need and funding context", "description": "Record the procurement purpose and scoped references to needs, budget and value assessments. This process does not appropriate funds, value assets or certify affordability.", "source_refs": [ "SRC-001", "SRC-003" ], "findings": [ { "id": "finding-need", "name": "Defined demand and funding references", "description": "Record the procurement purpose and scoped references to needs, budget and value assessments. This process does not appropriate funds, value assets or certify affordability.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "q-need-1", "text": "What need and acceptance requirements define the proposed acquisition?", "kind": "requirement", "answer_data": [ "need: purpose, goods works or services, requirement references, exclusions, acceptance basis", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-need-2", "text": "What estimated value and funding evidence inform the procurement decision?", "kind": "measurement", "answer_data": [ "estimate: amount, currency, tax basis, valuation date, uncertainty, budget references", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-need-3", "text": "Which delivery locations and contextual constraints affect the procurement scope?", "kind": "spatial", "answer_data": [ "context: location references, delivery constraints, service area, accessibility requirements", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-need-1", "name": "need", "description": "Candidate answer group: need: purpose, goods works or services, requirement references, exclusions, acceptance basis. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "data-need-2", "name": "estimate", "description": "Candidate answer group: estimate: amount, currency, tax basis, valuation date, uncertainty, budget references. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "data-need-3", "name": "context", "description": "Candidate answer group: context: location references, delivery constraints, service area, accessibility requirements. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "artifact-need", "name": "Need and funding context register", "description": "Versioned local index of answers, evidence references and unresolved assessments; authoritative source records remain externally mastered.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with namespace and revision first; governed external URI next; otherwise opaque local UUID with reconciliation status. Use stable entry IDs and revision sequences.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-lots", "name": "Lots and participation scope", "description": "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.", "source_refs": [ "SRC-001", "SRC-003" ], "findings": [ { "id": "finding-lots", "name": "Awardable scope and dependencies", "description": "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.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "q-lots-1", "text": "How is the acquisition divided into lots or explicitly kept undivided?", "kind": "composition", "answer_data": [ "lots: scoped lot IDs, descriptions, item references, quantities and units, undivided reason", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-lots-2", "text": "Which combination limits or dependencies govern bidding and awards across lots?", "kind": "constraint", "answer_data": [ "constraints: allowed combinations, dependency rules, limits, rule version, evidence", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-lots-3", "text": "Which lot references connect each submission and proposed award to its actual scope?", "kind": "relationship", "answer_data": [ "coverage: bid references, lot references, award references, unresolved scope mismatches", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-lots-1", "name": "lots", "description": "Candidate answer group: lots: scoped lot IDs, descriptions, item references, quantities and units, undivided reason. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "data-lots-2", "name": "constraints", "description": "Candidate answer group: constraints: allowed combinations, dependency rules, limits, rule version, evidence. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "data-lots-3", "name": "coverage", "description": "Candidate answer group: coverage: bid references, lot references, award references, unresolved scope mismatches. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "artifact-lots", "name": "Lots and participation scope register", "description": "Versioned local index of answers, evidence references and unresolved assessments; authoritative source records remain externally mastered.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with namespace and revision first; governed external URI next; otherwise opaque local UUID with reconciliation status. Use stable entry IDs and revision sequences.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-solicitation", "name": "Solicitation and criteria", "description": "Procurement context for solicitation and criteria.", "rationale": "Authored concern grouping grounded in cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008" ], "layers": [ { "id": "layer-notice", "name": "Solicitation and clarifications", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "findings": [ { "id": "finding-notice", "name": "Controlled solicitation versions", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "questions": [ { "id": "q-notice-1", "text": "What solicitation or invitation was actually issued through which authorized channel?", "kind": "event", "answer_data": [ "issue: document ID, version, channel, audience, dispatch and receipt evidence", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-notice-2", "text": "Which closing time and calendar govern submissions after any amendment?", "kind": "temporal", "answer_data": [ "deadline: instant or date, offset, calendar, rule, amendment version, uncertainty", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-notice-3", "text": "How were clarification answers and amendments distributed with appropriate confidentiality?", "kind": "access", "answer_data": [ "clarification: enquiry ID, response revision, audience, redactions, equal-information assessment", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-notice-1", "name": "issue", "description": "Candidate answer group: issue: document ID, version, channel, audience, dispatch and receipt evidence. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] }, { "id": "data-notice-2", "name": "deadline", "description": "Candidate answer group: deadline: instant or date, offset, calendar, rule, amendment version, uncertainty. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] }, { "id": "data-notice-3", "name": "clarification", "description": "Candidate answer group: clarification: enquiry ID, response revision, audience, redactions, equal-information assessment. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-notice", "name": "Solicitation and clarifications register", "description": "Versioned local index of answers, evidence references and unresolved assessments; authoritative source records remain externally mastered.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with namespace and revision first; governed external URI next; otherwise opaque local UUID with reconciliation status. Use stable entry IDs and revision sequences.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-criteria", "name": "Eligibility and award criteria", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "findings": [ { "id": "finding-criteria", "name": "Declared assessment basis", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "questions": [ { "id": "q-criteria-1", "text": "Which eligibility requirements and evidence apply to each participant category?", "kind": "requirement", "answer_data": [ "eligibility: criteria, evidence requirements, profile, exceptions, verification status", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-criteria-2", "text": "Which award criteria and decision method were disclosed or otherwise authorized?", "kind": "decision", "answer_data": [ "criteria: version, price and quality factors, weights if applicable, scoring method, tie rule", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-criteria-3", "text": "What review checks the criteria version against the version actually used in evaluation?", "kind": "validation", "answer_data": [ "criterion control: approved revision, applied revision, differences, rationale, reviewer", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-criteria-1", "name": "eligibility", "description": "Candidate answer group: eligibility: criteria, evidence requirements, profile, exceptions, verification status. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "data-criteria-2", "name": "criteria", "description": "Candidate answer group: criteria: version, price and quality factors, weights if applicable, scoring method, tie rule. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "data-criteria-3", "name": "criterion control", "description": "Candidate answer group: criterion control: approved revision, applied revision, differences, rationale, reviewer. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-criteria", "name": "Eligibility and award criteria register", "description": "Versioned local index of answers, evidence references and unresolved assessments; authoritative source records remain externally mastered.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with namespace and revision first; governed external URI next; otherwise opaque local UUID with reconciliation status. Use stable entry IDs and revision sequences.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-participation", "name": "Participants and submissions", "description": "Procurement context for participants and submissions.", "rationale": "Authored concern grouping grounded in cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-participants", "name": "Participants and impartiality", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "findings": [ { "id": "finding-participants", "name": "Qualified participant roles", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "questions": [ { "id": "q-participants-1", "text": "Who participates as bidder, consortium member, representative or evaluator?", "kind": "relationship", "answer_data": [ "participants: party master references, role, group membership, mandate, time scope", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-participants-2", "text": "What evidence supports each qualification or exclusion assessment?", "kind": "evidence", "answer_data": [ "qualification: evidence references, assessment, decision role, reasons, challenge status", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-participants-3", "text": "How are conflicts of interest declared and managed without unnecessary personal disclosure?", "kind": "privacy", "answer_data": [ "impartiality: declaration reference, reviewer, recusal or mitigation, access scope, unresolved risk", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-participants-1", "name": "participants", "description": "Candidate answer group: participants: party master references, role, group membership, mandate, time scope. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "data-participants-2", "name": "qualification", "description": "Candidate answer group: qualification: evidence references, assessment, decision role, reasons, challenge status. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "data-participants-3", "name": "impartiality", "description": "Candidate answer group: impartiality: declaration reference, reviewer, recusal or mitigation, access scope, unresolved risk. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-participants", "name": "Participants and impartiality register", "description": "Versioned local index of answers, evidence references and unresolved assessments; authoritative source records remain externally mastered.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with namespace and revision first; governed external URI next; otherwise opaque local UUID with reconciliation status. Use stable entry IDs and revision sequences.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-custody", "name": "Submission and custody", "description": "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.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008" ], "findings": [ { "id": "finding-custody", "name": "Submission receipt and access evidence", "description": "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.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008" ], "questions": [ { "id": "q-custody-1", "text": "What receipt evidence identifies the submitted version and its claimed arrival time?", "kind": "event", "answer_data": [ "receipt: submission ID, version, receipt ID, event and ingestion times, offset, integrity evidence", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-custody-2", "text": "Which custody policy governs access and what evidence supports any authorized opening?", "kind": "security", "answer_data": [ "custody: applicable seal policy, access role, opening authorization, time, audit reference, breach status", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-custody-3", "text": "How are late, replaced or withdrawn submissions preserved and assessed under the applicable rule?", "kind": "lifecycle", "answer_data": [ "submission history: supersession or withdrawal reference, timing, rule, decision, unresolved status", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-custody-1", "name": "receipt", "description": "Candidate answer group: receipt: submission ID, version, receipt ID, event and ingestion times, offset, integrity evidence. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008" ] }, { "id": "data-custody-2", "name": "custody", "description": "Candidate answer group: custody: applicable seal policy, access role, opening authorization, time, audit reference, breach status. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008" ] }, { "id": "data-custody-3", "name": "submission history", "description": "Candidate answer group: submission history: supersession or withdrawal reference, timing, rule, decision, unresolved status. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-custody", "name": "Submission and custody register", "description": "Versioned local index of answers, evidence references and unresolved assessments; authoritative source records remain externally mastered.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with namespace and revision first; governed external URI next; otherwise opaque local UUID with reconciliation status. Use stable entry IDs and revision sequences.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-selection", "name": "Evaluation and outcomes", "description": "Procurement context for evaluation and outcomes.", "rationale": "Authored concern grouping grounded in cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "layer-evaluation", "name": "Evaluation and exceptions", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-evaluation", "name": "Evidence-backed assessment record", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-evaluation-1", "text": "Which authorized evaluators assessed which submissions against which criteria version?", "kind": "process", "answer_data": [ "evaluation: reviewer roles, submission versions, criteria version, assessment stages, timestamps", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-evaluation-2", "text": "What scores or comparisons follow from the recorded inputs and calculation method?", "kind": "measurement", "answer_data": [ "assessment: criterion results, units, currency conversion basis, precision, formula version, uncertainty", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-evaluation-3", "text": "Which inconsistencies or integrity concerns remain unresolved before a decision?", "kind": "quality", "answer_data": [ "issues: missing evidence, outliers, suspected misconduct, clarification requests, escalation, disposition", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-evaluation-1", "name": "evaluation", "description": "Candidate answer group: evaluation: reviewer roles, submission versions, criteria version, assessment stages, timestamps. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ] }, { "id": "data-evaluation-2", "name": "assessment", "description": "Candidate answer group: assessment: criterion results, units, currency conversion basis, precision, formula version, uncertainty. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ] }, { "id": "data-evaluation-3", "name": "issues", "description": "Candidate answer group: issues: missing evidence, outliers, suspected misconduct, clarification requests, escalation, disposition. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-evaluation", "name": "Evaluation and exceptions register", "description": "Versioned local index of answers, evidence references and unresolved assessments; authoritative source records remain externally mastered.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with namespace and revision first; governed external URI next; otherwise opaque local UUID with reconciliation status. Use stable entry IDs and revision sequences.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-award", "name": "Award and contract handoff", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "findings": [ { "id": "finding-award", "name": "Authorized outcome and separate contract", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "questions": [ { "id": "q-award-1", "text": "What authorized outcome applies to each lot and participant?", "kind": "decision", "answer_data": [ "outcome: award or cancellation ID, scope, selected submissions if applicable, suppliers, reasons, authority", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-award-2", "text": "What notification evidence and profile-specific waiting conditions qualify the outcome?", "kind": "temporal", "answer_data": [ "notification: recipient, dispatch and receipt, waiting rule or exception, time basis, unresolved effect", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-award-3", "text": "Which resulting contract references have been confirmed and which handoffs remain pending?", "kind": "relationship", "answer_data": [ "handoff: award ID, contract master IDs, formation evidence, unresolved cardinality, responsible recipient", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-award-1", "name": "outcome", "description": "Candidate answer group: outcome: award or cancellation ID, scope, selected submissions if applicable, suppliers, reasons, authority. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "data-award-2", "name": "notification", "description": "Candidate answer group: notification: recipient, dispatch and receipt, waiting rule or exception, time basis, unresolved effect. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "data-award-3", "name": "handoff", "description": "Candidate answer group: handoff: award ID, contract master IDs, formation evidence, unresolved cardinality, responsible recipient. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-award", "name": "Award and contract handoff register", "description": "Versioned local index of answers, evidence references and unresolved assessments; authoritative source records remain externally mastered.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with namespace and revision first; governed external URI next; otherwise opaque local UUID with reconciliation status. Use stable entry IDs and revision sequences.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-assurance", "name": "Review and securities", "description": "Procurement context for review and securities.", "rationale": "Authored concern grouping grounded in cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-review", "name": "Challenges and correction", "description": "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.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-review", "name": "Review status without assumed legal effect", "description": "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.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "questions": [ { "id": "q-review-1", "text": "Which body and applicable rule govern a procurement challenge?", "kind": "authority", "answer_data": [ "review basis: forum reference, jurisdiction or policy, standing assessment, filing rule, source", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-review-2", "text": "What evidence establishes whether the challenged action is suspended, corrected or still effective?", "kind": "state", "answer_data": [ "effect: disputed act, order reference, asserted effect, time scope, uncertainty", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-review-3", "text": "How does the review outcome affect procurement revisions or a separately identified new process?", "kind": "lifecycle", "answer_data": [ "review result: case reference, outcome evidence, affected revisions, reopening or restart link", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-review-1", "name": "review basis", "description": "Candidate answer group: review basis: forum reference, jurisdiction or policy, standing assessment, filing rule, source. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "data-review-2", "name": "effect", "description": "Candidate answer group: effect: disputed act, order reference, asserted effect, time scope, uncertainty. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "data-review-3", "name": "review result", "description": "Candidate answer group: review result: case reference, outcome evidence, affected revisions, reopening or restart link. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-review", "name": "Challenges and correction register", "description": "Versioned local index of answers, evidence references and unresolved assessments; authoritative source records remain externally mastered.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with namespace and revision first; governed external URI next; otherwise opaque local UUID with reconciliation status. Use stable entry IDs and revision sequences.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-security", "name": "Tender and performance securities", "description": "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.", "source_refs": [ "SRC-003", "SRC-008" ], "findings": [ { "id": "finding-security", "name": "Conditional security assurance references", "description": "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.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "q-security-1", "text": "Which tender or performance security is required by the applicable profile and at what stage?", "kind": "constraint", "answer_data": [ "security requirement: kind, purpose, applicable rule, requirement or waiver, stage", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-security-2", "text": "What instrument evidence supports the claimed amount, issuer and validity?", "kind": "evidence", "answer_data": [ "instrument: master reference, issuer and beneficiary, amount and currency, terms, expiry, verification state", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-security-3", "text": "Which authorized source establishes an extension, release or claim against the security?", "kind": "event", "answer_data": [ "security event: instrument reference, action, decision evidence, effective time, disputed status", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-security-1", "name": "security requirement", "description": "Candidate answer group: security requirement: kind, purpose, applicable rule, requirement or waiver, stage. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] }, { "id": "data-security-2", "name": "instrument", "description": "Candidate answer group: instrument: master reference, issuer and beneficiary, amount and currency, terms, expiry, verification state. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] }, { "id": "data-security-3", "name": "security event", "description": "Candidate answer group: security event: instrument reference, action, decision evidence, effective time, disputed status. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-security", "name": "Tender and performance securities register", "description": "Versioned local index of answers, evidence references and unresolved assessments; authoritative source records remain externally mastered.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with namespace and revision first; governed external URI next; otherwise opaque local UUID with reconciliation status. Use stable entry IDs and revision sequences.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-continuity", "name": "Disclosure and exchange", "description": "Procurement context for disclosure and exchange.", "rationale": "Authored concern grouping grounded in cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-disclosure", "name": "Disclosure and record continuity", "description": "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.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006", "SRC-008" ], "findings": [ { "id": "finding-disclosure", "name": "Controlled views and retention", "description": "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.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006", "SRC-008" ], "questions": [ { "id": "q-disclosure-1", "text": "Who is accountable for the procurement file and what separate rights remain over submitted material?", "kind": "ownership", "answer_data": [ "stewardship: custodian role, authority basis, contributor rights, permissions, disputes", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-disclosure-2", "text": "Which recipient-specific view is authorized for this disclosure or audit request?", "kind": "access", "answer_data": [ "view: recipient, purpose, scope, legal or policy basis, redactions, decision, expiry", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-disclosure-3", "text": "What retention schedule and holds govern disposition of each procurement record and copy?", "kind": "retention", "answer_data": [ "disposition: record class, schedule, trigger, holds, authorization, erasure or tombstone evidence", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-disclosure-1", "name": "stewardship", "description": "Candidate answer group: stewardship: custodian role, authority basis, contributor rights, permissions, disputes. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-006", "SRC-008" ] }, { "id": "data-disclosure-2", "name": "view", "description": "Candidate answer group: view: recipient, purpose, scope, legal or policy basis, redactions, decision, expiry. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-006", "SRC-008" ] }, { "id": "data-disclosure-3", "name": "disposition", "description": "Candidate answer group: disposition: record class, schedule, trigger, holds, authorization, erasure or tombstone evidence. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-disclosure", "name": "Disclosure and record continuity register", "description": "Versioned local index of answers, evidence references and unresolved assessments; authoritative source records remain externally mastered.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with namespace and revision first; governed external URI next; otherwise opaque local UUID with reconciliation status. Use stable entry IDs and revision sequences.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-projection", "name": "Provenance and exchange", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-projection", "name": "Traceable projections and acceptance gaps", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007" ], "questions": [ { "id": "q-projection-1", "text": "Which source revisions and transformations support each published or exchanged assertion?", "kind": "provenance", "answer_data": [ "lineage: source record IDs, revisions, actor, derivation, event time, ingestion time, uncertainty", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-projection-2", "text": "What pinned exchange profile preserves the selected view and reports mapping losses?", "kind": "interoperability", "answer_data": [ "mapping: target standard version, extensions, mapping version, omitted fields, loss report", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-projection-3", "text": "Which checks and unresolved failures qualify this projection for its intended use?", "kind": "validation", "answer_data": [ "acceptance: schema result, semantic review, reference resolution, permission checks, failed cases, approver", "Include source evidence, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-projection-1", "name": "lineage", "description": "Candidate answer group: lineage: source record IDs, revisions, actor, derivation, event time, ingestion time, uncertainty. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "data-projection-2", "name": "mapping", "description": "Candidate answer group: mapping: target standard version, extensions, mapping version, omitted fields, loss report. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "data-projection-3", "name": "acceptance", "description": "Candidate answer group: acceptance: schema result, semantic review, reference resolution, permission checks, failed cases, approver. Nested profile schema and cardinalities require implementation review.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-projection", "name": "Provenance and exchange register", "description": "Versioned local index of answers, evidence references and unresolved assessments; authoritative source records remain externally mastered.", "media_or_form": [ "structured register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with namespace and revision first; governed external URI next; otherwise opaque local UUID with reconciliation status. Use stable entry IDs and revision sequences.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "resolve-process", "name": "Resolve a process reference", "description": "Proposed operation, not implemented. Resolve exact namespace and identifier; similarity never authorizes merging procurements.", "inputs": [ "process reference", "namespace", "authorized purpose" ], "outputs": [ "resolved reference or ambiguity report" ], "preconditions": [ "Verified actor role, purpose and record-level access; unresolved authority causes refusal", "Source evidence and applicable profile are identified; no fabrication of missing legal effects", "For mutation, expected revision and idempotency key must match; fail without partial writes" ], "effects": [ "Read-only reference resolution" ], "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "record-solicitation", "name": "Record solicitation evidence", "description": "Proposed operation, not implemented. Append an existing notice or amendment reference with audience and version; do not publish or transmit it.", "inputs": [ "process ID", "notice or amendment evidence", "audience and deadline profile" ], "outputs": [ "solicitation index revision or refusal" ], "preconditions": [ "Verified actor role, purpose and record-level access; unresolved authority causes refusal", "Source evidence and applicable profile are identified; no fabrication of missing legal effects", "For mutation, expected revision and idempotency key must match; fail without partial writes" ], "effects": [ "Append a local evidenced reference, preserving earlier revisions" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "record-submission-receipt", "name": "Record submission receipt evidence", "description": "Proposed operation, not implemented. Index an existing receipt and custody assertion without opening protected content or accepting the bid.", "inputs": [ "submission ID and revision", "receipt evidence", "custody authorization" ], "outputs": [ "receipt index revision or refusal" ], "preconditions": [ "Verified actor role, purpose and record-level access; unresolved authority causes refusal", "Source evidence and applicable profile are identified; no fabrication of missing legal effects", "For mutation, expected revision and idempotency key must match; fail without partial writes" ], "effects": [ "Append local receipt metadata; preserve unknown admissibility" ], "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "prepare-evaluation-view", "name": "Prepare an evaluation view", "description": "Proposed operation, not implemented. Assemble authorized assessment inputs and unresolved differences. This proposed function performs no ranking, exclusion or award decision.", "inputs": [ "permitted submission revisions", "approved criteria version", "reviewer scope" ], "outputs": [ "local assessment view and issue list or refusal" ], "preconditions": [ "Verified actor role, purpose and record-level access; unresolved authority causes refusal", "Source evidence and applicable profile are identified; no fabrication of missing legal effects", "For mutation, expected revision and idempotency key must match; fail without partial writes" ], "effects": [ "Create a local restricted view with lineage; no master decision change" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ] }, { "id": "record-outcome-link", "name": "Record an outcome and handoff link", "description": "Proposed operation, not implemented. Reference an existing authorized outcome and any confirmed contract; do not award, notify, sign or spend.", "inputs": [ "outcome and authority evidence", "scope and participant references", "contract references if available" ], "outputs": [ "outcome index revision or refusal" ], "preconditions": [ "Verified actor role, purpose and record-level access; unresolved authority causes refusal", "Source evidence and applicable profile are identified; no fabrication of missing legal effects", "For mutation, expected revision and idempotency key must match; fail without partial writes" ], "effects": [ "Append decision references and unresolved legal-effect assertions" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "record-review-or-security-event", "name": "Record review or security evidence", "description": "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.", "inputs": [ "source event and instrument or case reference", "authority and effect evidence", "affected procurement revision" ], "outputs": [ "assurance index revision or refusal" ], "preconditions": [ "Verified actor role, purpose and record-level access; unresolved authority causes refusal", "Source evidence and applicable profile are identified; no fabrication of missing legal effects", "For mutation, expected revision and idempotency key must match; fail without partial writes" ], "effects": [ "Append local effect assertions with disputed or unknown status preserved" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "prepare-authorized-projection", "name": "Prepare an authorized procurement projection", "description": "Proposed operation, not implemented. Build a local recipient-scoped export with pinned mapping and a loss report; no upload, notification or disclosure expansion.", "inputs": [ "recipient authorization", "procurement revision", "mapping and target profile" ], "outputs": [ "local projection and validation report or refusal" ], "preconditions": [ "Verified actor role, purpose and record-level access; unresolved authority causes refusal", "Source evidence and applicable profile are identified; no fabrication of missing legal effects", "For mutation, expected revision and idempotency key must match; fail without partial writes" ], "effects": [ "Create local export with redaction and provenance manifest" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] } ], "composition": [ { "target": "WM-ORG-001", "relation": "REFERENCE", "purpose": "Candidate party master for buyers, procuring entities, bidders and issuers; verify and pin before use. Local roles do not replace organization identity.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "WM-PER-001", "relation": "REFERENCE", "purpose": "Candidate person master for individual bidders, representatives and evaluators; identities and personal rights remain separate.", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] }, { "target": "WM-ECO-006", "relation": "REFERENCE", "purpose": "Optional resulting commercial contract master. Replace legacy mandatory composition and one-to-one assumption with evidenced handoff references; performance and payment stay outside.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "WM-ECO-002", "relation": "REFERENCE", "purpose": "Candidate valuation master for estimates or currency conversion evidence; no local valuation engine.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-POL-009", "relation": "REFERENCE", "purpose": "Optional court or arbitration case for a challenge; administrative review may use a different record and is not forced into litigation.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "WM-POL-010", "relation": "REFERENCE", "purpose": "Candidate forum identity and competence reference, separate from an individual review case; legacy A19 is ambiguous.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "WM-POL-013", "relation": "REFERENCE", "purpose": "Candidate registry mandate only when a disclosure profile requires it. Legacy public-register alias does not prove every tender needs this binding.", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "target": "WM-XCT-001", "relation": "REFERENCE", "purpose": "Candidate stewardship policy binding. Custody and opening do not transfer ownership; rights and policy evidence remain required.", "required": false, "source_refs": [ "SRC-006", "SRC-008" ] }, { "target": "WM-XCT-002", "relation": "REFERENCE", "purpose": "Candidate access grant or consent binding; procurement access may depend on other legal bases and is not presumed to rest on consent.", "required": false, "source_refs": [ "SRC-008" ] }, { "target": "WM-XCT-004", "relation": "REFERENCE", "purpose": "Candidate access-audit record link; procurement event facts remain local while generic access audit semantics stay external.", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] }, { "target": "OCDS 1.1.5", "relation": "ALIGN", "purpose": "Selected public-data concepts; lots and bid details require pinned extensions. No complete schema mapping or disclosure authorization follows.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "UBL 2.3", "relation": "ALIGN", "purpose": "Selected pre-award message roles and contract handoff only; no implemented XML binding or conformance claim.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "UNCITRAL Model Law 2011", "relation": "ALIGN", "purpose": "Policy-level conceptual comparison, not enacted law or a jurisdictional compliance claim; full legal verification remains open.", "required": false, "source_refs": [ "SRC-004", "SRC-008" ] }, { "target": "PROV-O 2013-04-30", "relation": "ALIGN", "purpose": "Evidence attribution and revision links without truth or legal-effect certification.", "required": false, "source_refs": [ "SRC-006" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Accountable procuring role and procurement file custodian with evidenced authority", "Applicable public-law or private procurement profile, versions and exceptions", "Master namespaces, role separation, access decisions, retention schedule and escalation path" ], "namespace_guidance": "Use master-qualified process IDs with distinct lot, submission, award and release IDs. Preserve aliases with evidence; do not use names or dates as sole identifiers.", "registry_links": [ "vr.wm-eco-007", "All candidate neighbor bindings need verified identity, boundary and version pins" ] }, "canon_and_patch": { "canonicalization_rules": [ "Resolve identifiers within their namespaces; never merge processes by supplier, title or price similarity.", "Keep declared, observed, disputed and unknown assertions distinct; award status is not contract formation." ], "patch_rules": [ "Use expected revision, idempotency key, actor, purpose and source evidence for each local append or correction.", "Retain supersession links while permitting lawful payload erasure; corrections must not silently replace evaluation criteria or source documents." ], "compatibility_rules": [ "Version profiles and projections; refuse mappings that lose required confidentiality, scope, authority or time qualifiers." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with namespace and revision", "Governed stable external URI with version", "Local UUID with explicit reconciliation state" ], "timestamp_rule": "Record event and ingestion instants in RFC 3339 with seconds and an explicit UTC offset or Z. Preserve receipt, opening, notification and asserted effect separately. Keep original precision, date-only values and timezone/calendar rules; never invent midnight or treat an unknown offset as known.", "serial_naming_rule": "Use opaque process key, artifact type, stable entry ID and revision sequence; avoid bidder names or protected content in filenames.", "integrity_rule": "Record hash algorithm, digest and transformation lineage when available. A digest or recorded seal state proves neither uninterrupted custody nor admissibility or signature authority." }, "policies": [ "Reviewable draft under the owner-authorized single-provider waiver; external independent review and source/version verification remain holds.", "Apply jurisdiction and private-policy rules explicitly; no universal deadline, standstill, exclusion, sealing or disclosure rule is executable here.", "Keep bid contents and integrity concerns restricted to authorized purposes; suspected misconduct is not an established finding of guilt.", "Restricted or dangerous subjects carry only policy and authorization references, never operational acquisition instructions.", "Proposed functions are local record operations; none publishes, opens sealed content, awards, signs, transfers money or enforces a guarantee." ], "crud": { "read": [ "Verify purpose and recipient scope; preserve redactions, sources, uncertainty and confidentiality qualifiers." ], "create": [ "Require process namespace, custodian and scoped need; explicitly mark an incomplete authority or procedure profile as pending, blocking consequential action." ], "update": [ "Append supported revisions with concurrency control and source evidence; preserve supersession, withdrawals and disputes." ], "delete": [ "Apply the approved retention schedule, legal holds and lawful erasure decisions to every payload and copy; retain only a minimal non-identifying tombstone where lawful.", "Local disposal cannot cancel a procurement, erase an external master or annul a contract; no perpetual personal-data audit retention is assumed." ] }, "roles": [ { "name": "Procurement custodian", "responsibilities": [ "Maintain qualified identity and controlled record continuity" ] }, { "name": "Authorized procurement officer", "responsibilities": [ "Record evidenced events within mandate and procedure profile" ] }, { "name": "Evaluation reviewer", "responsibilities": [ "Assess authorized inputs and record reasons without bypassing approval" ] }, { "name": "Award authority", "responsibilities": [ "Provide independently evidenced outcome decisions within delegation" ] }, { "name": "Records and access officer", "responsibilities": [ "Approve disclosure scope, retention, holds and disposition" ] }, { "name": "Bidder or representative", "responsibilities": [ "Supply evidence and access only the permitted participant view" ] }, { "name": "Review liaison", "responsibilities": [ "Link competent forum and case evidence without deciding legal effects" ] } ], "access": { "default_rule": "Deny protected content access unless recipient, purpose, stage and scope are authorized; public metadata does not open the full procurement file.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency, audit or review access needs an evidenced basis and minimum necessary scope; no unconditional full-file auditor bypass.", "Opening authorization changes permitted handling only as the profile states; bidder intellectual property and other rights are separately assessed." ], "audit_requirements": [ "Log protected reads, local exports, revisions and disposition with actor, purpose, scope, revision and result under a minimal-data retention policy." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md and accountable owner policies", "spec.yaml and publication holds", "Applicable procedure profile, verified source records and permitted view" ] } }, "coverage": { "claim": "A bounded source-grounded proposal for one persistent procurement proceeding, with profile-qualified selection, controlled submissions, evidenced outcomes and separate contract handoff. This is a reviewable draft, not universal coverage, operational procurement authority or certified conformance.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Persistent proceeding and separately scoped child identifiers; aliases need evidence." }, { "dimension": "lifecycle", "status": "covered", "notes": "Planning context through selection, cancellation, review and handoff; performance is external." }, { "dimension": "relationships", "status": "covered", "notes": "Multiple lots, participants and outcomes; optional contract, forum and case references." }, { "dimension": "temporal", "status": "covered", "notes": "Receipt, opening, notification, deadlines and legal effects are separate assertions." }, { "dimension": "provenance", "status": "covered", "notes": "Evidence attribution, source revision, transformation and uncertainty." }, { "dimension": "ownership", "status": "covered", "notes": "Role-based custodian; contributor rights do not transfer at opening." }, { "dimension": "validation", "status": "gap", "notes": "Research schema validation only; nested data schemas and jurisdiction acceptance tests remain open." }, { "dimension": "access", "status": "covered", "notes": "Stage- and recipient-scoped access with exceptions and redactions." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Profile schedules, holds, lawful erasure and minimal tombstones." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual OCDS, UBL and provenance alignments; actual bindings and fixtures unimplemented." }, { "dimension": "direct properties", "status": "covered", "notes": "Method, category, amount, scope and status are nonphysical process properties. Item measurements are delegated." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Master reference plus evidenced notice, receipt and decision events; absence of a public notice is not absence of a procurement." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Proposed local operations have role, evidence and revision preconditions; consequential actions remain external." }, { "dimension": "procedure diversity", "status": "gap", "notes": "Direct award is represented by profile and justification. Auctions, multi-stage dialogue, framework execution and sector regimes need deeper research." } ], "known_omissions": [ "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." ], "conflicts": [ "Legacy one-to-one award and contract relations are superseded by optional evidenced cardinalities.", "Legacy blanket sealed access, ownership transfer at opening and universal standstill claims are rejected; profile-specific authority governs." ], "regional_assumptions": [ "The public-policy sources are international guidance, not automatically enacted domestic law.", "UBL includes regional scenarios and OCDS targets disclosure; neither defines a universal private procurement workflow." ], "adversarial_checks": [ "No award, direct award, withdrawn submission and cancellation must be representable without manufactured bids or contracts.", "A multi-lot process with several awards must not merge party, lot, award or contract identifiers.", "A bidder cannot read competitor content merely because a notice is public or bids were opened.", "A challenge or local state update cannot establish suspension, contract formation or enforceable legal effect.", "A schema-valid export with missing authority, misleading timestamps or confidentiality loss must be refused." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "A procurement proceeding retains identity across revisions, selection, cancellation and review. Its indexed child records do not require an aggregate root classification. The registry standalone-mm value is a record-plane label; contract performance, parties, instruments and review cases remain independently mastered." }, "decisions": [ { "concept": "Persistent proceeding and scope", "disposition": "accepted", "rationale": "The identity and lifecycle questions preserve one proceeding through multiple events and outcomes. Demand and funding are scoped references, and contract execution remains outside." }, { "concept": "Competition-only legacy boundary", "disposition": "qualified", "rationale": "The registered Procurement subject can represent direct or restricted selection through an applicable profile and method rationale. This does not implement a private purchasing or payment system." }, { "concept": "Lot award and contract cardinalities", "disposition": "legacy assumptions rejected", "rationale": "Undivided procurement, no award, multiple awards and optional contract references remain expressible. There is no mandatory one-bid, one-award, one-contract chain." }, { "concept": "Criteria and participant authority", "disposition": "accepted with profile dependency", "rationale": "Qualification, responsiveness, award criteria and authority evidence stay distinct. The applied criteria version must be compared with the approved one; no universal weighting rule is asserted." }, { "concept": "Submission custody and ownership", "disposition": "legacy transfer rejected", "rationale": "Receipt, timeliness, admissibility and opening are distinct assertions. Sealing is procedure-dependent, and an opening event never implies transfer of intellectual property or other rights." }, { "concept": "Evaluation and local functions", "disposition": "accepted as proposed only", "rationale": "The seven unimplemented functions only resolve, index or prepare authorized local views. They cannot exclude, rank, award, publish, open sealed content, sign or spend; recorded assessments remain attributable evidence." }, { "concept": "Outcome notification and waiting periods", "disposition": "qualified", "rationale": "Questions request actual notification evidence and waiting rules or exceptions. No fixed standstill duration, legal effect from dispatch, or contract formation from an award is inferred." }, { "concept": "Review forum and ambiguous aliases", "disposition": "candidate bindings only", "rationale": "A forum and a case have separate roles; administrative review is not forced into litigation. Legacy S1, A19 and public-register mappings do not establish mandatory runtime dependencies." }, { "concept": "Tender and performance security", "disposition": "accepted at evidence level", "rationale": "Conditional requirements, distinct purposes, instrument references and effect evidence are sufficient for this boundary. The model cannot issue, enforce, release or guarantee the validity of a security." }, { "concept": "Direct properties and dangerous subjects", "disposition": "bounded", "rationale": "Method, category, values and states are process properties; item measurements are delegated. Restricted subjects carry policy and authorization references only, with no operational acquisition guidance." }, { "concept": "Disclosure retention and erasure", "disposition": "accepted with adopted policy", "rationale": "Recipient-specific views and minimal-data audit rules reject blanket auditor access. Revision continuity permits lawful payload erasure and does not require perpetual personal-data retention." }, { "concept": "Candidate fields and interoperability", "disposition": "operational conformance deferred", "rationale": "Optional object groups and conceptual alignments lack nested schemas, tested extensions and executable acceptance rules. These are explicit implementation holds rather than evidence of a complete operational specification." }, { "concept": "Source strength and currency", "disposition": "limited", "rationale": "Six browser-accessible bodies and two official indexed sources support selected concepts. Direct checks were not run, full legal retrieval is incomplete, and no current enacted legal profile is certified." }, { "concept": "Independent provider review", "disposition": "waived and held", "rationale": "Claude and Grok were skipped with zero attempts under the owner override. This frozen no-tools Codex self-audit adds no facts and is not independent corroboration or provider agreement." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex no-tools self-audit is not independent second-provider review.", "Live source and version verification is incomplete. Direct HTTP checks were not attempted under the owner-reported sandbox restriction: zero responses and zero HTTP 200 statuses were measured. Six document bodies were browser-accessible and two UNCITRAL sources used official indexed evidence; full legal texts and current adopted versions remain unverified. The coordinator must run check_sources.py outside the sandbox and review claim support.", "Jurisdiction, private procurement policy, legal applicability, licensing, confidentiality, rights, remedies, retention, sector restrictions and security conditions need qualified profile review before operational use. No compliance or legal-effect certification is claimed.", "Nested answer schemas, exact cardinalities, pinned neighbor bindings, OCDS extensions, UBL mappings, bid-custody assurance and adversarial instance acceptance tests remain incomplete. Proposed functions are unimplemented local operations.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "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." ] }, "statistics": { "sources": 8, "bundles": 7, "layers": 14, "findings": 14, "questions": 42, "artifacts": 14, "functions": 7 } }