Abstract a 50-page lease to one page

1 · Learn the move · RTO. Role · Task · Output

Nobody reads the fifty pages twice, so the abstract becomes the lease in everyone's head. That is why it has to be built by the right role, for one task, in a fixed output. The role is the owner's lease administrator: someone who reads records and restates them, not someone who explains what they mean. The task is a named list of fields, and on a ground lease for a pad on your own site the fields are not the ones a building lease has: the pad as the exhibit describes it, who carries the pad's taxes before it is separately assessed, the restrictions the lease puts on the rest of your acreage, and who owns the improvements at the end. The output is one page with a section cite on every line. Two instructions keep it honest. A field the lease never addresses reads NOT IN LEASE, so silence is visible. A field that points to an exhibit you did not paste reads [NEEDS: that exhibit], so the model does not describe a pad boundary from a site plan it has never seen.

You are the landlord's lease administrator. Abstract the ground lease below to one page with these fields: parties and premises as the exhibit describes them, term and options, rent schedule, taxes and shared site costs, use and restrictions on the rest of my site, improvements at expiry, leasehold financing, assignment. Cite the section on every line. Silent in the lease: NOT IN LEASE. Refers to an exhibit I did not paste: [NEEDS: that exhibit]. No interpretation. [lease]