parallax-house-view-diff

Name: parallax-house-view-diff
Availability: InStock
Author: bencharoenwong

Validate active house view shifts via paired-call protocol with diff_output JSON.

3|3|Updated Mar 27, 2026

Search Tags:#diff #output-contract #house-view #portfolio-verification #paired-call #protocol-spec

Ready to run

npx skills add https://github.com/bencharoenwong/parallax-workflows --skill parallax-house-view-diff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: parallax-house-view-diff
Source: https://github.com/bencharoenwong/parallax-workflows/tree/main/skills/house-view-diff
Command: npx skills add https://github.com/bencharoenwong/parallax-workflows --skill parallax-house-view-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This SPEC defines a standardized protocol to verify that an active house view produces a measurable shift in the downstream portfolio output, enabling deterministic validation of investment views.

Core Features & Use Cases

Dual-leg, paired-call protocol: Outlines how to run Leg A against a baseline and Leg B against an active view, ensuring comparability.
Diff-output contract: Requires emitting a <diff_output> JSON block that captures changes in ranks and weights, plus narrative rationale.
Exit and error semantics: Specifies PASS, WEAK, KILL outcomes and robust error handling for timeouts, validation failures, and query issues.

Quick Start

Validate a baseline vs. active view using the paired-call protocol and inspect the produced <diff_output> to confirm changes and verdict.

Frequently Asked Questions about parallax-house-view-diff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate portfolio output changes when applying an active house view?▼

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.

What is the diff output contract for portfolio verification?▼

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.

How do I handle validation failures and timeouts during a paired-call house view diff?▼

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.

Can I use this paired-call protocol without supplying my own runner and calibration?▼

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.

When do I need to use a dual-leg protocol for investment view verification?▼

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.

What distinguishes paired-call portfolio verification from other data and analytics approaches?▼

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.