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

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.procurement.vergabe-teilnahme	Vergabe Teilnahme (Public Procurement Participation) Application	Django application (with a Vite/Tailwind frontend) for managing German public-procurement (Vergabe) tender participation — Ausschreibungs- und Teilnahme-Management-System.	vergabe-teilnahme	draft	communication	procurement django vergabe	discovery availability current target confidence rationale D1 D3 low SCOPE.md is an unfilled template (placeholders only) and README.md is a stale repo-seed leftover; discovery rests entirely on direct inspection of the codebase (pyproject description, manage.py, vergabe_teilnahme Django app, docker-compose.test.yml with a dedicated Postgres test database) rather than on written scope documentation. current target confidence rationale A1 A3 medium Full Django application (413+ files) with manage.py, a vergabe_teilnahme package, and a Vite/Tailwind frontend; docker-compose.dev.yml and docker-compose.test.yml exist but no hosted deployment confirmed in this sweep.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C0 low scope_vs_intent_and_consumer_expectations level confidence basis known_reliability_risks R0 low consumer_quality_signals SCOPE.md is an unfilled template — this repo's own scope documentation does not yet exist no independent verification of test suite health in this sweep	intent includes excludes assumptions use_cases research_memos Manage German public-procurement (Vergabe) tender participation workflows as a Django application, per its own pyproject description (Ausschreibungs- und Teilnahme-Management-System). tender/Ausschreibung participation management (Django app + Vite frontend)	current_level target_level current_artifacts target_artifacts consumption_modes A1 A3 Django application (`vergabe_teilnahme`) Vite/Tailwind frontend application (Django + Vite, local dev via docker-compose)	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents pyproject.toml description conftest.py docker-compose.test.yml	recommended_for not_recommended_for known_limitations understanding or extending this specific German procurement participation tool general reuse — SCOPE.md is unfilled, so consumer expectations are undocumented; treat as low-discovery until SCOPE.md is written SCOPE.md template is unfilled; this entry's discovery evidence comes from direct code inspection, not authored scope documentation — filling in SCOPE.md should be the first step before promoting this entry further

Vergabe Teilnahme (Public Procurement Participation) Application

Overview

vergabe-teilnahme is a Django application (with a Vite/Tailwind frontend) for managing German public-procurement (Vergabe) tender participation. Its own SCOPE.md is an unfilled template, so this entry's discovery level is honestly low (D1) — filling in SCOPE.md is the natural next step before this capability can be promoted further.

Assessment notes

Discovery

SCOPE.md is an unfilled template (placeholders only) and README.md is a stale repo-seed leftover; discovery rests entirely on direct inspection of the codebase (pyproject description, manage.py, vergabe_teilnahme Django app, docker-compose.test.yml with a dedicated Postgres test database) rather than on written scope documentation.

Availability

Full Django application (413+ files) with manage.py, a vergabe_teilnahme package, and a Vite/Tailwind frontend; docker-compose.dev.yml and docker-compose.test.yml exist but no hosted deployment confirmed in this sweep.

Completeness

First-pass honest assessment from the REUSE-WP-0017 coverage campaign (reuse-surface). No external consumer feedback exists yet; levels reflect scope-vs-intent documentation quality, not internal code quality.

Reliability

No production consumer telemetry exists yet; reliability level is intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.

Promotion checklist

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs (none yet)
• Index entry added in registry/indexes/capabilities.yaml