Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Build a small but real system whose performance depends on correct data-structure choices — an LRU cache (hash map + doubly linked list, O(1) get/put), an autocomplete (trie), a task scheduler (priority queue), or a dependency resolver (topological sort). Justify each structure by its access pattern, prove the complexity, and benchmark it under load.
Data structures fit the access patterns; the choice is justified, and a wrong choice would be measurably slower.
The target complexity is achieved and proven (e.g. O(1) LRU get/put via map + list); benchmarked under realistic load.
Works correctly including edge cases (eviction, empty, capacity, cycles).
Tested, documented, and benchmarked honestly.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# Build a real system on the right data structures ## Goal Build a small but real system whose performance depends on correct data-structure choices — an LRU cache (hash map + doubly linked list, O(1) get/put), an autocomplete (trie), a task scheduler (priority queue), or a dependency resolver (topological sort). Justify each structure by its access pattern, prove the complexity, and benchmark it under load. ## Acceptance criteria - [ ] Structure choice: Data structures fit the access patterns; the choice is justified, and a wrong choice would be measurably slower. - [ ] Complexity achieved: The target complexity is achieved and proven (e.g. O(1) LRU get/put via map + list); benchmarked under realistic load. - [ ] Correctness: Works correctly including edge cases (eviction, empty, capacity, cycles). - [ ] Engineering: Tested, documented, and benchmarked honestly. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.