← Back to parent Epic
MAZENG-FT-42 · Open a Prism work item as a Maze project
Why it matters
A Prism user needs to enter Maze with verified identity and work-item context instead of recreating the project manually.
Expected outcome
Trusted context transfer creates the correct Maze project and takes the user to their work without leaving partial records.
In scope
- Validate the Prism bearer token against the configured authority.
- Reuse a verified-email Maze user or create a Prism-bound user.
- Create the project atomically from validated Prism context and navigate to the canvas or project list.
- Delivery status
IN_BACKLOG- Owner
- RootAtSkic
- Solution approval
- PENDING
Acceptance
Acceptance outcomes
- 01
Maze validates the Prism bearer token with the configured Prism authority.
- 02
An existing Maze user is reused by verified email; otherwise a Prism-bound Maze user is created.
- 03
Prism context creates a project carrying hyperscaler, target repository, tags, task ID, base directory, and name.
- 04
The user lands on the new project canvas or their project list.
- 05
Invalid or incomplete context fails without creating a partial project.
Dependencies and risks
Dependencies
None recorded.
Risks
- The flow depends on a trusted Prism authentication endpoint and agreed context schema.
- Legacy behavior passes JSON through a URL query parameter.
- Legacy authentication disables two-factor authentication in its response and auto-creates users by email.
Authoritative Architecture tasks
No authoritative Architecture tasks are linked.