Stewardship or Nonwaste Covenant¶

Binding covenant — instantiates Property Rights Bundle Governance

Binds a holder to a schedule of care-and-nonwaste duties that run with the resource, so a right to use never becomes a license to degrade what successors and the public inherit.

A right to use is not a right to use up. Stewardship or Nonwaste Covenant attaches affirmative care duties and negative nonwaste prohibitions to a holder's use, and — crucially — makes them run with the resource, so they bind successors, not just the party who signed. Its distinctive concern is the holder's obligations, the shadow side of their powers: where the transfer and exclusion mechanisms govern what a holder may do, this one governs what a holder must not let happen. Its one idea is old — use salva rerum substantia, without impairing the substance — so that the person enjoying a resource today cannot strip its value before the reversioner, the successor, or the public takes it back.

Example¶

A tenant takes a 40-year lease on a landmarked theater. Without a covenant, the tenant's incentive near the end of the term is to milk the building and defer everything; the landlord inherits a ruin. The covenant schedules affirmative duties — maintain the facade to a heritage standard, service the mechanical systems on a fixed cadence, keep it insured — and nonwaste prohibitions — no structural alteration, no stripping of protected fixtures, no letting deferred maintenance ripen into decay. Because it runs with the leasehold, a sublessee inherits the identical duties. Behind it stands the common-law doctrine of waste: a holder of a limited estate may use the thing but must not damage the interest of the one who holds the future estate.^[1] The reversioner's building — and the public's landmark — survive a holder who will not be there to face the long-run cost.

How it works¶

Three features set it apart from a generic contract clause:

It binds duties, not powers — it adds obligations to a use right rather than granting or moving a stick.
It runs with the resource — successors inherit the duties automatically, so the protection does not evaporate on the next transfer.
It pairs affirmative and negative — active upkeep on one side, prohibition of waste on the other; either alone leaves a gap.

Breach does not itself revoke or transfer anything — it triggers remedies handled by the enforcement and reversion siblings.

Tuning parameters¶

Duty stringency — from a bare nonwaste floor to an active, rising stewardship standard. Higher standards protect the resource but burden the holder and can deter use.
Running scope — personal to the signer, or running with the resource to all successors. Running scope is what gives durable protection and what raises dead-hand risk.
Horizon — co-terminous with a term, or perpetual. Perpetual duties protect longest and ossify fastest.
Measurement — a condition standard ("maintain to heritage grade") versus an outcome metric. Concrete measures are enforceable; vague ones are decorative.
Remedy linkage — whether breach yields damages, feeds a reversion trigger, or both.

When it helps, and when it misleads¶

Its strength is that it fixes the limited-holder's incentive to extract value before exit, protecting successors, reversioners, and shared resources from quiet degradation. Its failure mode is dead-hand control — perpetual covenants that bind successors to obsolete or even wasteful standards, blocking sensible modernization long after the drafter is gone — and, at the other extreme, duties so vague they cannot be enforced at all. Run backwards, a covenant can be invoked selectively to burden a disfavored holder rather than to protect the resource. The discipline that keeps it honest is to write measurable duties, to sunset or allow amendment so the covenant can track changed circumstances, and to tie stringency to genuine impairment risk rather than to a drafter's preferences.^[1]

How it implements the components¶

Stewardship or Nonwaste Covenant fills the duty side of the archetype:

stewardship_duty_schedule — the enumerated affirmative-care and nonwaste duties and the cadence on which they fall due.
encumbrance_and_constraint_register — the covenant is itself a constraint that runs with the resource, entered as an encumbrance against it so successors are on notice.

It sets duties but does not maintain the ledger of record (that register is Title or Entitlement Registry's), does not enforce a breach (Exclusion Enforcement Protocol and Dispute Adjudication Clause), and does not by itself end the right — that trigger is Reversion or Abandonment Rule.

Instantiates: Property Rights Bundle Governance — it is the archetype's duty-and-nonwaste layer running with the resource.
Sibling mechanisms: Reversion or Abandonment Rule · Title or Entitlement Registry · Rights Bundle Matrix · Exclusion Enforcement Protocol · Transfer, Assignment, or Sale Contract · Property Rights Impact Assessment · Access License or Permit · Anti-Commons Clearance Process · Benefit-Sharing or Royalty Agreement · Commons Access Rule · Compensation or Takings Review · Dispute Adjudication Clause · Easement, Covenant, or Use Restriction

Notes¶

A covenant is inert without a partner. It defines what care is owed, but nonwaste that no one monitors and no one remedies is merely decorative; the duty schedule only bites when a breach feeds an enforcement action or a Reversion or Abandonment Rule trigger. Write the covenant and its remedy pathway together, or neither works.

References¶

[1] The common-law doctrine of waste constrains a holder of a limited estate (a life tenant, a lessee) from acting — or failing to act — in ways that permanently damage the interest of the person entitled to the property afterward. It is the classic legal expression of "use without impairing the substance." ↩