How to verify a perpetual purpose trust's legal structure

Legal information only; not legal advice. This record is written for attorney verification of an AI-drafted or AI-assisted instrument, not for client reliance or execution. Source links appear in the references, and statutory citations in this briefing were last verified on July 31, 2026.

A perpetual purpose trust legal structure is not validated by calling it “perpetual,” “steward-owned,” or “noncharitable.” Before execution, counsel has to prove that the selected situs statute authorizes the structure, that the purpose is lawful and possible, that someone has standing to enforce it, and that the duration clause fits the jurisdiction. If the draft came from an AI tool, assume those four points are unverified until the statute says otherwise.

That is a narrower question than whether purpose trusts are useful. They can be. The Purpose Foundation describes perpetual purpose trusts as ownership structures that can hold a company for a defined mission rather than for individual beneficiaries, and The Stakehold’s legal discussion uses the same basic frame: property is held and administered to carry out a stated purpose, with governance replacing ordinary beneficiary economics.[1][2] The drafting problem begins when that business-purpose vocabulary is treated as if it supplies legal validity by itself.

It does not. In a conventional private trust, beneficiaries do much of the enforcement work because they have equitable interests. In a noncharitable purpose trust, the instrument is asking state law to tolerate a trust without an ascertainable beneficiary. That is why the boring clauses matter: the situs clause, the purpose clause, the enforcer clause, the application-of-property clause, and the duration clause are not cleanup provisions. They are the structure.

Start with the statute, not the polished draft

An AI-generated purpose trust can look finished because the sentences are orderly. That is not the same as being executable. The first review should not be a style pass. It should be a source pass: identify the governing law, open the current statute, and test the instrument against the statutory elements that make a noncharitable purpose trust enforceable in that jurisdiction.

The sequence matters. If the governing law does not authorize the trust, the elegance of the purpose clause is beside the point. If the purpose is too indefinite to administer, naming an enforcer will not rescue it. If no one has standing to enforce, the trustee may be left with an attractive mission statement and no statutory mechanism. If the duration clause exceeds the statute, the document may fail exactly where the client thought it was strongest.

Gate 1: statutory authorization

The word “perpetual” should make the reviewer slower, not more confident. “Perpetual purpose trust” is a descriptor used by planners and ownership-design advocates; the enforceable thing is the statute under the chosen governing law. Some statutes track the Uniform Trust Code’s limited noncharitable-purpose trust model. Some jurisdictions permit longer or indefinite duration. Some documents use the language of one state while selecting another state’s situs.

Maine is a useful example of the UTC-style limit. Its noncharitable trust provision allows a trust for a noncharitable purpose without an ascertainable beneficiary, but provides that the trust may be enforced for 21 years unless another statute supplies a different rule.[3] New Mexico’s UTC enactment likewise includes the noncharitable-purpose trust framework, including the same kind of limited-duration structure.[4] A draft that says a Maine or New Mexico purpose trust is “perpetual” because it lacks individual beneficiaries has not solved the statutory problem; it has described the desired result.

Oregon illustrates a different cap. ORS 130.190 permits a trust for a noncharitable purpose, but the statute limits enforceability to 90 years.[5] That is not a stylistic distinction. A 90-year Oregon clause and a perpetual Wyoming clause are not interchangeable merely because both instruments are called purpose trusts.

Wyoming sits on the other side of the contrast. Wyoming materials addressing Wyo. Stat. § 4-10-410 describe a purpose trust structure that can continue indefinitely if the statutory requirements are satisfied.[6] South Dakota is also commonly selected in purpose-trust planning because of its perpetuity treatment, but any South Dakota instrument should be checked against the official current SDCL text before counsel quotes or relies on the clause. Do not let a model-generated citation to a familiar-looking trust-code section substitute for the actual situs statute.

The authorization check should end with a short written note in the file: selected situs, exact statutory section, current text verified, duration rule identified, and any statutory appointment or enforcement language copied into the review record. That note is not bureaucracy. It is the difference between reviewing the instrument and admiring it.

Gate 2: a purpose the court can administer

A purpose clause has two audiences. The client wants it to express the mission. The statute and any future court need it to be administrable. UTC-style provisions require trust purposes to be lawful, not contrary to public policy, and possible to achieve; a purpose trust also needs property to be applied only to its intended use.[3][4]

AI tools tend to overproduce language in this part of the document. They may generate a purpose clause that sounds noble but gives the trustee no test for compliance. “Preserve the founder’s values,” “advance stakeholder capitalism,” or “maintain the company’s positive impact” may be suitable introductory language, but standing alone they are weak administration standards. The reviewer should ask what action the trustee must take, what action the trustee must avoid, what tradeoffs are permitted, and who can say the purpose is being frustrated.

