diff --git a/meeting-notes/2025-07-03 data model review.md b/meeting-notes/2025-07-03 data model review.md
new file mode 100644
index 0000000..3225010
--- /dev/null
+++ b/meeting-notes/2025-07-03 data model review.md	
@@ -0,0 +1,16 @@
+Attendees: @kiara @fricklerhandwerk
+
+- Discussed @fricklerhandwerk's WIP branch for implementing https://git.fediversity.eu/Fediversity/Fediversity/issues/103
+- The resource policy idea seems sound
+- The test sample doesn't look minimal at first glance, but in fact is
+  - An entire NixOS configuration is only minimal in terms of resource policy -- just put it in a VM
+  - An application that configures a whole NixOS needs to set many more things to make it run
+  - The login-shell sample also allows us to explicitly enumerate resource-specific configuration options to demonstrate how they're declared and used
+- We re-iterated on the stance not to touch actual applications before we have the whole workflow tested with samples
+  - Our packaged applications are already tested and in a state where we could translate them to the proper data model mechanically once it's in place and well-understood, so this will be a well-scoped problem for next year
+- It emerged again that we need to figure out a notion of compatibility (and therefore versioning) before being able to model migrations
+  - Once the data model draft type-checks and the tests pass, this will be the next research question
+  - We need to check if we want or have to make simplifying assumptions, such as not allowing version rollbacks
+  - Chances are, once we have compatibility clarified, migrations will be trivial
+- @kiara will spend some time today debugging the draft
+- Likely we'll need the next week to finish that part and play with it a bit, such as by adding a few more test cases.
\ No newline at end of file