← Back to parent Epic
MAZENG-FT-12 · Maintain project identity and context
Why it matters
A project's meaning changes over time and needs durable context beyond its cloud resources.
Expected outcome
Keeps the workspace recognizable and understandable to returning contributors.
In scope
- Update project name and description.
- Update project notes and tags.
- Display project owner, relevant dates, description, notes, tags, and an existing project image.
- Allow editing only to users with the required project authority.
- Delivery status
IN_BACKLOG- Owner
- RootAtSkic (product lead)
- Solution approval
- PENDING
Acceptance
Acceptance outcomes
- 01
Authorized contributors can save supported identity and context fields and see them after reload.
- 02
Viewers can read project context but cannot edit it.
- 03
Rejected or unauthorized updates leave the prior values intact.
- 04
An existing project image is displayed when available without implying image-edit support.
Dependencies and risks
Dependencies
None recorded.
Risks
- Project-image editing is not convincingly wired into the legacy project user interface despite image services; image management remains an open scope question.
- Edit authority and field-level validation must be defined consistently for names, notes, descriptions, and tags.
Authoritative Architecture tasks
No authoritative Architecture tasks are linked.