vergabe-teilnahme/registry/capabilities/capability.procurement.vergabe-teilnahme.md

---
id: capability.procurement.vergabe-teilnahme
name: Vergabe Teilnahme (Public Procurement Participation) Application
summary: Django application (with a Vite/Tailwind frontend) for managing German public-procurement (Vergabe)
  tender participation — Ausschreibungs- und Teilnahme-Management-System.
owner: vergabe-teilnahme
status: draft
domain: communication
tags:
- procurement
- django
- vergabe
maturity:
  discovery:
    current: D3
    target: D4
    confidence: medium
    rationale: SCOPE.md filled 2026-07-07 with in/out scope, current state, terminology, and orientation
      pointers; supported by wiki/ProductRequirementsDocument.md (German product definition) and
      wiki/ArchitectureBlueprint.md. README.md remains a stale repo-seed leftover — SCOPE and wiki
      are authoritative for discovery.
  availability:
    current: A1
    target: A3
    confidence: medium
    rationale: Substantial Django application (12 domain apps, WP-0001–WP-0017 implemented) with
      Vite/Tailwind frontend and docker-compose dev/test; SCOPE.md describes internal collaboration
      use only — no hosted production deployment confirmed in this review.
external_evidence:
  completeness:
    level: C1
    confidence: medium
    basis: scope_vs_intent_and_consumer_expectations
    satisfied_expectations:
    - in-scope/out-of-scope boundaries documented in SCOPE.md
    - 8-phase tender participation model described with operational/management/strategic levels
    - manual-entry-first v1 constraint and external-portal exclusion explicit
    broken_expectations: []
    out_of_scope_expectations: []
  reliability:
    level: R1
    confidence: low
    basis: consumer_quality_signals
    known_reliability_risks:
    - no CI workflow configured yet (per SCOPE.md current state)
    - no production consumer telemetry (REUSE-WP-0019)
    - README.md still stale repo-seed text — fix separately
discovery:
  intent: Guide a team through the full lifecycle of bidding on public or private tenders (Ausschreibungen)
    — from research and participate/no-bid decisions through submission and post-award retrospective.
  includes:
  - tender (Ausschreibung) and lot (Los) tracking across 8 navigable phases
  - requirements analysis and bidder-question (Bieterfragen) handling
  - tasks (Aufgaben), documents (Dokumente), pricing (Preise), submission/retrospective (Abgabe/Nachbetrachtung)
  - partner/reference library (Bibliothek) and competitor observation (Marktbegleiter)
  - issue-core task facade integration (not a UI replacement)
  excludes:
  - external partner/subcontractor portal accounts (data objects only in v1)
  - multi-tenancy
  - automated ingestion from tender platforms, SharePoint, Teams, CRM, ERP, email, or calendars
  assumptions: []
  use_cases: []
  research_memos: []
availability:
  current_level: A1
  target_level: A3
  current_artifacts:
  - Django application (`vergabe_teilnahme`, 12 apps)
  - Vite/Tailwind frontend (`static/`)
  - docker-compose.dev.yml and docker-compose.test.yml
  target_artifacts: []
  consumption_modes:
  - application (Django + Vite, local dev via docker-compose)
relations:
  depends_on:
  - capability.infotech.issue-tracking
  supports: []
  related_to:
  - capability.design.whynot-system
evidence:
  documentation:
  - SCOPE.md
  - wiki/ProductRequirementsDocument.md
  - wiki/ArchitectureBlueprint.md
  - pyproject.toml
  tests:
  - vergabe_teilnahme/apps/*/tests.py (pytest-django suite across domain apps)
  - docker-compose.test.yml
  consumer_feedback: []
  bug_reports: []
  incidents: []
consumer_guidance:
  recommended_for:
  - teams needing structured German tender-participation workflow tracking (manual-entry-first v1)
  - extending or deploying this specific Django application
  not_recommended_for:
  - automated tender-platform ingestion (out of scope for v1)
  - external bidder/partner self-service portals (not built)
  known_limitations:
  - manual data entry only in v1 — no platform integration
  - README.md is still repo-seed boilerplate; use SCOPE.md and wiki/ for orientation
promotion_history:
- date: "2026-07-07"
  dimension: discovery
  from: D1
  to: D3
  rationale: SCOPE.md filled with full in/out scope and current-state documentation (REUSE-WP-0017-T05 entry-2 review).
  author: grok
- date: "2026-07-07"
  dimension: completeness
  from: C0
  to: C1
  rationale: Consumer scope expectations now documented in SCOPE.md and wiki PRD.
  author: grok
---

# Vergabe Teilnahme (Public Procurement Participation) Application

## Overview

`vergabe-teilnahme` is a Django + Vite/Tailwind application for managing German public-procurement (Vergabe) tender participation end-to-end. SCOPE.md (filled 2026-07-07) documents the 8-phase, manual-entry-first v1 model across 12 Django apps.

## Assessment notes

### Discovery

SCOPE.md now provides authoritative in/out scope, current state, terminology, and pointers to the German-language wiki PRD and architecture blueprint. Discovery promoted from D1 to D3; README cleanup remains a separate hygiene item.

### Availability

Substantial implemented application (WP-0001–WP-0017) with local docker-compose paths. Held at A1 until a hosted deployment path is confirmed (railiance-apps is named as deployment target in SCOPE.md).

### Completeness

Scope-vs-intent expectations are now documented (C1). Feature completeness against the full PRD is not independently verified in this review.

### Reliability

Pytest-django suite exists across domain apps (structural R1). No CI workflow or production telemetry yet.

## Promotion checklist

- [x] ID follows `capability.<domain>.<name>` pattern
- [x] Maturity enums match `specs/CapabilityMaturityStandard.md`
- [x] `external_evidence` is populated separately from `maturity`
- [x] Relations reference valid capability IDs
- [x] Index entry added in `registry/indexes/capabilities.yaml`