Layered Investment, Value, Cash & Capital — Self-Contained Research Payload (v0.1)

Quick use

• Use when: a decision crosses delivery cost, implementation capacity, commercial behavior, service or clinical value, cash timing, and capital allocation.
• Produces: a PODA frame, method-selection receipt, five linked ledgers, six event clocks, calculations, evidence and coverage ledgers, scenario comparison, decision gate, and machine node.
• Decision set: continue, revise, pilot, scale, defer, redirect, stop, or study next.
• Completion state: decision_ready, bounded_not_ready, or authority_required.
• Core discipline: connect layers through explicit mechanisms and evidence. A value in one ledger becomes a coefficient in another only through a defined and reviewed relationship.

Named finance, accounting, clinical, operating, commercial, and investment owners establish local policy and authorize their respective decisions.

Public source basis

This payload precipitates four public Registry methods:

• Initiative Costing — Eight Methods for Evidence-Bearing Platform Decisions
• Eight Costing Methods — Choosing the Shape That Fits the Decision
• PODA
• PODA in Practice — Investment, Participation, and Organizational Return

A private design input informed the separation of layers, clocks, evidence, and authority. Its locator and internal details remain with their private owner; this public payload carries only the reusable architecture.

PODA frame

Purpose

Make the next investment decision legible across work, implementation, commercial, clinical or operational, cash, and capital perspectives while preserving their distinct meanings.

Objectives

1. Define the decision, options, accountable receiver, perspective, horizon, and authority boundary.
2. Select the narrowest costing method or linked method set that answers the live question.
3. Keep five ledgers and six event clocks separately inspectable.
4. Calculate from defined units, denominators, cohorts, windows, policies, and sourced inputs.
5. Preserve clinical and operational consequences as disaggregated measures before any reviewed economic transformation.
6. Return a bounded action, evidence ceiling, decisive unknowns, next gate, and recovery path.

Discoverables

The run makes these surfaces inspectable:

• work packages, roles, opportunity cost, base cost, reserve, and lifecycle burden;
• implementation dependencies, acceptance, activation, adoption, and support capacity;
• pricing, acquisition, retention, expansion, contraction, and exit;
• service or clinical consequences, evidence strength, affected populations, burden, equity, safety, and governance;
• accounting, invoice, revenue, payment, and cash timing;
• incremental scenario cash flows, sensitivity, reversibility, and the option purchased by the next tranche;
• causal links whose mechanism and evidence are strong enough to inform the decision;
• source coverage, unresolved fields, and the observation that changes the recommendation.

Activities

1. Normalize the input packet.
2. Build source and coverage ledgers.
3. Route the decision through the eight-method family.
4. Construct five ledgers and six clocks.
5. Validate units, cohorts, windows, ownership, and double-counting boundaries.
6. Calculate eligible outputs.
7. Challenge the preferred route with a comparator, sensitivity, and disconfirming condition.
8. Produce the human-readable packet and machine node.
9. Stop at the fitting decision, evidence, or authority boundary.

Operating instruction

Use sourced values and accountable policies. Represent a missing value as reserved or unavailable, name the evidence needed, and continue with independent outputs that remain valid. Explicit zero remains zero.

Distinguish observed, calculated, assumed, illustrative, reserved, and unavailable values. A calculation inherits the claim ceiling of its least-supported material input.

Public and authorized sources form the research record. Private locators, access coordinates, person-specific material, and internal source text remain with their authorized owners. An opaque semantic key may establish that an authorized input existed.

Required parameters

Every decision-bearing metric carries:

Method router

Select the narrowest method that answers the decision. Link methods when the decision crosses boundaries and preserve each method's inputs and output.

P50 and P80 are modeled distribution percentiles. Their meaning comes from the stated distributions and dependencies. Transparent low, likely, and high scenarios are fitting when distribution evidence remains incomplete.

Five linked ledgers

1. Internal investment and change

Record work packages, owners, roles, hours, loaded-rate policy, opportunity cost, direct cost, dependencies, migration, validation, training, parallel operation, support, retirement, base, identified contingency, management reserve, ranges, and overlap rules.

2. Implementation and adoption

Record integration, configuration, validation, acceptance, enablement, production readiness, eligible users or workflows, activation, adoption depth, support demand, issue rate, recovery, and the first conditions for operational and clinical value.

Go-live, activation, adoption, operational value, and clinical value remain distinct states.

3. Commercial cohort

Record cohort identity, segment, tenure, sample size, window, pricing unit, opening customers and revenue, new customers and revenue, retention, expansion, contraction, churn, acquisition-cost policy, contribution-margin policy, sales capacity, sales cycle, implementation state, sources, and owners.

New-customer revenue remains outside opening-cohort retention. Expansion remains visible beside gross loss.

4. Clinical and operational value

Keep safety, quality, effectiveness, timeliness, participant experience, equity, efficiency, resource use, worker burden, governance, and budget capacity disaggregated. Each measure names population, intervention, comparator, unit, direction, baseline, candidate state, window, source, standing, and reviewer.

Cost-consequence analysis is the default when distinct outcomes matter. Cost per incremental outcome becomes eligible when measure, transformation, comparator, source, validity window, and accountable review are complete.

5. Cash flow and capital allocation

