EdTech / AI research
Long-term student memory: from hypothesis to a working service
A neuromorphic memory core and cognitive digital twins of students: 32 REST endpoints, 368 tests and formally verified memory convergence — built in a 10-day sprint.
- Status
- Research project
- Timeline
- 10-day sprint
- Stack
- Python
- NumPy
- PyTorch
- FastAPI
- Redis
- Lean 4
The task
An education platform needed long-term memory of each student: not a gradebook or prompt context, but a model of topic mastery, forgetting and current cognitive state. Existing approaches don't give a persistent neural model of a student, and the memory dynamics had to provably converge. We framed it as research to be taken all the way to a service the platform can integrate.
What we built
- We built a ~23.7k-line Python research platform. Its neuromorphic memory core — 59 modules in 12 subsystems — runs on spiking neural networks; the architecture is derived automatically rather than hand-designed — details in patent prep, closed.
- We created a cognitive digital twin of a student: it tracks mastery and forgetting, estimates cognitive state, predicts performance and picks the right task difficulty.
- We formally verified convergence of the memory core in Lean 4 with Mathlib: 22 theorems and lemmas, zero unproven statements, machine-checked.
- We added orchestration of heterogeneous models — SNN, DNN, CNN, RNN, transformers — with 7 execution strategies and hybrid architectures.
- We packaged it all as a FastAPI microservice: 32 endpoints, health checks, a Docker image, Redis and RabbitMQ integration. Three consumers in the platform's main backend are wired to it.
Outcome
- 10 days
- from first commit to a release with formal verification, measured by commit dates
- 368
- test functions across 37 files, counted from code
- 22
- Lean 4 theorems and lemmas on memory convergence, zero unproven statements, compiler-checked
- 32
- REST endpoints, 12 of them the digital-twin API; counted from router code
More cases
Manufacturing · Building materials
MVP in operationPanel specs from CAD drawings in seconds, not hours
Reads DWG/DXF layouts and builds the Excel spec: 10–30 seconds instead of 2–15 hours by hand. All 784 panels of one real project matched the manual spec line by line.
- 784/784 and 189/189
- panels on one project and wall panels on another matched the manual specs line by line, size groups included; area within 0.001 m²
- 2–15 h → 10–30 s
- to produce a project spec: manual work vs app processing, measured on real projects
Real estate · PropTech marketplace
MVP in operationLand-plot marketplace with a next-step plan: MVP in 2 months
From a mock-up to a working platform: plot → works → contractor → request. Rule-based next-step engine, three dashboards, personal-data compliance. MVP in 2 months.
- 2 months
- from approved spec to pre-release MVP on an HTTPS stand — week 9 against the plan's own 10–13 week estimate
- 7 days
- from spec to the first full-implementation commit: 168 files, 21.5k lines, then two months of hardening to pre-release
Marketplace e-commerce · Pricing
PilotRepricing without manual price control: a contract-guaranteed pilot
Competitor prices tracked per SKU on the marketplace, a price computed inside an agreed corridor, applied only after confirmation. Pilot: 10 SKUs, setup within 14 days.
- 10 SKUs · 2 scenarios
- pilot scope; the SKU cap and both scenarios are enforced in code and verified by contract tests — the cap cannot be exceeded
- up to 14 days
- contractual setup window from client inputs to launch, then a 1-month pilot; the service tracks the dates and closes access when the period ends
Estimate the impact on your own figures
AVA is a process-economics calculator. In a couple of minutes it shows whether a similar task pays off in your case — before any call and with no commitment.
Estimate the impact with AVAHave a similar task?
Describe the process and the data you have. We will tell you what can be measured in money and what cannot — before any work starts.
or email us directly: hello@xteam.pro