Grace Legacy Academy

An invite-only adult learning platform pairing founder-authored curriculum with deterministic, bounded guidance, real access controls, and a representative R³ Framework pathway.

Comment

Inspiration

What it does

How we built it

Challenges we ran into

Accomplishments that we're proud of

What we learned

What's next for Grace Legacy Academy

Inspiration

Grace Legacy Academy grew from a recurring problem: adults can finish books, courses, and personal-growth programs with plenty of information but no safe, structured answer to “What should I do next?” Nicole Sosa created the underlying Unified Theory of Redemption, curriculum, educational architecture, and product vision to bridge that gap.

What it does

Grace Legacy Academy is an invite-only adult learning platform built around founder-authored curriculum, real authentication, explicit entitlements, and intentionally bounded educational guidance.

The representative judge pathway includes a protected Module 3 R³ Framework lesson, its read-only workbook transition, and Grace Companion. Student Grace is deterministic: it matches approved topics to registry-grounded guidance, returns a fixed safe response when no topic matches, stores no conversation, and makes no model call. Students are denied access to founder administration and protected source material.

How we built it

The production implementation uses Next.js, React, TypeScript, Node.js, and MariaDB/MySQL behind HTTPS with Nginx and a loopback application service. Server-side sessions, roles, account states, and entitlements replace browser-only simulation. Founder operations are separately protected and auditable. The release also includes targeted verification, security boundaries, accessibility work, backup and recovery controls, and atomic deployment practices.

Before Build Week, Nicole had completed the product vision, curriculum, educational architecture, and a local Next.js scaffold with mock roles and protected-material concepts. During Build Week, that foundation was meaningfully extended into the accepted production implementation: database-backed authentication and sessions, enforceable founder/student separation, deterministic Student Grace, the representative Module 3 lesson/workbook pathway, founder governance controls, production deployment, security hardening, accessibility verification, recovery operations, and documented acceptance evidence.

Codex and GPT-5.6 collaboration

Nicole directed the product, curriculum, audience, governance model, privacy and security boundaries, feature priorities, acceptance testing, and release decisions. Codex and GPT-5.6 accelerated source inspection, implementation, refactoring, debugging, security analysis, targeted verifiers, production builds, private QA, deployment engineering, recovery controls, and submission documentation.

GPT-5.6 was the Codex development collaboration model—not the application runtime. Student Grace is deterministic and makes no model calls.

Challenges

The central challenge was making guidance useful without turning it into an unrestricted chatbot. We designed Grace around approved resources, explicit topic matching, safe no-match behavior, and clear professional-care and protected-source boundaries. A second challenge was converting a local scaffold into a real production pathway while preserving least privilege, privacy, and founder authority.

Accomplishments

  • A coherent, working production student pathway rather than a mock login
  • Real authentication, authorization, and entitlement enforcement
  • A protected Module 3 R³ lesson and read-only workbook transition
  • Deterministic supported-topic guidance and bounded no-match behavior
  • Student denial from founder administration
  • Clear Pre-Build Week versus Build Week evidence
  • A clean private judging repository and least-privilege judge account

Intentional limitations

This Build Week release intentionally excludes public registration, commerce, email notifications, writable student progress, automated completion, PDF/file delivery, and public access to founder administration. Wounded But Wiser and future curriculum editions are not part of the public judge student experience. The project makes no clinical claims and does not replace professional care.

What's next

After Build Week, development can continue toward broader curriculum pathways, progress tracking, enrollment and commerce workflows, and expanded founder tools—without weakening the bounded guidance and governance model demonstrated here.

Built With

Share this project:

Updates

posted an update —

One Month Later: From Build Week Project to Grace Legacy Ecosystem

It has been just over a month since I submitted Grace Legacy Academy for OpenAI Build Week, and the project has continued evolving much faster than I expected.

During Build Week, the goal was to transform an existing educational prototype into a secure, production-oriented learning platform. That release introduced real authentication, server-side authorization, deterministic Grace Companion guidance, founder administration, production security, monitoring, backup/recovery, and an invite-only deployment.

I thought I had built the platform.

It turns out I had built the foundation.

What has happened since Build Week

Grace Legacy Academy has continued maturing. The production Academy remains live and healthy, while a separate private staging environment now supports continued curriculum and platform development. Orientation and Modules 1–11 have been consolidated into the current staging release for founder acceptance and testing.

Grace Companion remains intentionally bounded. The student experience continues to use deterministic, founder-approved guidance rather than unrestricted generative AI. As the ecosystem expands, that original Build Week principle remains unchanged: technology should help learners navigate trusted resources without becoming the authority over the learning process.

Wounded But Wiser™ has grown from an extension into its own platform architecture. During Build Week, WBW existed as a controlled private extension of the Academy. Since then, an independent WBW platform has been developed and tested locally, with its own role in the ecosystem focused on coaching journeys, workbooks, reflections, client resources, and coaching progress.

The R³ Framework is becoming an operational system. The founder-approved R³ reference has been preserved as an immutable canonical version while a separate, governed validation process has been developed around it. This allows the framework to be evaluated without casually changing the underlying theory or exposing unfinished validation tools publicly.

The ecosystem architecture has become much clearer. Instead of forcing every function into one application, Grace Legacy is evolving into a group of purpose-specific systems:

Grace Legacy Academy owns structured learning, academic progress, certifications, and student resources.

Wounded But Wiser™ owns coaching journeys, reflections, workbooks, client libraries, and coaching progress.

Grace Companion provides bounded guidance within approved contexts.

Shared services are being designed for commerce, authentication/account linking, scheduling, notifications, storage, analytics, backups, monitoring, and other ecosystem-wide functions.

Founder Operations is being designed as the governance layer across those systems.

The goal is not simply to add more features. It is to make sure each part of the ecosystem has a clear responsibility, appropriate boundaries, and an auditable relationship with the others.

What I learned after Build Week

Build Week answered the first question:

Can this educational architecture become real software?

Yes.

The month since submission has been about the much harder second question:

What architecture is required for real people to safely move through an entire ecosystem built around it?

That has meant slowing down in some places, separating systems that should not be combined, strengthening governance, testing boundaries, building staging environments, preserving canonical versions, and resisting the temptation to send traffic into an ecosystem before the ecosystem is ready to receive it well.

Codex continues to serve as my engineering collaborator throughout that process. I remain responsible for the product architecture, curriculum, governance, acceptance decisions, and final direction, while AI dramatically accelerates implementation, testing, documentation, and technical iteration.

A month ago, I submitted Grace Legacy Academy as a Build Week project.

Today, I can see much more clearly that the Academy is one part of a larger Grace Legacy ecosystem.

And we're still building.

Log in or sign up for Devpost to join the conversation.

Submission history