Last updated Jun 14, 2026

Spousal consent on founder grants

Nine US states are community-property jurisdictions — Arizona, California, Idaho, Louisiana, Nevada, New Mexico, Texas, Washington, Wisconsin — and two more, Alaska and Tennessee, allow optional community-property elections. In a community-property state, a spouse holds an undivided 50% interest in marital property. Founder stock acquired during marriage is community property by default. When that stock is subject to vesting, repurchase rights, or transfer restrictions, the founder cannot unilaterally bind the spouse's community-property interest.

Investors, acquirers, and counsel for the corporation require spousal consent at every stage where the stock changes hands or its terms change — initial issuance, grant amendment, repurchase, departing- cofounder buyout, priced-round close, M&A close. Consent is a one-page acknowledgement: the spouse confirms awareness of the terms and waives community-property rights to the extent inconsistent with them. The structure is consistent across states; the underlying legal substance — what is community property, what a postnuptial agreement does, when a spouse can refuse — is state law and fact-intensive.

This page is the architectural commitment that defines that boundary. Matter records the document, captures the signature, and links it to the affected Grant / Resolution / CorporateTransaction. State-licensed family-law counsel determines whether consent is sufficient, whether a postnuptial agreement is needed, and what the consent actually waives.

Community-property states

The nine community-property states are Arizona, California, Idaho, Louisiana, Nevada, New Mexico, Texas, Washington, and Wisconsin. Alaska and Tennessee permit opt-in community-property elections via formal agreement. State-by-state nuances differ — Louisiana's civil-law origin produces substantively different results than California's common-law community-property framework — but the data model captures the state, not the substantive analysis. The substantive analysis is counsel's.

What Matter does

Matter owns the document-and-linkage surface around spousal consent. Specifically:

Trigger detection

• Matter determines whether spousal consent is required by evaluating Stakeholder.residence_state ∈ community_property_states AND Stakeholder.marital_status ∈ {married, domestic_partnership_with_cp} (proposed enum). When both are true at a stock-issuance, amendment, repurchase, transfer, or M&A event, Matter flags spousal_consent_required: true.
• The flag surfaces on Grant.preflight_blockers[], Resolution.preflight_blockers[], and CorporateTransaction.preflight_blockers[]. The blocker prevents the parent record from advancing until the consent is executed and linked.

Document generation

• Document.kind: spousal_consent (proposed) is the canonical document. Merge fields: founder name, spouse name, grant terms summary, state.
• The template is jurisdiction-aware. The CA template cites CA Family Code §1100; the TX template cites Texas Family Code Chapter 3; the LA template uses civil-law language. Matter selects the template from Stakeholder.residence_state at generation time.
• Generate via POST /v1/documents with kind: spousal_consent and the template_id for the right state. The state and the parent record are required merge inputs.

Signature capture

• The spouse signs with signing_capacity: spouse_of_stockholder (proposed enum). The capacity is distinct from signing_capacity: stockholder so the executed Document records who signed in what role.
• Matter captures the signature, the e-signature evidence, and the delivery channel.
• Document.execution_status flips to executed when both the founder (in stockholder capacity) and the spouse (in spouse_of_stockholder capacity) have signed.

Linkage

• The executed Document attaches to the relevant parent — Grant, Resolution, or CorporateTransaction — via attaches_to: <parent_id> and attachment_kind: spousal_consent.
• The cap-table view surfaces spousal-consent status on each grant in CP-state cases. A grant with spousal_consent_required: true and no executed consent is flagged on the cap-table.

No-op confirmation

• When a founder is in a non-CP state, Matter returns spousal_consent_required: false on the relevant pre-flight, with an evidence block citing the state and the test. The integrating agent records the no-op confirmation rather than skipping silently. See no-op confirmation for the evidence shape.

What Matter does NOT do

These belong to family-law counsel, the founder, the spouse, or the state's substantive law — not to Matter.

• Community-property determination. Whether a specific founder's specific shares are community property is a fact-question of state law: when were they acquired, with what consideration, was there a postnup, was the consideration separate property, did the founder reside in the state at acquisition. Matter assumes the default (acquired during marriage in a CP state = CP) and flags requires_counsel_verification: true for any case where the substantive question is genuinely contested. The verification itself is counsel's.
• Postnuptial agreement drafting. A postnup carving founder stock out of community property is a family-law document drafted by a family-law attorney. Matter records an executed postnup as a separate Document (Document.kind: postnuptial_agreement, proposed) but does not draft it.
• Substantive legal advice. Whether spousal consent is "good enough" for a specific deal, whether a postnup is preferable, whether a spouse can refuse to consent, whether a refusal blocks the stock issuance — all family-law questions. Matter records the document; counsel advises.
• Family-law jurisdictional analysis. Founders who relocate from non-CP to CP states (or vice versa) trigger a complex jurisdiction-of-marriage analysis: which state's law governs the property characterization of stock acquired under each residence. Matter records Stakeholder.residence_state history; counsel applies the law.
• Spouse identification. Matter relies on Stakeholder.spouse_id or Stakeholder.spouse_name being correctly populated. Verifying who the legal spouse is (in cases of separation, pending divorce, common-law marriage, putative marriage) is a counsel question.
• Negotiation between spouses. When a spouse refuses to consent, the conversation is between the founder, the spouse, and family-law counsel — not on the Matter platform. Matter exposes the document state (draft, sent, partially_signed); the negotiation lives elsewhere.

