Draft capability entry (reuse-surface REUSE-WP-0017-T04, cohort 3)

Honest first-pass maturity vector grounded in README/docs/tests present
in this repo; no invented evidence. Flagged for human review before
publish. See reuse-surface history/2026-07-06-coverage-classification.md.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
2026-07-06 19:50:54 +02:00
parent a3cec3f221
commit d20d21b21a
2 changed files with 138 additions and 2 deletions

View File

@@ -0,0 +1,121 @@
---
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: D1
target: D3
confidence: low
rationale: 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:
current: A1
target: A3
confidence: medium
rationale: 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.
external_evidence:
completeness:
level: C0
confidence: low
basis: scope_vs_intent_and_consumer_expectations
satisfied_expectations: []
broken_expectations: []
out_of_scope_expectations: []
reliability:
level: R0
confidence: low
basis: consumer_quality_signals
known_reliability_risks:
- 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
discovery:
intent: Manage German public-procurement (Vergabe) tender participation workflows as a Django application,
per its own pyproject description (Ausschreibungs- und Teilnahme-Management-System).
includes:
- tender/Ausschreibung participation management (Django app + Vite frontend)
excludes: []
assumptions: []
use_cases: []
research_memos: []
availability:
current_level: A1
target_level: A3
current_artifacts:
- Django application (`vergabe_teilnahme`)
- Vite/Tailwind frontend
target_artifacts: []
consumption_modes:
- application (Django + Vite, local dev via docker-compose)
relations:
depends_on: []
supports: []
related_to: []
evidence:
documentation:
- pyproject.toml description
tests:
- conftest.py
- docker-compose.test.yml
consumer_feedback: []
bug_reports: []
incidents: []
consumer_guidance:
recommended_for:
- understanding or extending this specific German procurement participation tool
not_recommended_for:
- general reuse — SCOPE.md is unfilled, so consumer expectations are undocumented; treat as low-discovery
until SCOPE.md is written
known_limitations:
- 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
promotion_history: []
---
# 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
- [x] ID follows `capability.<domain>.<name>` pattern
- [x] Maturity enums match `specs/CapabilityMaturityStandard.md`
- [x] `external_evidence` is populated separately from `maturity`
- [ ] Relations reference valid capability IDs (none yet)
- [x] Index entry added in `registry/indexes/capabilities.yaml`

View File

@@ -1,4 +1,19 @@
version: 1
updated: '2026-06-16'
updated: '2026-07-06'
domain: helix_forge
capabilities: []
capabilities:
- 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.
vector: D1 / A1 / C0 / R0
domain: communication
status: draft
owner: vergabe-teilnahme
path: registry/capabilities/capability.procurement.vergabe-teilnahme.md
tags:
- procurement
- django
- vergabe
consumption_modes:
- application (Django + Vite, local dev via docker-compose)