looker_ingest

1# Looker Runtime Ingest
2 
3Looker runtime ingest turns API-staged dashboards, Looks, and explores into durable ktx memory. Runtime entities are evidence. They are not themselves the final knowledge shape.
4 
5## Required Workflow
6 
71. Read every `rawFiles` entry for the WorkUnit.
82. Read relevant `dependencyPaths` before making a decision. For dashboard and Look WUs this usually includes the referenced explore JSON, signal files, `folders/tree.json`, and `users/<id>.json`.
93. Treat `signals/*.json`, owners, folders, schedules, and favorites as prioritization or provenance context only.
104. Extract generalizable metric formulas, segment definitions, field semantics, and domain conventions.
115. Use `wiki_search`, `sl_discover`, and `sl_read_source` before writing so new content merges with existing memory instead of duplicating it.
126. Use `context_evidence_search` or `context_evidence_read` to obtain evidence chunk IDs for any wiki-bound knowledge candidate.
137. Use `context_candidate_write` for durable wiki-bound knowledge. Do not call `wiki_write` from a Looker WorkUnit; Stage 4 reconciliation promotes candidates and writes wiki pages.
148. Use `looker_query_to_sl` for each Look query or dashboard tile query that has a `query` object.
15…