How handoff works

The pattern is the same in every direction: Matter generates the document; counsel verifies the substance; Matter records the executed result.

                   ┌─────────────────────────┐
                   │   Matter (records)      │
                   │  - Spouse known         │
                   │  - State known          │
                   │  - Document.kind:       │
                   │    spousal_consent      │
                   │  - Signing capacity     │
                   │  - Executed link        │
                   └────────────┬────────────┘
                                │
                  Document for execution
                                ▼
                   ┌─────────────────────────┐
                   │  Family-law counsel     │
                   │  - CP determination     │
                   │  - Substantive review   │
                   │  - Postnup if needed    │
                   │  - Refusal negotiation  │
                   └────────────┬────────────┘
                                │
                       Document executed
                                ▼
                   ┌─────────────────────────┐
                   │   Matter (records)      │
                   │  - attaches_to: grt_*   │
                   │  - attachment_kind:     │
                   │    spousal_consent      │
                   │  - Cap-table updated    │
                   └─────────────────────────┘

When spousal consent is required

Every event that changes a CP-state founder's equity terms or transfers shares the spouse has a community interest in:

• At founder stock issuance. Required when the founder is in a CP state at issuance and the stock is subject to vesting, repurchase, or transfer restrictions.
• At grant amendment. Required when amending vesting, repurchase, or transfer terms — for example, a re-vesting overlay imposed by Series A investors at first priced round.
• At repurchase. Required when shares being repurchased have community-property interest (founder departure, termination-for-cause repurchase, voluntary repurchase).
• At cofounder departure or buyout. Required for the departing cofounder's spouse, and for the remaining founders' spouses when their cap-table interest changes as a result.
• At priced-round close. Required when founder stock is being amended at close (new vesting overlay, accelerated-vesting carve-out, drag-along extension).
• At M&A close. Required for any officer, founder, or other CP-state stockholder whose shares are being sold or exchanged.

State-by-state notes

Matter's templates are jurisdiction-aware. Brief notes on the substantive landscape:

• California. Most common case. CA Family Code §1100 governs community-property management; §1102 governs real-property conveyances; §721 governs spousal fiduciary duties.
• Texas. Texas Family Code Chapter 3 governs marital property. Sole-management vs. joint-management distinctions matter — counsel determines which applies.
• Louisiana. Civil-law state with substantively different community- property doctrine than the common-law CP states. The template differs accordingly.
• Washington, Arizona, Nevada, New Mexico, Idaho, Wisconsin. Common- law CP frameworks broadly similar to California's, with state-specific nuances counsel applies.
• Alaska, Tennessee. Opt-in CP via formal election. Matter records the election as a Document.kind: community_property_election (proposed); the consent flow then runs as it would in a default-CP state.

Why the boundary

Three reasons.

Family law is state-law and fact-intensive

Whether a particular share is community property requires inquiry into when it was acquired, how it was paid for, whether the consideration was separate property, whether the founder was a resident of the state at acquisition, whether a postnup or premarital agreement applies. Matter cannot make that determination accurately at scale. The structured fields Matter exposes (residence_state, marital_status, spouse_id) support counsel's analysis; they do not replace it.

Counsel is the right party

Family-law attorneys are the right professionals for community-property substance. The corporate-equity attorney drafting the share-purchase agreement is the right professional for the equity terms. A cap-table platform is neither, and should not pretend to be either.

Matter's edge is records-of-truth

The document, the signature, the linkage to the affected Grant, the auditable history of who consented to what when — all are records. Records is what Matter does well at scale. The substance — the legal analysis of whether a given consent actually achieves what the parties need — is counsel's domain. The boundary keeps Matter useful without making Matter a substitute for legal advice.

Adding a community-property surface for a new event

When a new corporate-equity event surfaces that may require spousal consent (a new transaction shape, a new repurchase right, a new transfer restriction), the design pattern is:

1. Identify the corporate-equity event. A grant, an amendment, a repurchase, a transfer, a buyout, an M&A leg. Each event needs spousal-consent gating in CP-state cases. Add the event to the set that Matter checks spousal_consent_required against.
2. Identify the affected stakeholders. Whose shares are changing? What are their states? Matter resolves the affected Stakeholder list from the event payload.
3. Generate the consent. Document.kind: spousal_consent with the right state-template. The merge fields come from the event payload plus the Stakeholder record.
4. Distribute and capture signature. Use the standard signing envelope with signing_capacity: spouse_of_stockholder. Matter captures the e-signature evidence.
5. Link to the parent corporate-equity record. Set attaches_to to the grant, resolution, or corporate-transaction id, and attachment_kind: spousal_consent. The link is what makes the consent discoverable from the cap-table and the Resolution.
6. Surface the no-op for non-CP cases. Record the structured "spousal consent not required because residence state is not CP" verdict so integrators can confirm they checked. See no-op confirmation.

If a proposal cannot be expressed in those six steps without inventing a substantive-law-analysis resource, it crosses the line. Either the proposal needs to be reshaped, or it belongs with counsel — not in Matter.

Related

• No-op confirmation — the structured "nothing to do here" pattern that surfaces non-CP-state cases as evidence-bearing verdicts rather than silence.
• Post-Exit Manage — the parallel boundary pattern around post-close obligations, where Matter records governance and partners run substance.
• Payroll and benefits handoff — the same boundary pattern around employment and benefits.
• Lifecycle — the broader Create / Manage / Exit framing this convention fits inside.