For a company-holding purpose trust, that usually means separating the expressive recital from the operative purpose. The recital can explain mission preservation. The operative clause should identify the property to be held, the purpose for which it is held, the trustee’s voting or governance obligations, any permitted sale or conversion conditions, and how the trustee should resolve conflict between financial preservation and mission constraints. The statute will not supply those business judgments for the drafter.

The phrase “possible to achieve” also deserves attention. A trust purpose can fail because it is illegal, but it can also fail because no trustee can know what performance means. If the document requires the trustee to ensure that a business “always” operates in a particular way, counsel should decide whether that is an enforceable governance standard or an invitation to future breach allegations. Perpetual drafting magnifies that problem because the clause is expected to survive changes in business model, regulation, ownership of operating subsidiaries, and market conditions.

Gate 3: the enforcer cannot be implied

The no-enforcer problem is the quiet defect that should make counsel distrust an otherwise handsome draft. A noncharitable purpose trust lacks ordinary beneficiaries. If the instrument does not designate a person or mechanism with power to enforce, the document may have no practical adversary when the trustee drifts from the purpose.

Maine’s statute is a useful reminder of the statutory mechanics: a noncharitable-purpose trust may be enforced by a person appointed in the terms of the trust, or by a person appointed by the court if the trust terms do not appoint one.[3] That statutory backstop should not make drafting casual. Relying on a later court appointment means the instrument has already failed to identify the person expected to monitor the trustee before a dispute arises.

The reviewing lawyer should distinguish governance rights from enforcement rights. An advisory committee may recommend. A trust protector may consent to transactions. A board observer may receive reports. None of those roles necessarily gives the holder standing to compel the trustee to apply property to the purpose. If the AI draft uses all three labels but never says who may sue, petition, demand an accounting, remove the trustee, or invoke a court’s jurisdiction, the enforcement structure is incomplete.

• Name the enforcer or provide an appointment mechanism that works at inception and after vacancy.
• State the enforcer’s powers separately from advisory or protector powers.
• Give the enforcer access to information sufficient to monitor the trustee.
• Address removal, resignation, incapacity, conflicts, compensation, and successor appointment.
• Check whether the situs statute supplies mandatory or default rules that override the draft.

This is also where copied forms tend to betray their origin. A clause drafted for a pet trust, a cemetery trust, or a short-duration noncharitable purpose may not support a perpetual company-holding structure. The role may be too thin, the reporting cadence may be absent, and the remedy language may assume a beneficiary who does not exist.

Gate 4: duration is jurisdictional, not decorative

Duration is the easiest clause for a model to state confidently and the easiest clause for counsel to catch if the statute is open. A draft may declare that the trust is irrevocable and perpetual. That declaration has no force if the situs statute permits enforcement only for a shorter period.

The practical review question is not “Does this document say perpetual?” It is “What happens on the last day the statute allows enforcement?” In a 21-year jurisdiction, a model-generated perpetual clause may create false comfort and no usable termination plan. In Oregon, a 90-year cap still requires drafting for what happens at the end of the period.[5] In a jurisdiction permitting indefinite duration, counsel still has to verify that the trust actually satisfies that jurisdiction’s statutory conditions, including situs, trustee qualification if relevant, enforcement, and purpose language.

Do not bury the duration review in a general rule-against-perpetuities memo. The question is more specific: how does the chosen state treat noncharitable purpose trusts without ascertainable beneficiaries, and does the instrument’s duration clause track that treatment? A citation to a general trust-duration statute may not answer the noncharitable-purpose trust question.

Heppner adds an intake problem to the drafting problem

The validity analysis above would be necessary even if the draft came from a lawyer’s form bank. AI adds a separate risk: the drafting history itself may become evidence. In February 2026, a federal judge in U.S. v. Heppner ruled that documents a client created with a public AI tool during estate planning were not protected by attorney-client privilege, even after the client later gave those documents to counsel.[7]

That ruling should not be inflated into a universal rule that every AI-assisted trust file is discoverable. The available report is about privilege treatment of client-created AI materials, not about perpetual purpose trust validity, and not about all possible lawyer-supervised AI use. Its importance for this workflow is narrower and still serious: the reviewer can no longer treat the AI draft as a neutral attachment that begins the legal file only when counsel receives it.

Cozen O’Connor’s alert on Heppner also warns that public AI platforms may store or reuse user inputs, and that AI-generated explanations can become evidence in will or trust contests.[7] For a purpose trust, that is not a remote concern. The client may have asked the tool to explain why heirs should not benefit, why control should be locked away from a family member, why a founder wanted an irreversible structure, or how to avoid a tax or creditor result. Those prompts and outputs may be more damaging than the final clause.

