diff --git a/README.md b/README.md
index e69de29..1388a48 100644
--- a/README.md
+++ b/README.md
@@ -0,0 +1,3 @@
+---
+{}
+---
\ No newline at end of file
diff --git a/config.json b/config.json
new file mode 100644
index 0000000..39f57fd
--- /dev/null
+++ b/config.json
@@ -0,0 +1,44 @@
+{
+  "model": null,
+  "signature": {
+    "description": "Classify this email into exactly one of the following types.\n\nDefinitions:\n- action_request: The sender is asking the recipient to do something\n  specific (reply, send a file, approve, complete a task, etc.).\n- informational: The email conveys information, updates, or news without\n  a specific ask (status updates, FYIs, reports, summaries).\n- meeting_request: The primary purpose is scheduling, confirming, or\n  cancelling a meeting, call, or event.\n- newsletter: Bulk or automated distribution from an external service,\n  publication, or mailing list (market data feeds, industry newsletters,\n  promotional emails).\n- social: Casual personal correspondence \u2014 greetings, jokes, family\n  updates, chain emails, congratulations.\n- legal_notice: Regulatory filings, formal legal correspondence,\n  compliance notices, or attorney communications.\n\nChoose the single best-fit type.  When multiple types are plausible,\nprefer the type that best captures the primary purpose of the email.\n\nAs you reason, note any uncertainties, ambiguities, and gaps \u2014 both in\nhow the definitions apply to this email and in whether you have enough\ncontext to classify it confidently.",
+    "properties": {
+      "subject": {
+        "__dspy_field_type": "input",
+        "desc": "The email subject line (may be empty).",
+        "prefix": "Subject:",
+        "title": "Subject",
+        "type": "string"
+      },
+      "body": {
+        "__dspy_field_type": "input",
+        "desc": "The email body text (may be truncated).",
+        "prefix": "Body:",
+        "title": "Body",
+        "type": "string"
+      },
+      "email_type": {
+        "__dspy_field_type": "output",
+        "desc": "The email type \u2014 one of the six defined categories.",
+        "enum": [
+          "action_request",
+          "informational",
+          "meeting_request",
+          "newsletter",
+          "social",
+          "legal_notice"
+        ],
+        "prefix": "Email Type:",
+        "title": "Email Type",
+        "type": "string"
+      }
+    },
+    "required": [
+      "subject",
+      "body",
+      "email_type"
+    ],
+    "title": "EnronEmailTypeJudgeSig",
+    "type": "object"
+  }
+}
\ No newline at end of file
diff --git a/program.json b/program.json
new file mode 100644
index 0000000..c0032dc
--- /dev/null
+++ b/program.json
@@ -0,0 +1,40 @@
+{
+  "traces": [],
+  "train": [],
+  "demos": [],
+  "signature": {
+    "instructions": "Classify this email into exactly one of the following types.\n\nDefinitions:\n- action_request: The sender is asking the recipient to do something\n  specific (reply, send a file, approve, complete a task, etc.).\n- informational: The email conveys information, updates, or news without\n  a specific ask (status updates, FYIs, reports, summaries).\n- meeting_request: The primary purpose is scheduling, confirming, or\n  cancelling a meeting, call, or event.\n- newsletter: Bulk or automated distribution from an external service,\n  publication, or mailing list (market data feeds, industry newsletters,\n  promotional emails).\n- social: Casual personal correspondence \u2014 greetings, jokes, family\n  updates, chain emails, congratulations.\n- legal_notice: Regulatory filings, formal legal correspondence,\n  compliance notices, or attorney communications.\n\nChoose the single best-fit type.  When multiple types are plausible,\nprefer the type that best captures the primary purpose of the email.\n\nAs you reason, note any uncertainties, ambiguities, and gaps \u2014 both in\nhow the definitions apply to this email and in whether you have enough\ncontext to classify it confidently.",
+    "fields": [
+      {
+        "prefix": "Subject:",
+        "description": "The email subject line (may be empty)."
+      },
+      {
+        "prefix": "Body:",
+        "description": "The email body text (may be truncated)."
+      },
+      {
+        "prefix": "Email Type:",
+        "description": "The email type \u2014 one of the six defined categories."
+      }
+    ]
+  },
+  "lm": {
+    "model": "together_ai/Qwen/Qwen2.5-7B-Instruct-Turbo",
+    "model_type": "chat",
+    "cache": true,
+    "num_retries": 3,
+    "finetuning_model": null,
+    "launch_kwargs": {},
+    "train_kwargs": {},
+    "temperature": null,
+    "max_tokens": null
+  },
+  "metadata": {
+    "dependency_versions": {
+      "python": "3.11",
+      "dspy": "3.1.3",
+      "cloudpickle": "3.1"
+    }
+  }
+}
\ No newline at end of file