Legal Compliance Vault

Legal & Compliance Vault

What it is: Legal documents.

Overview

Works out the smallest useful Legal & Compliance Vault setup for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on request, from one field list so they cannot drift apart.

Layer: Layer 7: Protect. Fits: Growth stage. Table code: n/a.

When to Use This Skill

• legal document vault
• compliance document register
• licence register
• statutory records

Also use it when the user says "legal documents", or describes the same process happening in a spreadsheet, a document or someone inboxes.

Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces empty templates only - it never holds or processes real employee or customer data.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

• "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
• "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
• "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
• "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: What is the most urgent obligation?

Step 2 - Ask only what is missing

Skip anything the user already answered, in any earlier message. Ask the rest one at a time, and stop as soon as the remaining answers would not change the output.

• Obligations - Which laws or licences apply? / How many? / Any deadlines this year?
• Evidence - What proves compliance? / Where held? / Who signs off?
• Ownership - Who owns each obligation? / External counsel involved? / Review cadence?
• Current process - Is it tracked now? / Calendar or memory? / What is overdue?
• Outcome - What do you need? / An obligation register, a document list or both?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless they ask, and it never carries a value the user did not give.

module: legal-compliance-vault
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Obligations": null
  "Evidence": null
  "Ownership": null
  "Current process": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking

Step 4 - Recommend the smallest workflow

If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.

Recommended approach: Record each obligation with a deadline, an owner and the evidence that proves it, and review the overdue list first.

Why this one: Compliance risk concentrates in the few items that are due and unowned. A register with owners and dates is the whole control.

Workflow: Obligation listed → Owner assigned → Evidence linked → Due date tracked → Reviewed or filed

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the requested artifacts. For machine-readable text, keep prose outside the data; for files, provide a usable link. Report material validation failures or limitations separately.

A selected Notion output is rendered by notion-manual-import, so route the Notion step there. When the user selects Notion, hand that step to @notion-manual-import: it holds the CSV, the property mapping, the import steps and the verification checklist, and it renders the Field Reference below instead of defining a table of its own. Do not restate the mapping here and do not improvise the import steps. Manual CSV and mapping outputs need no connection. For requested workspace changes, follow the shared contract: verify actual tool access and the target before writing. A user saying "connected" is not tool evidence. Never ask for a Notion password or token.

For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the text correctly. A CSV is not an .xlsx workbook; create .xlsx only when the user requests a workbook. A CSV carries no types, so after it, name the columns that need a number, date or currency format applied.

Document Title,Document Type,Compliance Framework,Owner,Department,Effective Date,Expiry Date,Renewal Required,Storage Link,Confidentiality,Status,Legal ID
Master Services Agreement,Contract,ISO 27001,Sneha Iyer,Delivery,2026-01-15,2026-01-15,TRUE,https://example.com/doc,Internal,Active,

CREATE TABLE legal_compliance_vault (
  document_title VARCHAR(255),
  document_type VARCHAR(100) NOT NULL,
  compliance_framework VARCHAR(255),
  owner VARCHAR(255),
  department VARCHAR(255),
  effective_date DATE NOT NULL,
  expiry_date DATE NOT NULL,
  renewal_required BOOLEAN NOT NULL,
  storage_link TEXT,
  confidentiality VARCHAR(100) NOT NULL,
  status VARCHAR(100) NOT NULL,
  legal_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_legal_compliance_vault_status ON legal_compliance_vault (status);

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Legal & Compliance Vault",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Document Title": { "type": "string" },
      "Document Type": { "type": "string" },
      "Compliance Framework": { "type": "string" },
      "Owner": { "type": "string" },
      "Department": { "type": "string" },
      "Effective Date": { "type": "string", "format": "date" },
      "Expiry Date": { "type": "string", "format": "date" },
      "Renewal Required": { "type": "boolean" },
      "Storage Link": { "type": "string", "format": "uri" },
      "Confidentiality": { "type": "string" },
      "Status": { "type": "string" },
      "Legal ID": { "type": "integer" }
  },
  "required": [
      "Document Type",
      "Effective Date",
      "Expiry Date",
      "Confidentiality",
      "Status"
  ]
}

| CSV column | Notion property | Set after import |
|---|---|---|
| Document Title | Title | Use as the database title |
| Document Type | Select (add options after import) | Convert to Select, add options: "Contract", "Policy", "Invoice", "Certificate", "Report", "ID Proof", "Other" |
| Compliance Framework | Text | Leave as Text |
| Owner | Text | Leave as Text |
| Department | Text | Leave as Text |
| Effective Date | Date | Convert to Date |
| Expiry Date | Date | Convert to Date |
| Renewal Required | Checkbox | Convert to Checkbox |
| Storage Link | URL | Convert to URL |
| Confidentiality | Select (add options after import) | Convert to Select, add options: "Internal", "Public", "Confidential", "Restricted" |
| Status | Select (add options after import) | Convert to Select, add options: "Draft", "In Review", "Approved", "Active", "Expired", "Superseded" |
| Legal ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date, and anything pointing at another table stays relation.

Field Reference