property-reconcilelisted
Install: claude install-skill Vinedine/para-os
# Property reconcile
Answers one question: **does what the dossier says match what the source documents and the owner's own books say?** A verification skill, not an enrichment one.
## Arguments
| Arg | Behavior |
|---|---|
| *(none)* | Ask which property to reconcile |
| `<property-name>` | Match against `projects/`, `resources/ideas/`, then `areas/properties/` |
| `--test` | Test run, see [para-shared/test-run.md](../para-shared/test-run.md). |
## What it reads
- **The vault's `CLAUDE.md`**: its `**Flavor:**` and `**Delivery:**` lines, the books line under `## Deal sheets`, the language rule.
- **`.claude/rules/property-dossier.md`** (the shape claims live in) and **`property-sources.md`** (how `sources/` is named).
- **`resources/property-evaluation/property-data-sources.md`**, the source register: it says which gaps are unobtainable. It is not a licence to fetch.
A vault that declares no `**Flavor:** real-estate` and has no dossier rule is not a property vault: ask which vault to run in.
## Procedure
Track the phases in the harness's task list where it offers one, else in a short progress message at each phase boundary. On `**Delivery:** readonly-ipad`, run [its edit cycle](../para-shared/operating-discipline.md#the-read-only-ipad-delivery) around the writes.
1. **Locate.** Resolve the vault root once and hold it (`operating-discipline.md`). Resolve the property to exactly one folder and its dossier: `brief.md` in `projects/` or `resources/ideas/`, `README.md` in