See the stars

RecordMesh Specification

Home / RecordMesh / RecordMesh Specification

RecordMesh

Record systems don’t connect – until RecordMesh.


Specification

RecordMesh is an open source, modular AI platform for designing life estates and related real property instruments according to the laws of the state where a property is located. The system translates structured legal intent into jurisdiction-aware instruments, validates legal and recording conditions, and generates county-specific deed recording packets.

RecordMesh separates legal rules from county recording requirements so that state-specific legal logic can evolve independently from local recording procedures. The system is designed to support transparent drafting, validation, provenance, auditability, and human review.

RecordMesh is a legal drafting and workflow automation system. It does not replace licensed legal counsel, guarantee legal enforceability, or guarantee acceptance by a recording authority.


Core Modules

Intent Module

The Intent Module converts natural-language property and estate objectives into structured legal intent.

Features include:

  • Capture property ownership objectives.
  • Identify grantors, grantees, life tenants, remaindermen, and other relevant parties.
  • Identify the property and jurisdiction.
  • Capture desired life estate terms and conditions.
  • Capture termination and reversion conditions.
  • Capture restrictions, responsibilities, and rights associated with the life estate.
  • Identify desired recording and filing outcomes.
  • Distinguish user-provided objectives from legally derived requirements.
  • Preserve the original intent for audit and review.
  • Identify incomplete, ambiguous, or conflicting instructions.

Jurisdiction Law Module

The Jurisdiction Law Module provides state-specific property law rules used to evaluate and construct instruments.

Features include:

  • State-specific property law rules.
  • Life estate requirements.
  • Deed execution requirements.
  • Conveyance requirements.
  • Ownership and transfer rules.
  • Remainder and reversion concepts.
  • Termination conditions.
  • Abandonment-related legal rules.
  • Forfeiture provisions where legally recognized.
  • Statutory and regulatory requirements.
  • Jurisdiction-specific limitations.
  • Legal source citations.
  • Effective dates and rule versions.
  • Rule provenance.
  • Human-review requirements for uncertain or conflicting law.
  • Independent state-law plugins that can be updated without changing the core system.

The module must distinguish between a requested legal condition and a condition that is actually enforceable under applicable law.

For example, a requested termination after three years of abandonment must be evaluated against the applicable jurisdiction rather than automatically being treated as legally effective.

Instrument Builder Module

The Instrument Builder converts structured legal intent and applicable jurisdiction rules into a structured real property instrument.

Features include:

  • Life estate deed generation.
  • Deed clause generation.
  • Granting language.
  • Legal descriptions.
  • Life estate provisions.
  • Remainder provisions.
  • Reversion provisions.
  • Termination provisions.
  • Conditions and restrictions.
  • Rights and obligations of parties.
  • Execution provisions.
  • Signature provisions.
  • Notary acknowledgment provisions.
  • Jurisdiction-specific language.
  • Conditional clause handling.
  • Alternative clause generation where legal rules provide multiple approaches.
  • Preservation of source intent.
  • Traceability between generated clauses and applicable rules.

The Instrument Builder must not silently convert an unenforceable user request into a statement of law. Potentially invalid or uncertain provisions must be identified for review.

Legal Risk and Validation Module

The Legal Risk and Validation Module evaluates generated instruments before they are presented as filing-ready documents.

Features include:

  • Validate required parties.
  • Validate jurisdiction selection.
  • Validate property information.
  • Validate legal descriptions.
  • Validate required deed provisions.
  • Identify conflicting provisions.
  • Identify potentially unenforceable provisions.
  • Identify jurisdictional uncertainty.
  • Identify missing execution requirements.
  • Identify missing acknowledgment requirements.
  • Identify potential recording deficiencies.
  • Flag abandonment and forfeiture provisions requiring additional legal review.
  • Flag conditions that may require judicial enforcement.
  • Identify conflicts between state law and requested terms.
  • Assign risk levels.
  • Provide explanations for validation results.
  • Provide supporting legal sources.
  • Preserve validation results in the audit record.
  • Prevent unsupported claims of legal validity.

