phoenix-waterfall-ledger-semantics

Implement waterfall ledger semantics and shortfall-based partial clawback for the Phoenix VC fund model.

Updated Jul 21, 2025
One-click install
npx skills add https://github.com/nikhillinit/Updog_restore --skill phoenix-waterfall-ledger-semantics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phoenix-waterfall-ledger-semantics
Source: https://github.com/nikhillinit/Updog_restore/tree/main/.claude/skills/phoenix-waterfall-ledger-semantics
Command: npx skills add https://github.com/nikhillinit/Updog_restore --skill phoenix-waterfall-ledger-semantics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Waterfall semantics for the Phoenix VC fund model, including tier vs ledger behavior and shortfall-based partial clawback. Ensures consistency between implementation, docs, and truth cases for GP/LP distributions and carry outcomes.

Core Features & Use Cases

  • Tier engine vs Ledger engine semantics (carry, distributions, and clawback rules)
  • Shortfall-based partial clawback computation
  • Cross-validation with truth-cases JSON and documentation (docs/calculations.md)
  • JSDoc alignment and precise articulation of clawback behavior

Quick Start

Update ledger/tier logic in server/analytics/waterfall-ledger.ts and related docs, then run truth-case tests to validate outcomes.

Frequently Asked Questions about phoenix-waterfall-ledger-semantics

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

FAQPage Schema
How do waterfall ledger semantics work for VC fund distributions?

Waterfall ledger semantics define the sequence and rules for distributing capital and carry to LPs and GPs in VC funds. This Skill implements tier-based and ledger-based engines that calculate GP carry limits, LP distributions, and shortfall-based partial clawback behavior to ensure consistent fund outcomes.

What is shortfall-based clawback and when does it apply?

Shortfall-based clawback is a mechanism that recaptures GP distributions when fund performance falls short of targets. This Skill specifies how clawback is computed non-time-based using LP shortfall calculations and applies it during liquidation to validate GP carry limits and cross-check truth-case scenarios.

How do I validate waterfall behavior matches documentation and truth cases?

Cross-validate your waterfall implementation by running truth-case tests against documented calculations. This Skill handles JSDoc alignment, validates clawback outcomes in truth-case JSONs like L08, and syncs behavior between server code and docs/calculations.md to catch inconsistencies.

What's the difference between tier engine and ledger engine in waterfall semantics?

Tier and ledger engines differ in how they compute carry, distributions, and clawback. This Skill covers both approaches: tier-based distributes sequentially by tier, while ledger-based uses cumulative fund performance at liquidation. Each has distinct shortfall calculations and GP carry outcomes.

Can I debug waterfall truth cases and expand the JSON test suite?

Yes. This Skill applies when expanding or debugging waterfall truth-case JSONs to validate real-world distribution scenarios. It ensures new truth cases align with clawback behavior, ledger semantics, and cumulative fund performance rules before deployment.