shield-compliance

name	shield-compliance
version	2.0
type	autoresearch
description	Legal research and compliance automation
user-invocable	true
agent	SHIELD
agent_model	claude-opus-4-6
mcps	["paperclip","github","filesystem"]
gstack_skills	["/cso","/investigate","/review"]
eval_metric	compliance_coverage
eval_budget	120s
guard	legal_accuracy > 0.95

/shield-compliance — Legal & Compliance Automation

What it does

Automates legal research, contract drafting, and compliance monitoring using Paperclip for statute/case law fetching, GitHub for document versioning, and gstack's security audit for tech compliance.

Protocol

Step 0: Load context

• memory/LEGAL_MEMORY.md — active legal matters, filed docs
• star-voss/ATTORNEY_PACKAGE.md — litigation state
• dark-factory/LOI_*.md — active deal documents
• HENRY_BRAIN.md — legal priorities

Step 1: Legal research (Paperclip)

Fetch current statutes and regulations:

CPA Acquisitions:

• TX Occupations Code §513.11 — Non-CPA ownership rules
• TX Business Organizations Code — entity formation
• SBA 7(a) compliance requirements
• IRS rules for practice acquisitions

Star Voss Litigation:

• TX Property Code §92.052 (habitability)
• TX Property Code §92.056 (failure to repair)
• TX Property Code §92.331 (retaliation)
• TX DTPA §17.46 (deceptive practices)
• Harris County court filings and docket

RIA Registration:

• TX State Securities Board requirements
• SEC vs. state registration thresholds
• Form ADV filing requirements

Step 2: Document drafting

For each document type:

LOIs: Use HENRY standard template:

• Purchase price at 0.4x revenue
• 10% earnest money
• 90-day due diligence period
• Seller transition: 6-12 months
• Non-compete: 3 years, 50-mile radius
• SBA 7(a) financing contingency

NDAs: Standard mutual NDA for buyer package requests

Compliance checklists: Per regulatory body

Step 3: Security audit (/cso)

For any tech deliverable:

• Run /cso OWASP Top 10 + STRIDE audit
• Flag any data handling that touches client PII
• Verify encryption for financial data

Step 4: Document review (/review)

For existing documents:

• Run /review for completeness and accuracy
• Cross-reference with current statutes (Paperclip refresh)
• Flag any clauses that may be unenforceable

Step 5: Version control (GitHub)

• All legal documents tracked in git
• Each revision gets a commit with context
• Never overwrite without preserving history

Step 6: Route outcomes

• LOI ready → CLOSER for submission
• Compliance issue → ATLAS for strategic decision
• Litigation update → Update attorney package

Active Legal Matters

Matter	Type	Status	Next Action
TXS5345 LOI	Acquisition	Drafted	Submit
TXS5513 NDA	Acquisition	Needed	Draft after package received
Star Voss	Litigation	Active	Attorney follow-up
RIA Registration	Compliance	Not filed	Start filing
TX Non-CPA Ownership	Compliance	Confirmed OK	Document

Autoresearch Loop

• Metric: compliance_coverage — % of applicable regulations addressed in documents
• Budget: 120s eval
• Modify: document templates, research sources, compliance checklists
• Guard: legal_accuracy must stay above 95% (verified against current statute text)

MCP Integration Map

SHIELD (Opus 4.6)
  ├── paperclip: fetch statutes, case law, regulations, filings
  ├── github: version control for all legal docs
  ├── filesystem: read/write legal documents
  ├── /cso: OWASP + STRIDE security audit
  ├── /investigate: root-cause for compliance gaps
  └── /review: document completeness review