CIEL Lab Wiki¶
CIEL Lab is a workspace for maintaining the CIEL concept dictionary: inspect terminology content, run repeatable quality checks, stage fixes, manage translations, and prepare releases without losing the audit trail back to OCL.
This wiki explains the product as it exists in the codebase and records the operational knowledge that had previously lived across source code, issue threads, and Slack conversations.
Choose a task¶
| If you need to… | Start here |
|---|---|
| Understand the complete system | Architecture overview |
| Learn the interface | Product tour |
| Find and update a concept | Concept Manager |
| Find an external terminology code | Code Search |
| Check the current CIEL HEAD | Quality assurance |
| Resume a long QA review | Bulk Validation |
| Prepare a release | Release workflow |
| Use CIEL Lab from an AI client | MCP App |
| Operate terminology loaders and exports | CIEL scripts |
Search is local and complete¶
Use the search box or Cmd+K. Material for MkDocs builds a Lunr-compatible index from every page and loads it in the browser. Search is:
- full-text and instant;
- aware of page titles, headings, and body text;
- typo-suggesting, highlighted, and shareable;
- independent of Algolia or another hosted search service.
The index covers written documentation, captions, and video descriptions. Video speech is not searchable until a transcript is added to its page.
How the product fits together¶
CIEL Lab combines a React application, a FastAPI/GraphQL backend, OCL, cached HEAD data, terminology loaders, vector search, and asynchronous workers. The short version is:
- OCL remains the source of truth.
- CIEL Lab caches and indexes content so review tools stay responsive.
- Quality checks and user actions create reviewable reports or worklists.
- Human reviewers approve changes before they are written to OCL.
- Release automation produces diffs and SQL artifacts from an approved state.
See the system infographic for the full data flow.
Documentation scope
This is operational guidance, not a replacement for OCL authorization or release governance. Features that mutate OCL require a user-specific OCL API token and the appropriate permission.