In-development learning platform · agent-assisted implementation

TuringSquare-LMS

Administrator, teacher, curator and student roles, course entitlements, and one-time/subscription payments must remain consistent under retries and network failures.

The project code is private. This case study intentionally excludes secrets, personal data, and operational identifiers.
01

Problem

Administrator, teacher, curator and student roles, course entitlements, and one-time/subscription payments must remain consistent under retries and network failures.

02

Constraints

Roles, course entitlements, duplicate orders and T-Bank verification; payment intent alone does not grant access.

03

Solution

I define and review ASP.NET Core/PostgreSQL contracts and T-Bank payment requirements: order idempotency and authoritative provider state checks before entitlement grants. Parts of implementation were produced by AI agents.

04

Outcome

Work in progress: checks and sandbox payments do not establish production readiness. No internal coin-wallet model.

05

Verification

Review of role and entitlement checks, T-Bank sandbox payment verification, migrations and critical flows; no production launch.

06

My ownership

Architecture and acceptance criteria; review of agent-generated roles, entitlements and T-Bank sandbox payments.