Energy Filament Theory · EFT Full KB

Gap and Alias Policy

V50-50.6 · D ·

If V50 has no keyed entry, ordinary non-EFT wording may be translated normally, while EFT-specific missing expressions stay pending rather than being promoted into canonical terminology.

Back to EFT Full KB index

AI retrieval note

Use this section as a compact machine-readable EFT reference.

Keywords: EFT, V50, canonical glossary, lock_level, MUST_LOCK, PREFERRED_UNIFIED, CONTEXTUAL, terminology authority, canonical naming, keyword normalization, alias registration, gap registration, E0001-E0261, E0199, E0200, terminology-fluency balance, Gap and Alias Policy, gap_alias_control_card

Section knowledge units

boundary

50.6 starts only after lookup against 50.5. If a keyed entry exists, apply that row’s lock_level. If no keyed entry exists, the absence of a hit does not authorize a new canonical form; it only opens a controlled pending branch.

boundary

The no-hit branch splits in two. If the concept is ordinary physics or ordinary prose and V50 does not list it, normal translation is allowed. If the expression still appears EFT-specific, it remains pending and should not be promoted silently into cross-volume terminology.

interface

When V50 already has a canonical entry, older source wording, half-translations, English-side placeholders, and other legacy variants may survive only as alias-side traces: source_anchor.heading, alt_term, legacy_source_alias, or explicit batch-log explanation. They do not take the main canonical lane.

summary

Gap registration stays inside the existing schema: use the term-gap register, process-state notes, and batch/release manifest as auxiliary traces; do not invent a new record type. Recommended fields are gap_id, source_form, provisional_local, category_pred, affected_sections, first_seen_source, reason, status, and resolution_owner. E0199 and E0200 remain missing/reserved key gaps.