اِمْپُورْ import
Provenance
- #13 dataflow concept_map maps javascript/import → concept import
- #23 demo-alpha concept_map maps javascript/import → concept import
- #28 sealion-refinement concept_map maps javascript/import → concept import winning layer
Full per-leaf change history across brain builds is not yet recorded; shown is the current build's layer stack.
Across locales
What each covering migration carries for this concept, per locale — the whole-brain view, not filtered by your language. Forms are the migration's leaf values (pre-transform, pre-human-verdict); a locale without a form falls back to canonical English. Chips open that locale's live docs page for this term.
dataflow · concept import — per-locale forms
Expand to load the per-locale matrix.
demo-alpha · concept import — per-locale forms
Expand to load the per-locale matrix.
sealion-refinement · concept import — per-locale forms
Expand to load the per-locale matrix.
AI council review
Reviewed by 1 model
· @cf/aisingapore/gemma-sea-lion-v4-27b-it · 2026-07-17
Cluster dataflow
· locale mad-Arab
· member import
Using a direct transliteration of 'import' (اِمْپُورْ) is more common and clearer in technical contexts within Pegon. It avoids the semantic issues of 'ngèbet'.
Issue breakdown
- accuracy While 'ngèbet' can mean 'to want strongly', it doesn't capture the technical sense of 'importing' data or modules. It's too emotive.
- specificity Low. Lacks technical precision.