Readiness
| Dimension | Status and evidence |
|---|---|
| Specification | Proposed journey outline from the proposed tender list; roles, fields, and completion remain undecided. [S1] |
| Figma | No Figma creation state or transition is cited or freshly verified. |
| Local prototype | Not implemented. The router has no tender list or creation destination. [S2] |
| Verification | Tracked list spec and router inspected in D-026. No executable creation journey, submission, return path, or persistence is verified. [S1] [S2] |
Goal
Proposed design goal: let a user start creating a tender from a tender-list context. The destination and visible completion require design decisions before this becomes a prototype scenario. [S1]
Actor, Trigger, and Preconditions
- Proposed actor: a user of the tender list; exact role is an open question.
- Proposed trigger: a create action on
screen.tender-list. [S1] - Preconditions: not established. Authentication and creation permissions must not be inferred from this outline.
Screens and Routes
screen.tender-list— proposed/tenders; no current local route. [S1] [S2]
A creation destination has not been specified, so no additional screen ID or route is asserted.
Primary CJM
Proposed sequence only:
- A user would open the proposed tender list.
- The user would choose a create action.
- The prototype would show a creation state; modal, page, and panel are still alternatives.
- A later design decision would define the fields and a visible completion.
These steps do not imply working submission or production navigation. [S1] [S2]
Branches and Failure Handling
Cancellation, validation errors, draft handling, retries, and access restrictions are open design questions. No draft-save operation, permission rule, or error recovery is established by the current sources.
Cross-Screen Rules
The list is the proposed starting context. Return destination, focus restoration, retained input, refresh behavior, and deep links are undecided; no persistence or session rule is claimed. [S1] [S2]
Completion Criteria
Not defined yet. A proposed prototype could end in a visible completion state, but whether it adds an example row, retains a draft, or returns to the list needs an explicit design decision. No created tender record is currently produced.
Maintenance and Open Questions
Update this flow with screen.tender-list and area.tenders when a design
choice is made. Keep proposals separate from verified local interactions.
- Which role and creation fields should the prototype illustrate?
- What visible state should count as completion?
- What should cancellation preserve, and where should focus return?
Documentation Review
Readiness review: D-026 (GitLab task);
verified member danil-lebedev / GitLab 8269564; agent codex;
session 01a0725e-9ce7-7070-bd66-3b8a92ab9006. This review inspected tracked
local sources; it did not re-verify Figma or establish production behavior.