Concept ID
An opaque identifier such as C.SAFETY.WARNING that downstream systems can reference without relying on a display label.
Interlingua
Concept Interlingua
How a language-agnostic semantic layer separates vector neighborhoods from canonical concept identity, aliases, side channels, provenance, abstention, and render targets.
Language-agnostic layer
The interlingua is the concept layer between expression and output.
A semantic neighborhood is where candidate meanings cluster. A canonical concept identity is the stable record a system can hand off, audit, and render. Neurokinetic AI keeps those separate so vector proximity does not become an unreviewed truth claim.
Concept IDs are opaque by design. Human labels can change by language, domain, or interface, while the record can preserve aliases, side channels, provenance, confidence, versioning, and render targets.
Expression streams converge on a registry record, then fan out to target surfaces.
Concept record anatomy
A concept record carries more than a translated word.
Aliases
Human-facing labels, synonyms, domain phrases, and multilingual surfaces that can point at the same record.
Side channels
Tone, urgency, register, authority, locale, and domain constraints that matter but should not overwrite identity.
Provenance
Source expression, policy version, candidate evidence, confidence, and resolver history for audit trails.
Render targets
Natural language, compact symbol sequences, UAI-1 envelopes, search keys, review notes, or support macros.
Abstention
A resolution can fail cleanly when the input is ambiguous, culturally loaded, adversarial, or outside a known registry.
Versioning
Concept records evolve, but downstream systems need to know which version was used for a handoff.
Governance
Registry changes require ownership, review, rollback paths, and public boundaries for what the concept claims.
Resolution contract
The interlingua separates four things that ordinary translation collapses.
Candidate neighborhood
Dense, sparse, and late-interaction signals surface likely meanings without claiming final identity.
Residue and side channels
Language, tone, urgency, formality, locale, and authority are preserved as metadata instead of confused with the invariant.
Canonical concept ID
A registry record becomes the stable handoff target when the evidence passes the chosen threshold.
Render envelope
The receiving surface gets the target language, search key, review artifact, or protocol payload it can actually use.
Examples
Surface expression to concept to rendered output.
| Surface expression | Concept | Rendered output |
|---|---|---|
| Hello / Hola / Bonjour | C.GREETING.OPENINGCore invariant: open a social channel. | Localized greeting, support macro, or UAI-1 opening-intent envelope. |
| Caution / Cuidado / Attention | C.SAFETY.WARNINGCore invariant: prevent harmful action. | Safety warning with urgency and authority side channels preserved. |
| Run step two after approval | C.PROCEDURE.STEPCore invariant: move a task forward with a precondition. | Task instruction, workflow gate, or agent handoff record. |
| Find this policy in every supported language | C.SEARCH.CONCEPT_RETRIEVALCore invariant: retrieve by underlying construct. | Hybrid retrieval plan with dense/sparse evidence, language-residue score, and provenance trail. |