# V-PP-001 Property Valuation Profile

V-PP-001 defines what a property valuation presentation must contain and how its evidence is bound together. A recipient checks the opinion of value, basis, date, property identity, issuer, status and addressee under its own policy. Professional reliance remains an engagement decision outside the format.

## Roles

Producer: a valuer, via the credential. Receiver: the lender named as addressee in the record, applying its own checks. The receiver controls its own policy ([X-PO-002 Institution Policy Overlay](../shared/policy/institution-overlay.md)) and its own acceptance decision.

## Claims and composition

Required (MUST): one valuation credential ([V-PC-001 Property Valuation Credential](../valuation/property-valuation-credential.md)). Conditional (MUST_IF): Property Condition evidence ([C-PP-001 Property Condition Profile](../condition/property-condition-profile.md)). The condition requirement is true when the recipient policy says a condition record is required, or when the valuation itself links a condition record. It is optional otherwise. Valuation composes with condition by reference to a separately signed instance; it never absorbs or re-signs it. Binding rules, in draft: [X-BD-001 SD-JWT VC Binding](../shared/sd-jwt-vc-binding.md), [X-VR-001 Verification Result Contract](../shared/verification-result-contract.md).

## Rules and timing

The valuation exists when the valuer issues it at origination, before any charge is registered; no registered security is required before a valuation exists. Its age runs from the valuation date. Condition-link semantics (draft): a linked condition instance keeps its own observation date, which a valuation or monitoring view does not refresh; a technical re-sign of that instance is the same record; a newer condition record does not change an earlier valuation's state but may raise a monitoring exception. Details are in [C-PP-001 Property Condition Profile](../condition/property-condition-profile.md). Adversarial evaluation remains incomplete and does not establish full enforcement of these rules.

The recipient supplies the expected property, engagement, purpose and acceptable evidence ages from its own transaction context. A presenter cannot replace those expectations with claims from the credential. Each linked condition credential needs its own signature, issuer authority, status and observation-age checks. See [Verifier behaviour](../security/verifier-behaviour.md).

## Example

A borrower obtains a valuation (350,000, market value) for a house. The lender's policy requires a condition record, so the valuation links a separately signed condition credential from an inspector.

## Implementation status

The property prototype includes a draft claims schema and signed synthetic fixtures. Internal, model-assisted evaluation has identified failures and incomplete coverage; independent human assurance and a profile-level independent conformance checker remain absent. The result checker checks consistency rather than credential signatures. Date validation, recipient-context enforcement and linked-condition checks remain incomplete. These requirements must not be described as established production controls. See [Assurance and release](../security/assurance-and-release.md).

## Related documentation

[Profile guide](../profiles/index.md) · [Valuation](index.md) · [Engagement and reliance](engagement-and-reliance.md)
