Origin Kind
Origin Kind
Section titled “Origin Kind”Definition
Section titled “Definition”Planned closed enumeration on q_a_pairs.origin_kind capturing the provenance route by which a Q&A pair entered the corpus: extracted from existing content, curated explicitly by a SME, derived from a prior bid response (and thus may carry response context), or imported from a legacy data set. Pipeline-side, platform-internal vocabulary. CORE per §6.2.
Synonyms / Acronyms
Section titled “Synonyms / Acronyms”None.
Baseline values
Section titled “Baseline values”| key | label | provenance |
|---|---|---|
| extracted_from_corpus | Extracted From Corpus | core |
| curated_explicit | Curated Explicit | core |
| derived_from_bid_response | Derived From Bid Response | core |
| imported_legacy | Imported Legacy | core |
Relationships
Section titled “Relationships”q_a_pairs.origin_kind— planned column (q_a_pairs table promotion pending per S16 spike).- Adjacent to
q_a_pairs.source_workspace_id(nullable, provenance audit only per Q-OQR1-07): the originating workspace iforigin_kind='derived_from_bid_response'. - Adjacent to
q_a_pairs.dedup_status(CV 07) andscope_tag[](CV 21). - Layer 5: q_a_pairs is the canonical Layer-5 “citable fact” entity (per source §3.5).
Consumers
Section titled “Consumers”- Q&A pair management UI surfaces (planned).
- Provenance / audit trails — origin_kind drives “where did this Q&A come from?” surfaces.
lib/mcp/tools/search.ts,lib/mcp/tools/content.ts— future MCP filter when column lands.- Q-OQR1-08 deferred private-q_a_pairs work in v1.1 may extend.
- Status: planned — column not yet in production schema; awaits the q_a_pairs table promotion (S16 spike per source §3.5).
- Closed CV; schema migration adds new values.
- Per Q-OQR1-06 + Q-OQR1-07 ratification,
source_workspace_idis nullable provenance audit, not the scoping mechanism.