wassname/moral-maps
1
0
Fork 0
mirror of https://github.com/wassname/moral-maps.git synced 2026-09-09 11:27:22 +08:00
Code Issues Packages Projects Releases Wiki Activity

Require explicit showcase steering anchor

Browse Source
This commit is contained in:
wassname
2026-06-30 14:08:16 +08:00
parent fe3b0aff2c
commit 9fc3852a8a
3 changed files with 29 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/spec/20260630_readme_plots.md
+21 -19
View File
@@ -16,30 +16,31 @@ Out: changing eval semantics, changing dataset schemas, adding new metrics.
- R6: README range plots show the coherent coefficient path in sign lanes. Done means: all negative c values share a blue lane, base is black in the middle, and all positive c values share a red lane. Reversals/wraps are visible on the y-axis without marker-size encoding. VERIFY: inspect regenerated range PNGs and check `draw_steer` maps x by sign only.
## Tasks
- [ ] User ask checklist
- [/] User ask checklist
- [ ] Regenerate README plots from one unified artifact, not mixed old runs.
- [ ] Fix MFV plots, including the MFV normalization/range issue.
- [ ] Do not show 16PF in the README.
- [ ] README plot order: MFV first, Humor second, Big Five third, MFQ-2 last.
- [ ] Fix MFV plots, including the MFV normalization/range issue. Code reviewed; final proof is regenerated MFV images.
- [x] Do not show 16PF in the README showcase.
- [x] README plot order: MFV first, Humor second, Big Five third, MFQ-2 last.
- [ ] Make each plot clear about what is being steered and which direction is which.
- [ ] Titles/captions should say the actual axis/pole, not vague "authority axis" if sign is ambiguous.
- [ ] Red/blue should be explained: red is positive coefficient, blue is negative coefficient.
- [ ] Dots should not scale with `c`; intermediate points should be small/hollow, endpoints solid.
- [ ] Range plots should use sign lanes, not horizontal coefficient swim lanes.
- [ ] Coherence/path gate should show `0, +/-0.5, +/-1, +/-2...` only up to real coherence, not pmass-only fake coherence.
- [ ] Investigate the double-back separately as a calibration/gating problem.
- [ ] Investigate the small-steer MFV direction separately as persona/template/scenario/method failure.
- [/] Titles/captions should say the actual axis/pole, not vague "authority axis" if sign is ambiguous.
- [x] Treat direction as run-local: this README run can declare an MFV Authority anchor, but generic steering vectors stay `+c`/`-c` unless the run declares an anchor.
- [x] Red/blue should be explained: red is positive coefficient, blue is negative coefficient.
- [x] Dots should not scale with `c`; intermediate points should be small/hollow, endpoints solid.
- [x] Range plots should use sign lanes, not horizontal coefficient swim lanes.
- [x] Coherence/path gate should show `0, +/-0.5, +/-1, +/-2...` only up to real coherence, not pmass-only fake coherence.
- [x] Investigate the double-back separately as a calibration/gating problem.
- [x] Investigate the small-steer MFV direction separately as persona/template/scenario/method failure.
- [ ] Try/identify better persona/template/scenario selection from persona-steering-template-library, not just accept strict22.
- [ ] Keep selections committed in steering-lite, not persona library.
- [ ] Use steering-lite for the actual steering run and tinymfv for the eval/plots.
- [x] Keep current strict22 selection committed in steering-lite, not persona library.
- [x] Use steering-lite for the actual steering run and tinymfv for the eval/plots.
- [ ] Add README table with profile shift normalized to human variation plus reader-logit change/noise, per dataset/axis.
- [ ] Make "Moral Foundations" unambiguous: MFV vignettes versus MFQ-2 survey.
- [ ] Link dataset table entries to committed JSON/CSV files.
- [ ] Keep README simple: what it is, why useful, datasets, metric/API, plots.
- [ ] Use one main README metric: `profile`; keep other metrics as support/API details.
- [ ] Define metrics cleanly with LaTeX that renders in GitHub markdown.
- [x] Make "Moral Foundations" unambiguous: MFV vignettes versus MFQ-2 survey.
- [x] Link dataset table entries to committed JSON/CSV files.
- [x] Keep README simple: what it is, why useful, datasets, metric/API, plots.
- [x] Use one main README metric: `profile`; keep other metrics as support/API details.
- [x] Define metrics cleanly with LaTeX that renders in GitHub markdown.
- [ ] Avoid AI-ish prose and long "design notes"; say less.
- [ ] Run external-review-v2 on plots/code.
- [x] Run external-review-v2 on plots/code.
- [ ] Run external-review-v2 comprehension panel on README once final plots/table are in.
- [ ] Show final file paths for plots and README.
- [ ] Commit small, push when done.
@@ -74,3 +75,4 @@ Out: changing eval semantics, changing dataset schemas, adding new metrics.
- 2026-06-30: README structural check before final regeneration: 9 images, `missing_images: []`, 15 local links, `missing_local_links: []`, and no 16PF map link.
- 2026-06-30: The endpoint-only map removed the path readers need. The sign-offset range geometry also made a one-dimensional value plot look like a fake two-dimensional fork.
- 2026-06-30: User wants range plots to show the path as sign lanes, not coefficient-x swim lines. The fix is negative/base/positive lanes, with vertical paths inside each lane.
- 2026-06-30: Sign labeling cannot be inferred from tinymfv in general. For this run we have a declared MFV Authority anchor; otherwise plots should report observed `+c`/`-c` effects, not auto-rename the vector.