Record alternative, decision standing, complete incremental cash-flow series including t=0, currency, period, horizon, tax, working-capital and terminal-value policy, discount-rate source, scenario probabilities, irreversible commitments, preserved options, learning objective, evidence threshold, gate date, capacity, opportunity cost, and next receiver.

Sunk cost remains history. Forward decisions use avoidable future cash flows, opportunity cost, capacity, evidence, and preserved options.

Six separate clocks

Contract signature, readiness, activation, first value, invoice, revenue recognition, and cash collection may occur in different periods. Preserve these event identities in every scenario.

Causal-link contract

A cross-ledger relationship begins as a hypothesis and gains standing through fitting evidence.

Training, disruption, adoption, support burden, retention, clinical value, and cash can be related. Their relationship becomes decision-bearing through a named mechanism, population, window, comparator, and reviewer.

Evidence hierarchy

Observed values describe their named population, source, and window. Calculated values report reproducible arithmetic and inherit the least-supported material input. Assumptions support scenarios and sensitivity. Illustrative fixtures demonstrate behavior. Reserved fields await evidence or authority. Unavailable results name the missing prerequisite.

Formula and eligibility contract

Expected NPV requires explicitly confirmed, mutually exclusive, collectively exhaustive scenarios whose probabilities sum to one. Incomplete probabilities stay visible. NPV leads the time-value comparison. IRR is eligible for a cash-flow pattern with a meaningful solution; payback remains visibly unreached while cumulative cash flow stays negative.

Consistency checks

Report each as pass, bounded, or open:

1. Each cost enters the base, implementation view, and cash flows through an explicit reconciliation rule.
2. Base, identified contingency, and management reserve remain separate.
3. Each uncertainty has one primary treatment, with mapped dependent effects.
4. Bookings, contract value, invoice, recognized revenue, and cash remain distinct.
5. Opening-cohort retention excludes new-customer and reactivation revenue.
6. Expansion remains visible beside contraction and churn.
7. Internal investment and customer implementation cost remain distinct until an explicit mapping joins them.
8. Clinical or operational outcomes connect to commercial value or cash through a reviewed mechanism.
9. Scenario probabilities remain supplied values and visibly incomplete when the outcome tree is incomplete.
10. Blank, invalid, inapplicable, ambiguous, and unreached values remain distinguishable.
11. Currency, period, horizon, cohort, perspective, and valuation date agree across compared options.
12. The status quo uses the same decision boundary as proposed options.

Source and coverage ledgers

A source can establish one field while adjacent claims remain open. State that boundary directly.

Research procedure

1. Frame

Return the PODA, accountable receiver, options, perspective, horizon, authority, decision date, and next review condition. Split materially distinct decisions into separate decision IDs.

2. Select methods

Offer two or three plausible methods with the question each answers, evidence required, open questions, and supported decision. Select the narrowest fitting set.

3. Build ledgers and clocks

Create all five ledgers. Mark an unused ledger inapplicable with its reason. Create separate event records for every represented clock.

4. Source and normalize

Build source and coverage records. Normalize units, currency, periods, cohorts, windows, and definitions. Preserve source-native values and record each transformation.

5. Calculate eligible outputs

Apply formulas whose prerequisites are complete. An unavailable result carries its exact missing requirement.

6. Compare and challenge

Compare the status quo, preferred route, one plausible alternative, and a defer, redirect, or stop posture when material. Test the largest sensitivity driver, a condition where waiting creates value, a condition where delay destroys value, a condition that weakens the preferred route, capacity constraints, and the effect of preserving or losing reversibility.

7. Form the gate

Choose continue, revise, pilot, scale, defer, redirect, stop, or study next. Name the evidence threshold, option preserved, irreversible commitment, receiver, and review date.

Output contract

Return one self-contained packet:

1. Executive decision brief
2. PODA
3. Method-selection receipt
4. Normalized parameter register
5. Five ledgers
6. Six clocks
7. Scenario and calculation tables
8. Clinical and operational cost-consequence table
9. Causal-link register
10. Source and coverage ledger
11. Assumption, reserve, and unknown register
12. Decision gate and re-entry
13. Machine node

Each numeric result carries value, status, unit, currency, period, cohort, observation window, formula version, sources, uncertainty, claim ceiling, owner, and explanation.

Stop and reopen

Return:

• decision_ready when evidence, policy, capacity, and authority support the next decision;
• bounded_not_ready when a named decision-changing evidence gap remains;
• authority_required when the analysis has reached a decision reserved for an accountable owner.

Stop when the decision, options, perspective, horizon, receiver, fitting method set, material definitions, ledgers, clocks, calculations, consistency checks, challenge case, next action, evidence threshold, and return date are explicit—and further retrieval would add examples without changing the next move.

Reopen when material evidence, policy, scope, cohort, pricing, implementation state, event timing, accounting treatment, safety or outcome evidence, adverse signals, option timing, source standing, or accountable authority changes. Preserve the prior packet, create a new as-of version, identify the changed evidence, and recalculate affected records and dependent conclusions.

Machine node

Corpus integrity and provenance

This public payload synthesizes Registry methods and a private architecture input. Public sources support the method. Local records, policies, owners, and observations establish the receiving decision.