# Tender list

<!-- wb-memory.v1
{
  "schemaVersion": "wb-memory.v1",
  "id": "screen.tender-list",
  "kind": "screen",
  "title": "Tender list",
  "lifecycle": "active",
  "authority": "canonical",
  "areaId": "area.tenders",
  "routes": [],
  "links": [
    {
      "type": "uses-component",
      "targetId": "component.table",
      "sourceRefIds": ["S3"]
    },
    {
      "type": "related-to",
      "targetId": "flow.tender-create",
      "sourceRefIds": ["S2"]
    }
  ],
  "sourceRefs": [
    {
      "id": "S1",
      "kind": "spec",
      "authority": "canonical",
      "path": "specs/ux/areas/tenders.md",
      "status": "verified",
      "anchor": "value"
    },
    {
      "id": "S2",
      "kind": "spec",
      "authority": "canonical",
      "path": "specs/ux/flows/tender-create.md",
      "status": "verified",
      "anchor": "goal"
    },
    {
      "id": "S3",
      "kind": "spec",
      "authority": "canonical",
      "path": "specs/ux/components/organisms/table.md",
      "status": "verified",
      "anchor": "purpose-and-use"
    },
    {
      "id": "S4",
      "kind": "code",
      "authority": "implementation",
      "path": "src/app/app.routes.ts",
      "status": "verified"
    },
    {
      "id": "S5",
      "kind": "spec",
      "authority": "canonical",
      "path": "docs/researches/tenders-cjm.md",
      "status": "verified",
      "anchor": "problem"
    }
  ]
}
-->

## Readiness

| Dimension | Status and evidence |
| --- | --- |
| Specification | Proposed screen outline. The CJM source is an initial documentation scaffold; fields, roles, and interactions are not validated requirements. [S1] [S5] |
| Figma | No exact Figma screen or visual verification is cited for this list. |
| Local prototype | Not implemented. `/tenders` is only a proposed route; the current router defines the repair-request screen at `/`. [S4] |
| Verification | Local router and source documents inspected in D-026. No tender-list runtime tests or browser verification are available for this proposed screen. [S4] [S5] |

## Purpose

Proposed screen for exploring tender discovery and an entry to tender creation.
This is design intent, not a currently usable list or a claim of validated user
value. [S1] [S5]

## Source and Route

- Proposed route: `/tenders`; absent from `src/app/app.routes.ts`, so the marker
  has `routes: []`. [S4]
- Proposed entry: area navigation, with the exact control still undecided.
- Proposed exit: a create action connected to `flow.tender-create`. [S2]
- Context: `docs/researches/tenders-cjm.md` and `specs/ux/areas/tenders.md`.
  The first is a scaffold, not research findings. [S1] [S5]
- Local feature source and exact Figma visual evidence: absent.

## Primary Scenario

Proposed sequence for a future prototype; no step is currently implemented:

1. A user would open the tender list.
2. The list would show example tender rows.
3. A primary action would start the proposed creation journey.
4. The destination and transition would be chosen with `flow.tender-create`.
   [S2]

## Alternate Scenarios

- Proposed: show an empty-list example; whether it offers creation remains open.
- Open: roles, access restrictions, and availability of the create action.

## States, Errors, and Edge Cases

Populated and empty lists are proposed visual states. Loading, network errors,
no-access states, disabled actions, and malformed rows need explicit scenario
decisions before they become prototype requirements. No such behavior is
implemented or verified.

## Data and Integration Boundary

No tender fixture, runtime data source, API, persistence, or navigation contract
is defined. Future local UI work would use the team's own generated components
and explicitly scoped examples. This outline does not describe developers'
production code or establish readiness for transfer to it. [S4]

## Components and Accessibility

- Proposed reuse: the owned `component.table` supports record-list composition;
  its availability does not mean this screen has been assembled. [S3]
- Proposed accessibility requirements: visible action labels, keyboard access,
  and logical focus movement when entering or leaving the creation state.
- Row-selection behavior and exact focus targets remain design questions.

## Related Flows

- `flow.tender-create` proposes a creation journey from this screen. [S2]

## Open Questions

- User role, row fields, sorting, and filter set.
- Exact creation destination, entry action, and return behavior.
- Which alternate and error states should be included in the local prototype?

## Documentation Review

Readiness review: D-026 ([GitLab task](https://gitlab.com/polozovdaniel/logistics-2/-/work_items/28));
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.