The intake questions should therefore move earlier. Before marking up the instrument, ask who used the AI system, whether it was public or enterprise-controlled, what was entered, what files were uploaded, what outputs were saved, whether the client relied on AI explanations when choosing the structure, and whether any family, fiduciary, employee, adviser, or investor received those outputs. If the client has already distributed an AI-generated rationale, counsel needs to know that before drafting the recitals.

This is not merely privilege housekeeping. It changes the contest file. A challenger may not need to prove that the final trust instrument was AI-generated if the saved prompt history shows confusion about beneficiaries, duration, tax consequences, or control. A clean execution ceremony will not erase a prior AI explanation that misdescribed the law or supplied a motive the client later denies.

The AI verification file counsel should build

For a conventional form review, a redline may be enough. For an AI-assisted perpetual purpose trust, the safer file is a verification record. It should show which assertions came from the draft, which were checked against authority, which were changed, and which client-provided AI materials were preserved or quarantined under counsel’s privilege protocol.

• Save the AI draft as received, with date, source, and sender.
• Identify all legal citations in the draft and mark each one as verified, wrong, irrelevant, or unsupported.
• Open the situs statute directly; do not rely on a secondary summary for authorization, enforcement, or duration.
• Create a clause-to-statute map for authorization, purpose, enforcer, application of property, and duration.
• Document any AI intake facts: prompts, outputs, uploaded documents, public-tool use, distribution to third parties, and client reliance.
• Record the human lawyer’s changes and the authority supporting each validity-critical revision.

The same discipline used in AI citation review applies here, but the stakes are more structural. A hallucinated case citation embarrasses a brief. A hallucinated duration rule can distort the trust’s entire premise. Our broader AI citation verification workflow is useful for the source-checking habit, but a purpose trust review needs clause-level statutory mapping as well.

Tax warnings belong in the risk check, not the validity holding

A legal-structure review should not pretend to resolve every tax consequence. It should, however, flag tax assumptions that make the structure dangerous. Greenleaf Trust cautions that retained-control issues can create estate-tax exposure under IRC §§ 2036 and 2038 when the transferor keeps powers or practical control inconsistent with the intended completed transfer.[8] That warning is especially relevant when a founder wants a purpose trust to preserve mission while also retaining influence over voting, trustee removal, protector appointments, or operating-company governance.

The classification backdrop is also unsettled. In May 2024, the AICPA submitted comments to Treasury and the IRS addressing tax classification of purpose trusts, which underscores that practitioners are still seeking clearer treatment rather than applying a single settled rule to every purpose trust.[9] Those comments are advocacy and guidance-seeking, not binding law. They should prompt tax review, not be cited as a definitive answer.

The verification file should therefore include a tax referral point: what powers are retained, who can remove or replace fiduciaries, whether the grantor can redirect economic value, and whether the business-control design undercuts the transfer position. That analysis may sit outside the trust-validity memo, but it should not sit outside the pre-execution process.

What to send back before execution

When the client or partner asks whether the AI draft is usable, the answer should be framed by status, not taste. “Clean draft” is not a status. “Verified against Wyoming purpose-trust statute, enforcer revised, duration supported, Heppner intake completed, tax review pending” is a status. So is “not executable: Oregon situs selected, perpetual duration clause unsupported, no enforceable enforcer provision, AI prompt history not yet reviewed.”

A pre-execution response can be short if the work behind it is complete. It should identify the selected situs, the statutory authority for a noncharitable purpose trust, the exact duration rule, the named enforcer and enforcement powers, the administrable purpose standard, unresolved tax issues, and the known AI-origin facts. If any of those points is unknown, the instrument is not ready for reliance.

A perpetual purpose trust can be reviewed safely. It cannot be reviewed generically. Treat the AI draft as an unverified artifact, check every validity element against the selected situs statute, preserve privilege awareness from intake forward, and document the human verification before execution.

References

1. What’s a Perpetual Purpose Trust? — Purpose Foundation
2. The Legal Stuff Underneath Perpetual Purpose Trusts — The Stakehold
3. Title 18-B, §409: Noncharitable trust without ascertainable beneficiary — Maine Legislature
4. HB0111FV — New Mexico Legislature
5. ORS 130.190: Trust for care of animal or other noncharitable purpose — Oregon Public Law
6. Purpose Trust — Wyoming LLC Attorney
7. A Caution About Using AI Tools During Estate Planning — Cozen O’Connor, 2026
8. Purpose Trusts: Proceed with Caution — Greenleaf Trust
9. AICPA provides comments on the tax classification of purpose trusts — AICPA & CIMA, May 2024