The legal and compliance Drive. Generate privacy policies, terms of service, and full legal packs for every product and site you run, from one operating-entity profile.
Single-site legal tools price per site and treat every launch as a fresh form. TermDriver is built for the operator who'd rather not pay a lawyer's retainer for boilerplate. Define the operating entity once, and every new document inherits it. Generating documents is free and unlimited. Snapped into the Merkava cockpit, TermDriver gains the part that matters as you grow: it watches every document you've published and flags the ones that fall out of date as the law moves.
Twenty US states now enforce comprehensive privacy laws, eleven require Global Privacy Control recognition, and the list grows most years. TermDriver assembles the right clauses for the regions each document serves and keeps them current.
Conversational Forge intake assembles documents to how the business actually runs, not a fixed template.
Company details, contacts, and processors defined once and reused on every document you generate.
A law change or a vendor terms change flags every affected document and queues the fix.
Date-stamped, auto-updating policy pages on a permalink, plus HTML, Markdown, and PDF export.
A drop-in cookie consent banner snippet tied to each site's cookie policy.
Version history per document and a gate that holds a launch until its legal pack is in place.
TermDriver conforms to the Merkava Platform Contract. It exposes the standard contract endpoints so the cockpit can measure and monitor it with no per-Drive code.
@meridian/forge shared AI engine@meridian/auth operator identityentity-profile shared primitive@meridian/config and @meridian/loggerv1.0.0entity-profile:read reuse company detailsdocuments:write create and version documentsventures:read map docs to each site/api/meridian/health · metrics · events · billingThe machine-readable listing the marketplace and the cockpit read. Conforms to the Platform Contract manifest schema.
{ "drive": "term-driver", "name": "TermDriver", "category": "legal-compliance", "function_label": "OPS", "publisher": { "name": "Merkava", "verified": true }, "version": "1.0.0", "contract_version": "1.0.0", "engine": "forge", "pricing": { "core": "free", "cockpit_features": "merkava-subscription", "agency": "add-on" }, "surfaces": [ "cockpit-panel", "standalone:termdriver" ], "capabilities": [ "document.generate", "document.host", "document.version", "compliance.monitor" ], "dependencies": [ "@meridian/forge", "@meridian/auth", "entity-profile", "@meridian/config" ], "scopes": [ "entity-profile:read", "documents:write", "ventures:read" ], "endpoints": { "health": "/api/meridian/health", "metrics": "/api/meridian/metrics", "events": "/api/meridian/events", "billing": "/api/meridian/billing" }, "events_emitted": [ "custom.term-driver.document_generated", "custom.term-driver.policy_published", "custom.term-driver.compliance_flag_raised" ], "data_owned": [ "documents", "entity_profiles", "compliance_flags" ] }
A Drive is a modular component that snaps into the operator cockpit and runs on the shared Forge engine. First-party Drives cover the core operating functions. Third-party Drives extend the cockpit. Every Drive that handles money or data conforms to the same Platform Contract, so the cockpit measures all of them the same way.
Legal packs and compliance monitoring across everything you ship.
This DriveOutreach, lead capture, and deal tracking across ventures.
First-partyMarketing engine, content, and channel attribution.
First-partyMulti-tenant AI customer support, one inbox per venture.
First-partyMRR, runway, and unit economics across the business.
First-partyMulti-model decision room that plugs into the cockpit.
Community Drive