diff --git a/pyproject.toml b/pyproject.toml
index 9a1e8c72..1040d06d 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -3,7 +3,7 @@ requires = ["setuptools>=61.0"]
 build-backend = "setuptools.build_meta"
 [project]
 name = "math-spec-mapping"
-version = "0.3.13"
+version = "0.3.14"
 authors = [
   { name="Sean McOwen", email="Sean@Block.Science" },
 ]
diff --git a/research_notes/2024-11-13 Predator-Prey Reverse Engineering.md b/research_notes/2024-11-13 Predator-Prey Reverse Engineering.md
new file mode 100644
index 00000000..07b54170
--- /dev/null
+++ b/research_notes/2024-11-13 Predator-Prey Reverse Engineering.md	
@@ -0,0 +1,78 @@
+# Predator-Prey Reverse Engineering Example
+
+## Executive Summary
+
+- As part of an effort to make high quality canonical examples, a predator-prey model is being iterated on to show a full end-to-end modeling workflow and the repository can be found [here](https://github.com/BlockScience/Predator-Prey-Canonical-Example)
+- Today we will go through the process of reverse engineering a past repository of code and updating it to be an MSML-compliant spec
+- This specific type of ideation is often done when presented with a system that is already in a production enviroment but needs to be modeled through simulations or digital twins
+
+## Predator-Prey Background
+
+- The Predator-Prey model is often used as an example in mathematics classes to illustrate equilibrium behaviors and modeling for it
+- Generally, the model is for representing the Lotka–Volterra equations, which are first order, non-linear differential equations
+- However, for our purposes, and purposes of the legacy model, we impose a discrete time to the system and model it instead as an agent-based simulation
+- The legacy model used comes from the [cadCAD demos repository](https://github.com/cadCAD-org/demos/tree/master/demos/Agent_Based_Modeling/prey_predator_abm) and is ported into Obsidian
+- Let's quickly look at what the old model looked like!
+
+## Predator-Prey Reverse Engineering Ideation
+
+- The [Predator-Prey-Ideation repository](https://github.com/BlockScience/Predator-Prey-Ideation/tree/main) is the repository for the ideation phase of the canonical example. Currently reverse engineering code is the only example but there will be more in the future.
+- Legacy code review is done to take a current version of a system and break it down into MSML/GDS style blocks and spaces
+- It can be free form but overall the goal should be piecing together the beginning of a scaffold to be ported into MSML
+- This can also be done in tandem with a literature review
+- The steps followed were:
+1. Port all relevant code into the "Legacy Code Review"
+2. Create the folder of "MSML Scaffold" and start to link pieces of the legacy code files to their counterparts in an MSML scaffold
+3. A second "MSML Scaffold 2" folder was created and copied over from "MSML Scaffold" with a canvas for organizing the wirings so that it could be refined (this can be done in one folder normally but for illustrative purposes was broken out)
+4. The "write_issues.ipynb" notebook was used to automatically write issues from the scaffold into the MSML repository which is where the next steps will come in
+
+
+### Code Porting
+
+- The folder of Predator-Prey-Obsidian-Legacy-Code was created and then markdown files were created to map directly to the legacy code
+![Code Porting Folder Strucutre](CodePortingFolderStrucutre.png)
+- Each section had its code pasted in, for example, the code for "parts/agents":
+![Parts Agents](PartsAgents.png)
+
+### MSML Scaffold 1
+
+- For the first round, an MSML scaffold was built out to hold different components that were gleaned from reviewing the code
+- Each part of the Predator-Prey-Obsidian-Legacy-Code folder had a #WIP at the top to denote that it still needed to be parsed in
+- For example, the PSUBs code was used to scaffold what the wirings loosely should be:
+![PSUB Code](PSUBCode.png)
+- And code can be copied into specific notes, such as the wiring shown below
+![Wiring](Wiring.png)
+- Some more notes were added to the scaffold but if you look it will not be complete, rather we can refine once we finish porting all the code and baseline structure we want
+
+### MSML Scaffold 2
+
+- The second scaffold is where refinement and going deeper happens
+- The first thing that was done was breaking down each wiring into the specific components and showcasing it using an Obsidian canvas
+- The linked notes will show filled in notes at this point, but in the beginning most of these notes will be empty or close to empty (and also can have #WIP added to flag what still needs to be finished)
+- The canvas looks like (it is too large to display the entire thing):
+![Obsidian Canvas](ObsidianCanvas.png)
+- Notes then can be filled in with the components of what will become the JSON representation, such as the "Agent Reproduction Boundary Action":
+![Agent Reproduction](AgentReproduction.png)
+
+### Issue Writing
+- By using the "write_issues.ipynb" which is a wrapper around MSML's new feature for github issue writing, one can automatically write github issues to the MSML repository (or the same repository)
+- In the [Predator-Prey-MSML Repository](https://github.com/BlockScience/Predator-Prey-MSML) one can see the issues (which at the time of this writing are in progress)
+- The issues that were automatically written are shown below:
+![MSML Git Issues](MSMLGitIssues.png)
+- The automatic issue writer also creates a checklist of components for each issues that need to be solved, shown below:
+![Git Issue](GitIssue.png)
+- One can also convert a checkbox into its own issue if they choose using the git functionality displayed above by moving their mouse into that location
+
+### Moving on to MSML
+- Now one can take the scaffold repository and move it into the Obsidian report folder if they want
+- By disabling the folder overwriting in the "Write Spec" notebook, you can even have it be that you are only overwriting notes which you have filled in the spec components for
+- And the github issues make it nice and easy to track what you still need to implement
+- Let's take a look at the current Predator-Prey-MSML repository!
+
+## Conclusion
+
+- This is only one potential way to go about ideation but it proves to be a powerful method
+- Moving forward the MSML specification is going to be completed for use as the second phase of the canonical example
+
+## Questions?
+- Feel free to ask any questions or give any thoughts!
\ No newline at end of file
diff --git a/research_notes/AgentReproduction.png b/research_notes/AgentReproduction.png
new file mode 100644
index 00000000..8e453c3e
Binary files /dev/null and b/research_notes/AgentReproduction.png differ
diff --git a/research_notes/CodePortingFolderStrucutre.png b/research_notes/CodePortingFolderStrucutre.png
new file mode 100644
index 00000000..c5dd11d4
Binary files /dev/null and b/research_notes/CodePortingFolderStrucutre.png differ
diff --git a/research_notes/GitIssue.png b/research_notes/GitIssue.png
new file mode 100644
index 00000000..8d6a01dd
Binary files /dev/null and b/research_notes/GitIssue.png differ
diff --git a/research_notes/MSMLGitIssues.png b/research_notes/MSMLGitIssues.png
new file mode 100644
index 00000000..536012e7
Binary files /dev/null and b/research_notes/MSMLGitIssues.png differ
diff --git a/research_notes/ObsidianCanvas.png b/research_notes/ObsidianCanvas.png
new file mode 100644
index 00000000..e59057ab
Binary files /dev/null and b/research_notes/ObsidianCanvas.png differ
diff --git a/research_notes/PSUBCode.png b/research_notes/PSUBCode.png
new file mode 100644
index 00000000..c2058c46
Binary files /dev/null and b/research_notes/PSUBCode.png differ
diff --git a/research_notes/PartsAgents.png b/research_notes/PartsAgents.png
new file mode 100644
index 00000000..c512a608
Binary files /dev/null and b/research_notes/PartsAgents.png differ
diff --git a/research_notes/Wiring.png b/research_notes/Wiring.png
new file mode 100644
index 00000000..a868fa2f
Binary files /dev/null and b/research_notes/Wiring.png differ
diff --git a/src/math_spec_mapping/Convenience/__init__.py b/src/math_spec_mapping/Convenience/__init__.py
index f2bb397a..65f6c89e 100644
--- a/src/math_spec_mapping/Convenience/__init__.py
+++ b/src/math_spec_mapping/Convenience/__init__.py
@@ -1,2 +1,3 @@
 # from .documentation import write_top_level_json_description
 from .starter import remove_dummy_repo_components
+from .github import write_scaffold_to_github_issues
diff --git a/src/math_spec_mapping/Convenience/github.py b/src/math_spec_mapping/Convenience/github.py
new file mode 100644
index 00000000..006bf76b
--- /dev/null
+++ b/src/math_spec_mapping/Convenience/github.py
@@ -0,0 +1,34 @@
+import os
+import requests
+
+
+def write_scaffold_to_github_issues(
+    scaffolder_folder, repo_owner, repository_name, access_token
+):
+    folders = [
+        x
+        for x in os.listdir(scaffolder_folder)
+        if os.path.isdir(scaffolder_folder + "/" + x)
+    ]
+    headers = {
+        "Accept": "application/vnd.github+json",
+        "X-GitHub-Api-Version": "2022-11-28",
+        "Authorization": "Bearer {}".format(access_token),
+    }
+    for folder in folders:
+        issue_name = "Write {} from MSML Scaffold".format(folder)
+        checklist = [
+            x[:-3]
+            for x in os.listdir(scaffolder_folder + "/" + folder)
+            if x.endswith(".md")
+        ]
+        checklist = ["- [ ] " + x for x in checklist]
+        checklist = "\n".join(checklist)
+
+        requests.post(
+            "https://api.github.com/repos/{}/{}/issues".format(
+                repo_owner, repository_name
+            ),
+            headers=headers,
+            json={"title": issue_name, "body": checklist},
+        )
diff --git a/src/math_spec_mapping/Reports/markdown.py b/src/math_spec_mapping/Reports/markdown.py
index 637ce85a..97caaf71 100644
--- a/src/math_spec_mapping/Reports/markdown.py
+++ b/src/math_spec_mapping/Reports/markdown.py
@@ -374,6 +374,12 @@ def write_control_action_markdown_report(ms, path, control_action, add_metadata=
         out += "\n"
     out += "\n"
 
+    out += "## Parameters Used\n"
+    for i, x in enumerate(sorted(control_action.parameters_used, key=lambda x: x)):
+        out += "{}. [[{}]]".format(i + 1, x)
+        out += "\n"
+    out += "\n"
+
     if control_action.control_action_options:
         out += "## Control Action Options:\n"
         for i, x in enumerate(control_action.control_action_options):
@@ -509,6 +515,7 @@ def write_parameter_markdown_report(ms, path, parameter, add_metadata=True):
             )
 
     out += "Description: {}\n\n".format(param.description)
+    out += "Type: [[{}]]\n\n".format(param.variable_type.name)
     out += "Symbol: {}\n\n".format(param.symbol)
     out += "Domain: {}\n\n".format(param.domain)
     out += "Parameter Class: {}\n\n".format(param.parameter_class)
diff --git a/src/math_spec_mapping/__init__.py b/src/math_spec_mapping/__init__.py
index 530fcaa7..d66dc7c1 100644
--- a/src/math_spec_mapping/__init__.py
+++ b/src/math_spec_mapping/__init__.py
@@ -30,6 +30,6 @@
     write_parameter_table_markdown,
 )
 from .schema import schema
-from .Convenience import remove_dummy_repo_components
+from .Convenience import remove_dummy_repo_components, write_scaffold_to_github_issues
 
 # from .Convenience import write_top_level_json_description