pf_app
Paul Trowbridge
2814b4073c
It was the literal 'Forecast'. The moment the buckets were renamed to carry their sort prefix -- '04 - Forecast' -- nothing matched: every row counted as a comparison rather than a step, so the walk had no middle, the loads came to nothing, and the bridge showed the basis cancelling itself exactly to zero with a Forecast anchor of 0.00 over 0 rows. The version's adjustment_bucket is the right source, being the same value an unbucketed adjustment is labelled with, so the bridge and the pivot agree by construction rather than by both hardcoding the same string. If that value names no bucket in the data -- renamed since, or never configured -- it falls back to whichever bucket actually holds the adjustments. A bridge that is merely mislabelled beats one that is silently empty. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| lib | ||
| public | ||
| routes | ||
| setup_sql | ||
| ui | ||
| .env.example | ||
| .gitignore | ||
| CLAUDE.md | ||
| install.sh | ||
| package-lock.json | ||
| package.json | ||
| PERSPECTIVE.md | ||
| pf_perspective_options.md | ||
| pf_spec.md | ||
| pf.sh | ||
| server.js | ||