The Velcro Model of Law: How Rules Connect to Facts

Legal engineering struggles with a fundamental problem: rules are abstract (e.g., "spouse"), but clients are specific (e.g., "Linda"). Bridging this gap usually requires custom code for every document.

This article introduces the "Velcro Model," a standardized interface that allows any legal rule to snap securely onto any client fact pattern without custom integration.

Key Concepts

Scalable legal tech requires a standard docking mechanism between law and data.

• Rule-Fact Binding — The protocol that defines which data points a rule needs to evaluate itself.
• Interface Standardization — Ensuring that a "Person" object looks the same to a Tax Rule as it does to a Family Law Rule.
• Dynamic Binding — The ability to swap out the underlying fact pattern (Client A vs. Client B) without rewriting the legal logic.

The Problem of Connection

In most systems, the document template asks for "Client Name." This hard-codes the connection. If you want to reuse that template for a Trust instead of a Will, or for a corporate client, the link breaks. You end up with brittle, one-off templates.

The Velcro Solution

Imagine every legal rule has a "hook" side (looking for a role, like "Grantor") and every fact has a "loop" side (holding the data). We build a universal adapter layer. When a rule needs a Grantor, it doesn't ask for a specific database field; it asks the adapter for the current Grantor context.

This allows us to "stick" a complex tax provision onto a client file instantly, and it just works because the interfaces align.

Conclusion

The Velcro Model turns legal drafting from a construction project into an assembly process. By standardizing the connections, we allow for infinite complexity in the rules and the facts, while keeping the system itself simple and robust.

Frequently Asked Questions

Is this an industry standard?

It is based on object-oriented programming principles applied to law, similar to the approach taken by advanced expert systems.

Does it work for all areas of law?

Yes, as long as the underlying ontology is correctly mapped.

Can we modify the bindings?

Yes, the adapter layer is configurable, allowing you to map "Client" to "Borrower" for a real estate transaction.

Sources & Further Reading

• Object-Oriented Legal Programming
• Future of Law Lab