Skip to content

OIC-GC-005 — Procurement preflight corpus selection and provenance #9

Description

@veraxis-protocol

Owner

Arkadiy Miteiko / Veraxis for corpus authorization and scope; Codex may perform bounded research, acquisition, inventory, and provenance preparation.

Required inputs

  • Bounded public or synthetic procurement use-case criteria.
  • Source candidates, access terms, provenance metadata, hashes, and handling restrictions.
  • Existing preflight SOURCE_MANIFEST.csv contract and Lab restrictions.

Required outputs

  • Proposed bounded corpus inventory.
  • Completed rights/provenance records for selected candidates.
  • Acquisition and hashing evidence, exclusions, uncertainty log, and reviewer-ready source manifest proposal.

Acceptance criteria

  • Every candidate has source, jurisdiction, date/version, acquisition method, digest, rights basis, and redistribution/use constraints recorded.
  • Confidential, privileged, regulated, export-controlled, and classified content is excluded.
  • Unclear rights or provenance remains blocked rather than inferred.
  • Selection is reviewed before any extraction work.

Explicit non-goals

  • No Docling integration, LLM extraction, normative-unit extraction, admission, IR construction, or semantic interpretation.
  • No claim that the corpus is representative or benchmark-superior.

Dependencies

  • Licensing questions coordinate with OIC-GC-008.
  • Feeds OIC-GC-007.

Current gate impact

Preflight provenance is currently OPEN. Completion supplies owner-review evidence but does not itself open the semantic gate.

Metadata

Metadata

Assignees

No one assigned

    Labels

    corpusCorpus selection, rights, and provenancegate-closureGate Closure v0.2 work

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions