Artifacts
Compare Semogram datasets, fact sets, predictions and recommendations. Inspect storage classes, contracts, output lineage and review state.
Artifacts are the durable outputs runs leave behind: datasets, fact sets, predictions, recommendations — each with lineage, storage rules, and review state.
Artifact kinds
| Kind | Holds | Example |
|---|---|---|
| Table / dataset | Structured rows | Forecast scores table |
| Parquet / JSON / file | Serialized payloads | Exported feature file |
| Ontology fact-set manifest | Prediction-ready grouped facts | Account feature manifest |
| Manifest | Pointers over other artifacts | Run output index |
| Other | Other payloads, with semantic type and contract | Decision-facing outputs |
Artifact physical kind and contract kind are separate. Predictions, recommendations, and reviews are contract kinds, not physical artifact kinds. The JSON below is an artifact-contract fragment, not an artifact creation request.
Storage classes
| Class | Meaning | Use for |
|---|---|---|
| Ephemeral | May expire; carries an expiry time | Previews, intermediates |
| Persisted | Kept under retention rules | Committed outputs |
| External | Lives outside Semogram, referenced by URI | Warehouse tables, file drops |
Contracts
| Field | Meaning |
|---|---|
| Kind | Rows, fact sets, assertions, signals, features, predictions, recommendations, reviews |
| Fields | Named, typed, nullable/required columns with descriptions |
| Primary key | Row identity for downstream joins |
| Evidence requirements | Whether citations, source artifacts, or source records are mandatory |
In Pipeline Studio, ask the assistant:
Prepare the output artifact contract. Kind: predictions; Name: renewal-risk-scores; Fields: [{"name": "account_id", "type": "string", "required": true}, {"name": "risk", "type": "number", "required": true}, {"name": "drivers", "type": "string", "nullable": true, "description": "Top reasons cited"}]; Primary key: ["account_id"]; Evidence / Citations: Enabled; Evidence / Source record ids: Enabled. Use the actual accessible resources and required enclosing definition. Show the proposed settings and validate them before saving or executing.This request describes the example’s intent; review the generated contract and any required permissions. It does not create missing resources or make an unsupported operation available.
This is a serialized configuration/contract fragment, not a complete UI workflow. Use it only in the enclosing operation or advanced editor described on this page.
{
"kind": "predictions",
"name": "renewal-risk-scores",
"fields": [
{ "name": "account_id", "type": "string", "required": true },
{ "name": "risk", "type": "number", "required": true },
{ "name": "drivers", "type": "string", "nullable": true, "description": "Top reasons cited" }
],
"primaryKey": ["account_id"],
"evidence": { "citations": true, "sourceRecordIds": true }
}Lineage and review
| Field | Meaning |
|---|---|
| Produced by | Run, node, and upstream artifact IDs where recorded — verify coverage |
| Namespace / ontology package | Which model or domain it belongs to |
| Review state | Approved, corrected, or rejected with reasons |
Choosing well
- Ephemeral for previews, persisted for commitments, external where teams already read.
- Demand evidence requirements on anything feeding decisions.
- Inspect lineage coverage. Source artifacts can legitimately have no upstream artifact parents, and transforms can declare that they drop lineage.