aisd-cinematic-redesign

Can cinematic interface craft clarify a coding-assessment workflow without hiding roles, backend assumptions, attribution, or security boundaries?

aisd-cinematic-redesign

Why this article exists

What does visual craft help if it makes an operational interface prettier but less clear? This 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, frontend/backend contract clarity, and explicit attribution when the work derives from an upstream academic project.

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/`, frontend workspace routes, and API boundary assumptions.

Boundary

The repository is a derivative redesign of an upstream academic project. Attribution is explicit, and the page should not imply a license grant, production deployment, or full backend ownership beyond what the repository states.

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