diff --git a/_quarto.yml b/_quarto.yml
index 496b9e9..73bb863 100644
--- a/_quarto.yml
+++ b/_quarto.yml
@@ -29,6 +29,10 @@ book:
     - art.qmd
     - users.qmd
     - user_dev.qmd
+    - match.qmd
+    - longrun.qmd
+    - fundOS.qmd
+    - liability.qmd
     - references.qmd
 
 bibliography: references.bib
diff --git a/fundOS.qmd b/fundOS.qmd
new file mode 100644
index 0000000..d5e0a10
--- /dev/null
+++ b/fundOS.qmd
@@ -0,0 +1,26 @@
+---
+title: "Funding OS"
+---
+
+## Is it possible for industry fund open source?
+
+-   Is it possible to fund OS development in pharmaceutical drug and vaccine development?
+
+-   What might a funding model look like?
+
+-   What problem(s) would funding solve?
+
+-   Are there examples of this in other industries?
+
+## How to Contribute
+
+Contribute to the discussion here in GitHub Discussions:\
+[Is it possible for industry fund open source?](https://github.com/phuse-org/OSTCDA/discussions/13){target="_blank"}
+
+## Guidance
+
+-   Provide your thoughts and perspectives
+
+-   Provide references to articles, webinars, presentations (citations, links)
+
+-   Be respectful in this community
diff --git a/liability.qmd b/liability.qmd
new file mode 100644
index 0000000..274107e
--- /dev/null
+++ b/liability.qmd
@@ -0,0 +1,22 @@
+---
+title: "Liability with OS"
+---
+
+## Are contributors to open source exposing themselves to any liability of their solutions?
+
+-   What are possible sources of liabilities?
+
+-   Are there mitigating actions which can limit or eliminate liabilities?
+
+## How to Contribute
+
+Contribute to the discussion here in GitHub Discussions:\
+[Are contributors to open source exposing themselves to any liability of their solutions?](https://github.com/phuse-org/OSTCDA/discussions/14){target="_blank"}
+
+## Guidance
+
+-   Provide your thoughts and perspectives
+
+-   Provide references to articles, webinars, presentations (citations, links)
+
+-   Be respectful in this community
diff --git a/longrun.qmd b/longrun.qmd
new file mode 100644
index 0000000..58a06e8
--- /dev/null
+++ b/longrun.qmd
@@ -0,0 +1,27 @@
+---
+title: "OS in the Long Run"
+---
+
+## How do we ensure that the solutions being developed today will exist in the long run?
+
+When these solutions are embedded in data pipelines, if development and maintenance support disappears, there is a risk to the pipelines which leverage them.
+
+-   How do we ensure long term viability?
+
+-   How do we ensure long term sustainability?
+
+-   How do we ensure long term maintainability?
+
+## How to Contribute
+
+Contribute to the discussion here in GitHub Discussions:\
+[How do we ensure that the solutions being developed today will exist in the long run?](https://github.com/phuse-org/OSTCDA/discussions/12){target="_blank"}
+
+## Guidance
+
+-   Provide your thoughts and perspectives
+
+-   Provide references to articles, webinars, presentations (citations, links)
+
+-   Be respectful in this community
+
diff --git a/match.qmd b/match.qmd
new file mode 100644
index 0000000..d1b78dc
--- /dev/null
+++ b/match.qmd
@@ -0,0 +1,26 @@
+---
+title: "Numerical Matching"
+---
+
+## Do we need to match SAS numerically when using a different language?
+
+-   What if we the same inputs yield similar, but numerically different results?
+
+-   What if we the same inputs yield drastically different results?
+
+-   What is the truth? Which is correct?
+
+-   What if SAS and R are equivalent, but a third language yields numerical differences?
+
+## How to Contribute
+
+Contribute to the discussion here in GitHub Discussions:\
+[Do we need to match SAS numerically when using a different language?](https://github.com/phuse-org/OSTCDA/discussions/11){target="_blank"}
+
+## Guidance
+
+-   Provide your thoughts and perspectives
+
+-   Provide references to articles, webinars, presentations (citations, links)
+
+-   Be respectful in this community
diff --git a/users.qmd b/users.qmd
index c1ded4b..3942882 100644
--- a/users.qmd
+++ b/users.qmd
@@ -8,7 +8,7 @@ The conventional user (programmer) processing clinical trial data may be used to
 
 -   How can we help users to operate in a (potentially) more variable environment?
 
--   How can we help users to address unexpected challenges due to changes in their computational environment??
+-   How can we help users to address unexpected challenges due to changes in their computational environment?
 
 ## How to Contribute