CLO Entity

Counsel asks for the signed one. This is the signed one.

The executed contract

The archive hands back the executed contract — parties, terms, the fingerprint of the page that closed. Precedent, obligation, regulation, policy, and the last compliance decision sit in one store on the Memory install. Write a clause once. Ask later. Get that clause. The model on top can still draft. The store is the filing system.

That page lives on the buyer’s hardware — in the building or in the buyer’s own cloud. When the relationship ends, the memory stays. Monday still has Friday’s close. Counsel gets the executed file, not a recap rebuilt from a chat window or a shared drive the night before the room.

The executed contract. Parties, terms, fingerprint — the page that closed.

Export, assignment, the last redline

Three objects travel with that page. Export hygiene names the jurisdictions, the data that cannot leave, the license that would trip a control. Assignment names who owns the work, the IP that moved, the grant that was actually given. The last redline is the last redline — “material breach,” not a later rewrite of the fight.

Those three sit in the same archive as the executed file. The Contract Analyzer pulls parties, liability, termination, and IP assignment from the raw text and scores each clause so the store can keep the obligation. The Clause Library holds the house language in risk tiers, with fallback wording the house already vetted. When a draft drifts, the library proposes the playbook cut. Escalation takes the novel line. Speed on the routine. Counsel on the exception.

After close the same store extracts owner, date, and criticality. Renewal and expiry become a clock. The executed agreement sits in a tamper-evident record. The fingerprint of the signed page is the fingerprint counsel can show.

Prepare the package

A regulatory shift lands as a brief. The Regulatory Monitor scans filings, databases, and the industry press for a move that would touch this estate — privacy, antitrust, financial rules, export, data localization — and scores the impact against the product surface the archive already knows. The Change Tracker tags every bill and enforcement action by jurisdiction and relevance. A high score is a package: which product, which data flow, which contract family.

Prepare is the work before the meeting: pull the last version, surface the clause that changed, list the jurisdictions named in the paper, flag the export line, draft the redline, keep the trail of who asked and who answered. Prepare is also the work after: obligation tracking so a renewal window does not lapse, IP and open-source governance so a license conflict is a finding, a DSAR workflow that already knows which contract holds the data. Counsel walks into a brief that already names the clause that would have to move.

Prepare the package: the executed page, the export line, the assignment, the last redline.

Seven views, one record

Seven specialized views share the same legal record and fill that package:

• Contract Review — inbound and outbound paper against the playbook: jurisdictional conflict, enforceability, hidden liability, a redline ready for the desk.
• Regulatory Monitor — the pulse above. Potential change, scored against this estate.
• IP Protection — portfolio watch: trademarks, patents, trade secrets, open-source license obligations, supplier and competitor noise.
• Litigation Risk — early exposure scores on contract, product, and employment paper, plus a resolution path.
• Policy Drafter — living policies for privacy, acceptable use, and retention that update when the monitor fires.
• Privacy Counsel — GDPR, CCPA, DPIAs, DSAR workflows, cross-border transfers, consent frameworks.
• Vendor Legal — DPAs, SLAs, liability caps, approved-vendor status, third-party hygiene.

They close a loop. A new contract raises review. A new regulation raises the monitor and the drafter. A DSAR raises privacy. A security gap raises a joint package. The modules share the archive. The next obligation is louder because the last one was bound.

The bench behind the package

The rest of the bench sits behind the analyzer and the library. A legal risk matrix multiplies probability by impact so a clause and a reserve can share a number. An NDA generator carries jurisdiction and expiry. A privacy impact assessor maps the flow before the product ships. A license checker flags GPL and AGPL conflicts. A litigation timeline tracks statutes of limitation so the clock is visible before it runs out.

The CLO Entity is one of ten buyer-named chairs on the Memory install. CORE, DIVISION, and ENTERPRISE change how many seats travel with the archive. This seat is the legal and compliance door onto the same permanent store — on hardware they own, with a human line. The buyer picks which doors open first.

What the buyer is looking at

The chair prepares the package — executed contract, export hygiene, assignment, last redline — against an archive they own. A person signs. There are no customer logos on this page. $20 million is an ask — seed to put the first archives on customer hardware, not cash in hand.

Next in the catalog: CMO Entity.