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

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 D3 D4 medium 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. current target confidence rationale A1 A3 medium 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.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 medium scope_vs_intent_and_consumer_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 level confidence basis known_reliability_risks R1 low consumer_quality_signals 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	intent includes excludes assumptions use_cases research_memos 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. 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) external partner/subcontractor portal accounts (data objects only in v1) multi-tenancy automated ingestion from tender platforms, SharePoint, Teams, CRM, ERP, email, or calendars	current_level target_level current_artifacts target_artifacts consumption_modes A1 A3 Django application (`vergabe_teilnahme`, 12 apps) Vite/Tailwind frontend (`static/`) docker-compose.dev.yml and docker-compose.test.yml application (Django + Vite, local dev via docker-compose)	depends_on supports related_to capability.infotech.issue-tracking capability.design.whynot-system	documentation tests consumer_feedback bug_reports incidents SCOPE.md wiki/ProductRequirementsDocument.md wiki/ArchitectureBlueprint.md pyproject.toml vergabe_teilnahme/apps/*/tests.py (pytest-django suite across domain apps) docker-compose.test.yml	recommended_for not_recommended_for known_limitations teams needing structured German tender-participation workflow tracking (manual-entry-first v1) extending or deploying this specific Django application automated tender-platform ingestion (out of scope for v1) external bidder/partner self-service portals (not built) manual data entry only in v1 — no platform integration README.md is still repo-seed boilerplate; use SCOPE.md and wiki/ for orientation	date dimension from to rationale author 2026-07-07 discovery D1 D3 SCOPE.md filled with full in/out scope and current-state documentation (REUSE-WP-0017-T05 entry-2 review). grok date dimension from to rationale author 2026-07-07 completeness C0 C1 Consumer scope expectations now documented in SCOPE.md and wiki PRD. 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

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