# Tenders

<!-- wb-memory.v1
{
  "schemaVersion": "wb-memory.v1",
  "id": "area.tenders",
  "kind": "area",
  "title": "Tenders",
  "lifecycle": "active",
  "authority": "canonical",
  "links": [
    {
      "type": "contains",
      "targetId": "screen.tender-list",
      "sourceRefIds": ["S1"]
    },
    {
      "type": "contains",
      "targetId": "screen.tender-carrier-express-auction",
      "sourceRefIds": ["S2"]
    },
    {
      "type": "contains",
      "targetId": "flow.tender-create",
      "sourceRefIds": ["S3"]
    }
  ],
  "sourceRefs": [
    {
      "id": "S1",
      "kind": "spec",
      "authority": "canonical",
      "path": "specs/ux/screens/tender-list.md",
      "status": "verified",
      "anchor": "readiness"
    },
    {
      "id": "S2",
      "kind": "spec",
      "authority": "canonical",
      "path": "specs/ux/screens/tender-carrier-express-auction.md",
      "status": "verified",
      "anchor": "readiness"
    },
    {
      "id": "S3",
      "kind": "spec",
      "authority": "canonical",
      "path": "specs/ux/flows/tender-create.md",
      "status": "verified",
      "anchor": "readiness"
    },
    {
      "id": "S4",
      "kind": "spec",
      "authority": "canonical",
      "path": "docs/researches/tenders-cjm.md",
      "status": "verified",
      "anchor": "problem"
    }
  ]
}
-->

## Readiness

| Dimension | Status and evidence |
| --- | --- |
| Specification | Tender list and creation journey are proposals; the carrier card records an earlier Figma design. The CJM note is a documentation scaffold, not completed user research. [S1] [S2] [S3] [S4] |
| Figma | Earlier evidence exists for the carrier card only. List/create have no cited Figma verification; no Figma state was freshly checked in D-026. [S1] [S2] [S3] |
| Local prototype | No tender screen or creation flow is implemented in the current local router. [S1] [S3] |
| Verification | Readiness was checked against tracked specs, the CJM scaffold, and the local router. No implemented tender scenario, usability result, or live business behavior is verified. [S1] [S2] [S3] [S4] |

## Value

The proposed area groups tender discovery and creation scenarios with the
existing carrier-card design record. Its intended value is to help the design
team explore how a user finds an opportunity and understands a tariff or bid
state. No completed research or measured coordination benefit is established by
`docs/researches/tenders-cjm.md`; it explicitly says canonical product text still
needs authoring. [S1] [S2] [S3] [S4]

## Users and JTBD

- Proposed list/create actor: a user exploring tenders and a way to start a new
  tender. The role and its permissions remain open. [S1] [S3]
- Carrier-card design actor: a carrier comparing the official tariff and the
  bid/counteroffer examples in the documented Figma states. [S2]

## Boundaries

The current documentation covers a proposed tender list, a proposed creation
journey, and a Figma-only carrier express-auction card. List filters, creation
fields, real data, authorization, and persistence are not established by these
proposals. Settlement, route execution, and contract execution are not modeled
here. [S1] [S2] [S3]

## Glossary

- `Tender list`: the proposed discovery screen; no local route exists yet. [S1]
- `Creation journey`: the proposed path from that list to a creation state. [S3]
- `Official tariff` and `counteroffer`: terms in the carrier-card design record;
  their documented visual rules are not a production API contract. [S2]

## Screens and Flows

- `screen.tender-list` — proposed browse/create entry screen. [S1]
- `screen.tender-carrier-express-auction` — documented Figma carrier card with
  tariff and counteroffer states. [S2]
- `flow.tender-create` — proposed journey starting from the list. [S3]

All three are linked by the marker's `contains` relationships. Those links
record document scope, not implementation or validation status.

## Current Rules and Decisions

- The list and creation journey remain proposals rather than current product
  behavior. [S1] [S3]
- Carrier-card requirements and prior visual evidence stay scoped to that
  screen; they do not define a generic tender lifecycle. [S2]
- The CJM scaffold does not verify user needs, roles, permissions, or business
  outcomes. [S4]

## Open Questions

- Which roles and user needs should the list/create prototype model?
- Which filters, rows, creation fields, and completion states should be designed?
- Should the proposed creation state use a modal, separate screen, or side panel?

## 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.