Document Renderer Module

The Document Renderer converts validated instrument data into usable document formats.

Features include:

  • Render deeds and related instruments.
  • Generate PDF documents.
  • Generate DOCX documents.
  • Generate Markdown documents.
  • Generate structured data representations.
  • Apply jurisdiction-specific formatting.
  • Apply county-specific formatting requirements.
  • Generate signature blocks.
  • Generate notary blocks.
  • Preserve legal descriptions.
  • Preserve recording metadata.
  • Generate human-readable review copies.
  • Generate filing-oriented document copies.
  • Maintain consistent document versioning.

County Profile Module

The County Profile Module manages local recording requirements independently from state legal rules.

Features include:

  • County-specific recording requirements.
  • Recording office information.
  • Document formatting requirements.
  • Page requirements.
  • Margin requirements.
  • Font requirements where applicable.
  • Paper and page-size requirements.
  • Cover sheet requirements.
  • Recording fee requirements.
  • Transfer tax requirements.
  • Documentary stamp requirements where applicable.
  • Preliminary change of ownership requirements where applicable.
  • Parcel identification requirements.
  • Indexing requirements.
  • Return address requirements.
  • Return envelope requirements.
  • Recording reference requirements.
  • Local metadata requirements.
  • E-recording requirements.
  • County rule versioning.
  • County source citations.
  • County requirement provenance.

County profiles must not override state legal rules. They function as the local recording and filing layer applied after jurisdictional legal analysis.

Recording Packet Compiler Module

The Recording Packet Compiler assembles the complete filing package required for a particular county.

Features include:

  • Compile the executed deed or instrument.
  • Generate county cover sheets.
  • Generate applicable transfer tax forms.
  • Generate applicable documentary tax forms.
  • Generate preliminary change of ownership forms where required.
  • Generate or validate notary acknowledgment blocks.
  • Generate recording fee calculation sheets.
  • Generate return envelope instructions where required.
  • Include parcel and lot indexing references.
  • Apply county-specific formatting.
  • Apply recording metadata.
  • Validate packet completeness.
  • Identify missing required documents.
  • Identify missing signatures or acknowledgments.
  • Organize documents in the required filing sequence.
  • Generate a human-review checklist.
  • Produce a complete county-ready recording packet.
  • Preserve packet provenance and version information.

The county is treated as the final recording compiler target after state legal analysis has been completed.

Submission Adapter Module

The Submission Adapter Module provides an interface between a completed recording packet and a filing method.

Features include:

  • Manual filing package generation.
  • Recording office submission instructions.
  • Electronic recording preparation.
  • E-recording vendor adapters.
  • Submission metadata generation.
  • Filing status tracking.
  • Recording reference capture.
  • Submission confirmation tracking.
  • Rejection tracking.
  • Resubmission workflow support.
  • Recording result preservation.

Electronic submission adapters are optional and must not be required for the core RecordMesh workflow.

Audit and Provenance Module

The Audit and Provenance Module preserves the reasoning, sources, inputs, outputs, and changes associated with each generated instrument.

Features include:

  • Record original user intent.
  • Record jurisdiction selection.
  • Record state-law sources.
  • Record county recording sources.
  • Record rule versions.
  • Record timestamps.
  • Record generated clauses.
  • Record validation results.
  • Record risk flags.
  • Record document versions.
  • Record packet versions.
  • Record user approvals.
  • Record human modifications.
  • Preserve source-to-clause relationships.
  • Provide reproducible drafting history.
  • Support document provenance verification.

Human Review Module

The Human Review Module keeps consequential legal decisions under human control.

Features include:

  • Present generated instruments for review.
  • Present legal risk warnings.
  • Present uncertain or conflicting rules.
  • Explain why provisions were generated.
  • Identify provisions requiring professional review.
  • Require approval before finalization.
  • Record reviewer decisions.
  • Record accepted and rejected provisions.
  • Preserve changes made after review.
  • Prevent automated systems from representing uncertain legal conclusions as settled law.

Optional Plugin Modules

State Law Plugins

