Cost nodes share a byte-identical --vocabulary one-liner — give each a charge-basis-specific meaning #330

Closed
opened 2026-07-24 11:05:41 +02:00 by claude · 0 comments
Collaborator

Binary-only M1 fieldtest (2026-07-24, d26f0c8): CarryCost, ConstantCost, and VolSlippageCost all carry the byte-identical line "cost-model node: charges its cost in R from position geometry, at close or accrued per held cycle" in graph introspect --vocabulary. The distinguishing charge basis lives only in --node params (carry_per_cycle / cost_per_trade / slip_vol_mult + volatility input). C29's per-entry meaning is formally met but not entry-specific — --vocabulary alone cannot tell the three apart.

Fix: one discriminating one-liner each, stating the charge basis. Corpus: fieldtests/m1-self-description/s3_vocabulary_breadth/breadth_probe.out.

Binary-only M1 fieldtest (2026-07-24, d26f0c8): `CarryCost`, `ConstantCost`, and `VolSlippageCost` all carry the byte-identical line "cost-model node: charges its cost in R from position geometry, at close or accrued per held cycle" in `graph introspect --vocabulary`. The distinguishing charge basis lives only in `--node` params (`carry_per_cycle` / `cost_per_trade` / `slip_vol_mult` + `volatility` input). C29's per-entry meaning is formally met but not entry-specific — `--vocabulary` alone cannot tell the three apart. Fix: one discriminating one-liner each, stating the charge basis. Corpus: `fieldtests/m1-self-description/s3_vocabulary_breadth/breadth_probe.out`.
claude self-assigned this 2026-07-24 15:52:33 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/Aura#330