Skip to content

feat(psychometric): recover ESEM loadings and refuse reverse DSEM lags - #119

Draft
seonghobae wants to merge 1 commit into
mainfrom
agent/psychometric-esem-dsem-fit
Draft

feat(psychometric): recover ESEM loadings and refuse reverse DSEM lags#119
seonghobae wants to merge 1 commit into
mainfrom
agent/psychometric-esem-dsem-fit

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Summary

  • ADR 0005 still required a CPU f64 ESEM/DSEM fit path that does not treat raw topic proportions as Euclidean indicators.
  • Adds standalone psychometric_fit: OLS recovers known exploratory cross-loadings from admitted ALR/ILR/logistic-normal coordinates; recovered RMSE is below a zero-loading collapse.
  • DSEM lagged paths are admitted only when the predictor is strictly earlier in event time.
  • A good global fit cannot reclassify formative or network constructs as reflective.
  • Does not recreate psychometric_core (feat(psychometric): posterior ESEM input gates with true-parameter RMSE #49 owns input gates) and does not allocate migration 0007/0008 (#45 still owns 0007).

Claim boundary

  • OLS loading recovery and event-time lag gates only. Not rotation, posterior pooling, invariance, or a full ESEM/DSEM sampler.
  • Not a certification, attestation, or causal-identification claim.

Test plan

  • RED: esem_dsem_fit_contract failed before the crate existed
  • cargo test -p psychometric_fit --offline --lib --tests
  • cargo clippy -p psychometric_fit --all-targets --offline -- -D warnings
  • cargo llvm-cov -p psychometric_fit authored lines 108/108; nightly-2026-08-01 branches 30/30
  • docstring, workspace, and documentation gates
  • Exact-head CI and independent review

Add a standalone psychometric_fit crate that recovers exploratory
cross-loadings on a CPU f64 OLS path from admitted log-ratio coordinates
and refuses non-forward event-time DSEM lags. Does not recreate
psychometric_core or allocate migration 0008.
@coderabbitai

coderabbitai Bot commented Aug 16, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 1d94e3ee-819c-4a2b-997e-8b201edd8589

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

1 similar comment
@coderabbitai

coderabbitai Bot commented Aug 16, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 1d94e3ee-819c-4a2b-997e-8b201edd8589

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant