Update VELODY_ROADMAP
This commit is contained in:
parent
96609a7802
commit
efd8630aa0
@ -30,7 +30,7 @@ When milestone scope, sequencing, or status changes, update this file first.
|
||||
| 11.4 | Legacy Owner Claim & Transfer | Completed |
|
||||
| 11.5 | OAuth Identity Providers | Completed |
|
||||
| 11.6 | Device Management & Recovery | Completed |
|
||||
| 11.7 | Authentication Runtime Foundation | Planned |
|
||||
| 11.7 | Authentication Runtime Foundation | Completed |
|
||||
| 12 | Monetization | Planned |
|
||||
| 13 | Pro Features | Planned |
|
||||
|
||||
@ -433,19 +433,33 @@ Add the runtime authentication foundation needed before monetization, without ch
|
||||
|
||||
**Major features**
|
||||
|
||||
- Email/password login runtime foundation.
|
||||
- OAuth callback/runtime flow foundation.
|
||||
- Access token and refresh token model.
|
||||
- Session lifecycle model.
|
||||
- Account-authenticated device linking entry point.
|
||||
- Token rotation and logout groundwork.
|
||||
- Authentication tests for account runtime behavior.
|
||||
* Internal account session management.
|
||||
* JWT access token foundation.
|
||||
* Opaque refresh token foundation with secure rotation.
|
||||
* Authentication runtime orchestration.
|
||||
* Internal account authentication guard.
|
||||
* Current authenticated account context.
|
||||
* Authentication runtime validation and testing.
|
||||
|
||||
**Current status**
|
||||
Planned
|
||||
Current status
|
||||
Completed
|
||||
|
||||
**Completion notes**
|
||||
Not started yet. This milestone is the next planned step before monetization because billing and entitlements need a stable account authentication runtime.
|
||||
Completion notes
|
||||
Completed.
|
||||
|
||||
All milestones 11.7.1 through 11.7.5 are complete.
|
||||
|
||||
Completed coverage:
|
||||
|
||||
* Internal Session Foundation
|
||||
* Access Token Foundation
|
||||
* Refresh Token Foundation
|
||||
* Authentication Runtime Pipeline
|
||||
* Authentication Guards Foundation
|
||||
|
||||
The backend now includes a complete internal account authentication runtime consisting of account sessions, JWT access tokens, opaque refresh tokens with secure rotation, runtime authentication orchestration, account authentication guards, and authenticated account context while preserving the existing device-token authentication system.
|
||||
|
||||
No public login, signup, logout, refresh endpoint, OAuth runtime, or frontend authentication flows have been exposed yet. The runtime foundation is complete and ready for future public authentication APIs.
|
||||
|
||||
## Milestone 12 Monetization
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user