State Law Plugins provide jurisdiction-specific property law knowledge.

Capabilities may include:

  • State statutes.
  • State regulations.
  • State case-law references.
  • State deed requirements.
  • State life estate rules.
  • State termination and reversion rules.
  • State-specific execution requirements.
  • State-specific transfer requirements.
  • State legal source tracking.
  • State rule versioning.

Each state plugin operates independently and can be updated without changing the core RecordMesh architecture.

County Recording Plugins

County Recording Plugins provide localized recording requirements.

Capabilities may include:

  • County recorder requirements.
  • County clerk requirements.
  • County cover sheets.
  • County fee schedules.
  • County tax forms.
  • County formatting requirements.
  • County indexing requirements.
  • County parcel metadata.
  • County return requirements.
  • County e-recording requirements.

E-Recording Plugins

E-Recording Plugins provide optional connections to electronic recording services.

Capabilities may include:

  • Electronic document packaging.
  • Submission metadata.
  • Vendor-specific requirements.
  • Filing status retrieval.
  • Recording confirmation retrieval.
  • Rejection handling.
  • Resubmission workflows.

GIS and Parcel Plugins

GIS and Parcel Plugins connect property instruments to geographic and parcel information.

Capabilities may include:

  • Parcel identification.
  • Parcel boundary information.
  • GIS references.
  • Lot and block information.
  • Property address validation.
  • Jurisdiction identification.
  • County identification.
  • Parcel metadata validation.
  • Mapping references.

Legal Source Plugins

Legal Source Plugins provide external legal authority and source-management capabilities.

Capabilities may include:

  • Statutory source retrieval.
  • Regulatory source retrieval.
  • Case-law source retrieval.
  • Legal citation management.
  • Source version tracking.
  • Effective-date tracking.
  • Source provenance.
  • Conflict detection between sources.

Trust and Estate Planning Plugins

Trust and Estate Planning Plugins extend RecordMesh beyond standalone life estate instruments.

Capabilities may include:

  • Trust-related property transfers.
  • Remainder planning.
  • Probate workflow integration.
  • Estate planning scenarios.
  • Property succession modeling.
  • Beneficiary structures.
  • Transfer simulations.

Property Transfer Simulation Plugin

The Property Transfer Simulation Plugin models potential ownership outcomes before an instrument is finalized.

Capabilities may include:

  • Ownership transition modeling.
  • Life tenant scenarios.
  • Remainder beneficiary scenarios.
  • Reversion scenarios.
  • Death-triggered transitions.
  • Requested abandonment scenarios.
  • Forfeiture scenarios.
  • Probate implications.
  • Recording workflow implications.
  • Alternative instrument comparisons.

Document Verification Plugin

The Document Verification Plugin provides additional document integrity and provenance capabilities.

Capabilities may include:

  • Document fingerprints.
  • Version verification.
  • Signature verification metadata.
  • Recording reference verification.
  • Provenance records.
  • Tamper detection.
  • Document comparison.

Multi-Language Plugin

The Multi-Language Plugin provides multilingual user interaction and document support.

Capabilities may include:

  • Multilingual intent capture.
  • Translation of user instructions.
  • Multilingual explanations.
  • Language-specific review workflows.
  • Preservation of authoritative legal terminology.
  • Human verification of translated legal content.

Enterprise Orchestration Plugin

The Enterprise Orchestration Plugin extends RecordMesh for organizations managing large volumes of property instruments.

Capabilities may include:

  • Batch processing.
  • Workflow queues.
  • Role-based review.
  • Approval routing.
  • Organization-level audit trails.
  • Bulk validation.
  • Bulk packet generation.
  • API-driven workflows.
  • Multi-jurisdiction processing.

Processing Model

RecordMesh follows a layered processing model:

Intent -> Jurisdiction Law -> Instrument Builder -> Legal Risk and Validation -> Document Renderer -> County Profile -> Recording Packet Compiler -> Submission Adapter

The processing model must preserve the distinction between:

  • User intent.
  • State legal requirements.
  • County recording requirements.
  • Generated document content.
  • Validation results.
  • Human decisions.
  • Submission results.

