Neo Implementation Plan

This plan translates the project guidelines into the first implementation slices for Neo Academy, the Neo agent harness, and the EpsilonDelta Tech documentation site.

Product Boundaries

Neo Academy

Custom LMS for AI courses and certifications. The target stack is Django for the backend, Next.js for the frontend, and Razorpay for payments.

Neo Agent Harness

Progressive coding-agent harness for learning, experimentation, evaluation, replay, and production hardening.

Documentation Site

Mobile-responsive public documentation for shipped features, APIs, deployment notes, business workflows, and agent handoff context.

Reimplementation Prompt

Use this prompt when starting a focused worker or a new repository implementation:

Build Neo Academy as a resource-conscious AI certification LMS for EpsilonDelta Tech.
Use a Django backend, a Next.js frontend, and Razorpay payments.
Implement the first complete path: course catalog, course detail, enrollment, payment initiation, learner progress, certificate issuance, certificate verification, and an admin dashboard.
Keep Neo Academy separate from the Rust Neo agent harness and its documentation.
Document every API, environment variable, deployment step, and administrator workflow on the documentation site.
Target a small VPS first: 2 CPU cores, 8 GB RAM, and 100 GB disk.
Avoid embedded secrets, unnecessary Docker services, and broad refactors.
Prefer clear interfaces, low memory usage, mobile-responsive pages, and testable feature slices.

Repository Split Plan

Area	Temporary location	Target ownership	First stable interface
Academy MVP	`website/academy/` for static prototype pages	Private Neo Academy repository	Course, enrollment, payment, progress, certificate, and verification APIs
Agent harness	`src/`, `crates/`, `examples/`, and harness docs	Current Neo harness repository	CLI commands, provider config, worker isolation, replay, and benchmark contracts
Documentation	`website/docs/`	Public EpsilonDelta Tech documentation site	Feature docs, API contracts, deployment notes, and validation commands

Implementation Phases

Phase 1: Stabilize the current repo

Remove tracked secrets, document deployment environment variables, keep the static Academy prototype intact, and publish this implementation plan.

Phase 2: Define Academy contracts

Create API contracts for courses, enrollment, payments, progress, certificate issuance, certificate verification, and admin analytics before scaffolding a private repository.

Phase 3: Build the MVP path

Implement the learner purchase-to-certificate workflow with mobile-responsive pages, low-resource deployment settings, and focused backend tests.

Phase 4: Expand harness learning demos

Turn the existing agent-harness docs and courses into guided exercises with replayable tasks, validation commands, and certificate checkpoints.

Acceptance Criteria

No secrets are committed in configs, scripts, examples, containers, or documentation.
Academy, harness, and documentation work stay in separate patches unless a feature explicitly crosses boundaries.
Every shipped feature includes user-facing docs, admin notes, validation steps, and mobile checks.
Deployment remains suitable for the current small VPS until traffic requires a larger architecture.