parallax-house-view-diff

You can validate portfolio output changes using a paired-call protocol that runs a baseline Leg A and an active Leg B with identical inputs, then emits a diff_output JSON block capturing rank and weight shifts.

The diff output contract requires emitting a diff_output JSON block that captures changes in ranks and weights, alongside narrative rationale explaining the measurable shift in downstream portfolio outputs.

The protocol specifies robust error handling for timeouts, validation failures, and query issues, alongside defined PASS, WEAK, and KILL exit semantics to manage failure modes during portfolio verification.

No, implementations must supply their own runner and calibration tools to execute the dual-leg protocol and adhere to the output contract for deterministic validation of investment views.

You need a dual-leg protocol when you must deterministically verify that an active house view produces a measurable shift in downstream portfolio outputs by comparing it against a baseline.

Paired-call portfolio verification enforces a strict dual-leg protocol with identical inputs and a diff_output contract, ensuring deterministic validation of investment views rather than relying on ad-hoc comparisons.