State modules determine legal and enforceability requirements.

County modules determine local recording and filing requirements.

The county recording layer must not modify the underlying legal interpretation supplied by the applicable state-law layer.

Life Estate Specification

RecordMesh must support the design of life estates and related property instruments based on the jurisdiction where the property is located.

The system must support requested conditions including:

  • Creation of a life estate.
  • Identification of the life tenant.
  • Identification of the property owner or grantor.
  • Identification of remainder beneficiaries.
  • Creation of reversion provisions.
  • Death-related termination conditions.
  • Requested forfeiture conditions.
  • Requested abandonment conditions.
  • Responsibilities associated with the life estate.
  • Property-use restrictions.
  • Property maintenance requirements.
  • Other legally relevant conditions.

Requested termination conditions must be evaluated against applicable law.

A requested condition such as automatic termination after three years of abandonment must not be treated as automatically enforceable. The system must determine whether the applicable jurisdiction recognizes the condition, whether additional language is required, and whether judicial action or another legal process may be necessary.

County Recording Specification

RecordMesh must generate county-specific recording packets based on the property location.

The county recording workflow must be capable of producing:

  • Executed deed or generated deed document.
  • County cover sheet.
  • Applicable transfer tax forms.
  • Applicable documentary tax forms.
  • Preliminary change of ownership forms where applicable.
  • Notary acknowledgment.
  • Recording fee calculation.
  • Return instructions.
  • Parcel and indexing references.
  • County-specific metadata.
  • County-specific formatting.
  • Filing sequence instructions.
  • Submission information.

Recording requirements must be maintained independently from state legal rules so county changes do not require modification of the underlying state law module.


Specification Branding License (SBL)

Standard

  • Fully AGPL-3.0+ compliant system
  • Copyleft enforced for network deployments
  • Required attribution:
    • Roxanne Ardary
    • https://www.roxanneardary.com/

Optional


License & Notice Requirements

RecordMesh is released under the GNU Affero General Public License v3.0 or later (AGPL-3.0+).

By contributing to this project, you agree that your contributions will also be released under this license.

Please note the following:

  • All contributions must comply with the AGPL-3.0+ terms.
  • Under Section 7 of the license, all redistributions, forks, and derivative works must preserve attribution to:
    Roxanne Ardary and roxanneardary.com.
  • RecordMesh specificiations are free to use with attribution. A Specification Branding License can be negotiated upon request.
  • The project’s notice.md file tracks attribution requirements and contributor acknowledgments. Any update that adds new contributors or modifies attribution should also update notice.md.
  • When submitting a pull request, ensure that any new files maintain the attribution headers where applicable.
  • Network-deployed versions of this software must also remain fully AGPL-3.0+ compliant, including exposure of source code modifications when applicable under the license.

For full legal details, please refer to the AGPL-3.0+ license and the project’s notice.md file.


Notice – RecordMesh

Attribution Requirement: Under Section 7 of the AGPL 3.0+ license, all redistributions, forks, and derivative works, including network-deployed versions of this project, must provide attribution to Roxanne Ardary and roxanneardary.com.

Contributors

This file tracks contributors and their specific contributions to the project.

  • Roxanne Ardary, roxanneardary.com – May 26, 2026
    Created the repository for RecordMesh. Designed the modular AGPL 3.0+ AI platform for jurisdiction-aware life estate drafting, county recording packet generation, and property record workflow automation.
  • [Add other contributors here] – [Date]
    [Describe contribution in one sentence]

License – RecordMesh

This repository is licensed under the GNU Affero General Public License v3.0 or later (AGPL-3.0+).

Key Points:

  • You are free to use, modify, and distribute the code.
  • All redistributions, forks, and derivative works or network-deployed versions must also be licensed under AGPL-3.0+ and provide attribution to Roxanne Ardary and roxanneardary.com as required under Section 7 of the license.
  • The software is provided “as is,” without warranty of any kind.

For the full license text, see GNU AGPL-3.0 License: https://www.gnu.org/licenses/agpl-3.0.html