aisd-cinematic-redesign

A derivative cinematic frontend redesign for an AI-assisted coding-assessment platform with explicit attribution and module-boundary notes.

aisd-cinematic-redesign

Why this article exists

This project is where visual craft had to serve an operational interface. The redesign is not just about making an academic platform look cinematic; it is about pacing student/admin workflows, browser IDE state, AI assistance, submission evaluation, and reporting without blurring security boundaries.

Problem

A coding-assessment product needs clearer hierarchy, workspace persistence, role-based administration, AI-assistance boundaries, and frontend/backend contract clarity.

What shipped

Next.js frontend redesign, ASP.NET backend context, HyperFrames motion source, rendered motion media, frontend API client, Figma reference, design discussion, attribution, and acceptance criteria.

Evidence

The README records the upstream commit, unlicensed-source boundary, attribution file, module responsibilities, useful routes, backend assumptions, API notes, and security rules.

Inspect path

Inspect `ATTRIBUTION.md`, `FINAL_ACCEPTANCE_CRITERIA.md`, `docs/frontend-cinematic-redesign-discussion.md`, `hyperframes/aisd-motion/`, and frontend workspace routes.

Boundary

The repository is a derivative redesign of an upstream academic project; attribution is explicit and does not claim a license grant from the upstream source.

What changed

The craft boundary became clearer: motion is useful only when it clarifies hierarchy, pacing, and the next object a student or admin should inspect.

Next question

Which interaction should become calmer before the motion system becomes more ambitious?

Open public repository

https://github.com/89325516/aisd-cinematic-redesign