Add initial JSON data files and implement core page components for game functionality

README.md

@@ -1,6 +1,4 @@
-# Welcome to your Expo app 👋
-
-This is an [Expo](https://expo.dev) project created with [`create-expo-app`](https://www.npmjs.com/package/create-expo-app).
+# Welcome to the mobile application development repository for our Treasure Hunt Game! This project is built using React Native and Expo.
 
 ## Get started
 
@@ -16,35 +14,49 @@ This is an [Expo](https://expo.dev) project created with [`create-expo-app`](htt
    npx expo start
    ```
 
-In the output, you'll find options to open the app in a
 
-- [development build](https://docs.expo.dev/develop/development-builds/introduction/)
-- [Android emulator](https://docs.expo.dev/workflow/android-studio-emulator/)
-- [iOS simulator](https://docs.expo.dev/workflow/ios-simulator/)
-- [Expo Go](https://expo.dev/go), a limited sandbox for trying out app development with Expo
 
-You can start developing by editing the files inside the **app** directory. This project uses [file-based routing](https://docs.expo.dev/router/introduction).
+# Database Structure
 
-## Get a fresh project
+This project uses split JSON files in `DB/` so each collection behaves like its own REST endpoint.
 
-When you're ready, run:
+## Purpose
 
-```bash
-npm run reset-project
-```
+- Keep data modular and readable.
+- Mirror server-side endpoint structure before moving to a hosted REST API.
+- Allow the app to load all collections into one in-memory state via `app/Model/DbController.js`.
 
-This command will move the starter code to the **app-example** directory and create a blank **app** directory where you can start developing.
+## Files
 
-## Learn more
+- `meta.json`: global version and numeric ID counters.
+- `users.json`: user accounts and role state (`Uid`, `Gid`, `SGid`, `TGid`, `IsAcceptedAdmin`).
+- `groups.json`: top-level game groups (`Gid`), admin approvals, and group settings.
+- `subgroups.json`: subgroup definitions within each group (`SGid` scoped by `Gid`), join codes, cache trigger defaults.
+- `subgroup-memberships.json`: membership bridge from `Uid` to `Gid`/`SGid`.
+- `admin-waitlist.json`: pending admin requests for groups when active admins already exist.
+- `teams.json`: team entities for non-admin subgroup players.
+- `team-members.json`: membership bridge from `Uid` to `Tid`.
+- `game-data.json`: per-group game payloads (geocaches, map/game objects).
+- `game-types.json`: available game type options for UI flow.
+- `db.json`: index file listing split JSON resources.
 
-To learn more about developing your project with Expo, look at the following resources:
+## ID Rules
 
-- [Expo documentation](https://docs.expo.dev/): Learn fundamentals, or go into advanced topics with our [guides](https://docs.expo.dev/guides).
-- [Learn Expo tutorial](https://docs.expo.dev/tutorial/introduction/): Follow a step-by-step tutorial where you'll create a project that runs on Android, iOS, and the web.
+- `Uid`: unique user ID.
+- `Gid`: unique group/game ID.
+- `SGid`: subgroup ID within a group (`0` is admin subgroup).
+- `Tid`: unique team ID.
 
-## Join the community
+## Admin Logic
 
-Join our community of developers creating universal apps.
+- Group creator is set as admin (`SGid = 0`) and accepted.
+- New admin join requests go into `admin-waitlist.json` if active admins exist.
+- If no active admin exists, the requester is auto-promoted to accepted admin.
+- Group-level `ApprovedAdmins` stores accepted admin `Uid` values.
+
+## Timestamp Format
+
+- `CreatedAt` values are stored at minute precision:
+  - format: `YYYY-MM-DDTHH:mmZ`
+  - example: `2026-03-17T14:42Z`
 
-- [Expo on GitHub](https://github.com/expo/expo): View our open source platform and contribute.
-- [Discord community](https://chat.expo.dev): Chat with Expo users and ask questions.