docs: ECS vocabulary glossary (midpoint vs self-consistent) - #48
Draft
quint-mbbdigital wants to merge 2 commits into
Draft
docs: ECS vocabulary glossary (midpoint vs self-consistent)#48quint-mbbdigital wants to merge 2 commits into
quint-mbbdigital wants to merge 2 commits into
Conversation
Class B: orient readers on ECS intent classes and lineages without changing optimizer math or defaults. Points at OPTIMIZER_VARIANTS for actuators.
Document exact midpoint formula, F(m) participation-ratio SC backend (not free-fit MP edge), SETOL conceptual tier, small-SV caution, and Porter-Thomas vs bare PRE wording. Class B only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type
Summary
Add
docs/ECS_GLOSSARY.mdexplaining ECS intent classes and midpoint vs self-consistent lineages, with α=2 as boundary language and explicit “not the same as density target_alpha / μ_rank / MP q”. Link from the root README under Optimizer variants.Why
OPTIMIZER_VARIANTS.mdmaps actuators; it does not fully teach ECS vocabulary. Joint tables often collapse different ECS objects into one column.Definition surface
Docs only — no new backends, no default changes.
Prior art
#37 variants map remains SoT for package/actuator catalog.
Test plan
Out of scope
Optimizer mathematics; α_zc product claims; changing support formulas.