Trinity Capital

Description

Trinity Capital is a financial literacy SaaS web application designed for the public school system. Its designed to give students a hands on, safe simulation sandbox where they can learn money concepts before they get into the real world. Its designed to be a balance of realism, and engagement. The goal is that when students become adults or get their own bank accounts, they will be confident enough to handle their own finances without getting into trouble.

Details

💼 Trinity Capital — Financial Literacy Through Simulation

Trinity Capital is an interactive financial literacy platform built for high school students, designed to bridge the gap between classroom lessons and real-world money management. Unlike traditional budgeting games or static lessons, Trinity Capital combines real-time market data, custom lesson engines, and sandboxed simulations to create a living, breathing economy where students can safely learn how finance works.

At its core, Trinity Capital empowers educators to bring financial education to life. Teachers can build or customize lessons using a JSON-based template system, track student progress through analytics dashboards, and even simulate long-term financial consequences with “time travel” scenarios.

The system is built as a full-stack web application using modern web technologies, featuring:

Real-time simulation mode
Custom teacher dashboards for lesson planning and grading
Dynamic UI tracking for behavioral analytics
Secure integration with school systems and cloud hosting through MongoDB Atlas, Node.js, and Express

Trinity Capital is currently in its pilot phase with several approved Texas school districts, including Mesquite ISD, Burleson ISD, Birdville ISD, Fort Worth ISD, and Conroe ISD.

The project’s mission is simple:

“To teach the next generation that financial wisdom isn’t learned by watching — it’s learned by doing.”

Project Logs

Collapse

Actions are firing as intended now! (ILGE Adventures)
Jake Ferguson • 11/07/2025 at 02:08 • 0 comments

OK. Soi the ILGE continues to update smoothly. The CRM, and the UITM are working together smoothly for multiple different action types.

For review:

UITM (User Interface Tracking Module)
CRM (Condition Rendering Modal)

The two UI actions that are now firing are timed events and account switch events.

How the account switch works is when the UITM detects the account switch button, it checks the active lesson (You need to indicate the lesson is active by hitting the begin activities button)

for the conditions in that lesson. If the account switched is on there, it triggers the action for "account_switched"

This action can be anything the teacher assigns when they go and make a lesson. So account switch can do anything from send you a hooray message, to resetting your entire progress.

In this case, it just sends a message modal

The conditions also work for timed events too. I dont have a YT video for it, but they do work.

I have to plug in the rest of the UITM functions into the CRM to make it work, but at this point, we do know that the idea, and the concept for how this works is solid and reliable.

We will also at some point have to address saving student lesson times in mongoDB so that when a student logs back in, they can pick up their time where they left off.

Stay tuned for next time!
ILGE Adventures part 1
Jake Ferguson • 11/03/2025 at 21:08 • 0 comments
Ok, so the ILGE is the last major piece of the app that needs building before its ready for service.
The ILGE stands for Interactive Lesson and Grading Engine. Its designed to pull lesson data from a database, render them on the DOM, track DOM inputs, and use said inputs to track lesson progress, grading assignments, ext. Without this system, Trinity Capital basically becomes just a fancy bank simulator. Fun for some, not useful for students or teachers.

Above is the folder layout of all the modules and current files in the engine. As of now, there are going to be 4 major modules. Those are:
1. CRM (Condition Rendering Module) - Handles all of the teacher assigned conditions and handles rendering certain conditions (If a student saves $200, send them a congrats modal)
2. LRM (Lesson Rendering Module) - Responsible for pulling lesson data and displaying them on screen.
3. UITM (User Interface Tracking module) - Responsible for DOM tracking and sending DOM input data to the CRM and LGM
4. LGM - Lesson Grading Module - Responsible for tracking grades and student health for the teacher dashboard.
The LRM and UITM are the only modules that are finished as of now.

Right now, im working on the CRM. Its going to be a while before I can test the CRM because it needs to connect to the UITM in such a way as any data that comes in from the DOM can be checked against all conditions.