26-1041 · Krauss Ranch — 412 ac
Rural Land & Ranch 1.1.0 In progressAll-features reference. This page stays as the annotated inventory of every stage-5 capability — the working surface users actually get is Report Studio · usability layout, where these same features appear contextually (rail tabs, Export menu, dialogs, tooltips).
Report Studio
editable document — not a previewPolycrest editor · managed regions · named-slot pipelineUsability layout →Clicking an outline entry jumps to that node in the canvas. Exhibits are numbered outline entries. Core + pack slots, wrapped in the firm shell — removing a pack removes its slots cleanly.
TALCB #F-1002 · (830) 555-0148
July 30, 2026
Central Texas Farm Credit
Attn: Loan Department
Re: Appraisal of the Krauss Ranch — 412.4± acres, Gillespie County, Texas · our file 26-1041
At your request, I have appraised the fee simple interest in the above-referenced property for mortgage-financing use. Based on the analysis in the attached narrative report, it is my opinion thatBased on the analyses summarized in the attached narrative report, in my opinion the market value of the subject property, as is, was:
$5,940,000† live
as of July 30, 2026, the effective date of value, subject to the assumptions and limiting conditions stated herein.
† Restated from the Whole property · As is conclusion — a bound value, merged live, never re-typed. One source, zero contradictions across the transmittal, salient facts, reconciliation, and certification.
Sales comparison (excerpt)
| Sale | Date | Acres | $/ac |
|---|---|---|---|
| Pedernales River frontage | Apr 2024 | 268.0 | $9,120 |
| Threadgill Creek Ranch | Sep 2023 | 214.6 | $7,850 |
| Crabapple Creek tract | Feb 2024 | 205.4 | $10,050 |
| Live Oak Springs tract | Jun 2024 | 331.2 | $8,400 |
This is a Word-like editor over the structured report — selection-relative formatting, undo/redo, lists, tables, images, page breaks, and direct typing inside managed core / pack / shell regions. Direct human editing is the primary surface; the value itself stays a merged bound value. 31 / 46 sections assembled from real work product.
Review & suggestions
same guarded apply engine as the agents — nothing lands silentlyAccepting applies through the same guarded engine agents use — atomic operations against stable node IDs, typed conflicts on staleness. After accept, the canvas reloads from server truth: what you see is what was actually applied.
Versions & history
four records, four different promises| Record | When | By | Captured | |
|---|---|---|---|---|
| Working copy editing now | autosaved 12 s ago | Dana Whitfield | — (bindings live) | In Studio ↑ |
| “Pre-review” immutable | Jul 22, 2026 | Dana Whitfield | 14 bound values · 6 media — exact | Open — read-only · Restore → new head · Export… |
| “Draft to client” immutable | Jul 15, 2026 | Dana Whitfield | 13 bound values · 5 media — exact | Open — read-only · Restore → new head · Export… |
The reproducibility invariant: exactly what was visible is what was saved. Opening a named version is read-only and snapshot-only — every binding shows snapshot, and current data is never substituted silently during review or delivery. Restore never overwrites history; it copies the version to a new working head (bindings show restored snapshot until you explicitly ⟳ Refresh). Return to working copy is always one click from history.
Outputs & delivery
four distinct actions — only server-rendered artifacts enter delivery lineage| Rendered artifact | From named version | Rendered | Checksum | |
|---|---|---|---|---|
| 26-1041-draft.docx · Word | “Draft to client” | Jul 15, 10:42 | sha256 9f31…7e2 | Re-download — byte-identical |
| 26-1041-draft.pdf · PDF | “Draft to client” (from its stored DOCX) | Jul 15, 10:44 | sha256 4bc7…a91 | Re-download — byte-identical |
Every delivered artifact links back to the same captured source: delivered record → rendered artifact → named version → the exact values and media that were on screen when it was saved.
Signing panel
Stored signature graphic — a bound element, captured exactly in named versions. Credential snapshot taken at delivery.
Reviews against the “Pre-review” named version — a stable, captured target; reviewer counter-signature.