diff --git a/SCOPE.md b/SCOPE.md index 4a2db4e..d0efe2e 100644 --- a/SCOPE.md +++ b/SCOPE.md @@ -141,8 +141,8 @@ It operates on three levels, per `wiki/ProductRequirementsDocument.md`: ## Provided Capabilities Registered in `registry/capabilities/capability.procurement.vergabe-teilnahme.md` -(reuse-surface federation, D1/A1/C0/R0 as of the initial coverage sweep — -low discovery confidence pending this SCOPE.md's first real fill-in). +(reuse-surface federation; vector **D3/A1/C1/R1** after SCOPE.md fill-in and +REUSE-WP-0017-T05 entry-2 review, 2026-07-07). --- diff --git a/registry/capabilities/capability.procurement.vergabe-teilnahme.md b/registry/capabilities/capability.procurement.vergabe-teilnahme.md index 69257c7..c2ae717 100644 --- a/registry/capabilities/capability.procurement.vergabe-teilnahme.md +++ b/registry/capabilities/capability.procurement.vergabe-teilnahme.md @@ -12,41 +12,52 @@ tags: - 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. + 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: 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. + 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: C0 - confidence: low + level: C1 + confidence: medium basis: scope_vs_intent_and_consumer_expectations - satisfied_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: R0 + level: R1 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 + - 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: Manage German public-procurement (Vergabe) tender participation workflows as a Django application, - per its own pyproject description (Ausschreibungs- und Teilnahme-Management-System). + 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 participation management (Django app + Vite frontend) - excludes: [] + - 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: [] @@ -54,68 +65,83 @@ availability: current_level: A1 target_level: A3 current_artifacts: - - Django application (`vergabe_teilnahme`) - - Vite/Tailwind frontend + - 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: [] + depends_on: + - capability.infotech.issue-tracking supports: [] - related_to: [] + related_to: + - capability.design.whynot-system evidence: documentation: - - pyproject.toml description + - SCOPE.md + - wiki/ProductRequirementsDocument.md + - wiki/ArchitectureBlueprint.md + - pyproject.toml tests: - - conftest.py + - vergabe_teilnahme/apps/*/tests.py (pytest-django suite across domain apps) - docker-compose.test.yml consumer_feedback: [] bug_reports: [] incidents: [] consumer_guidance: recommended_for: - - understanding or extending this specific German procurement participation tool + - teams needing structured German tender-participation workflow tracking (manual-entry-first v1) + - extending or deploying this specific Django application not_recommended_for: - - general reuse — SCOPE.md is unfilled, so consumer expectations are undocumented; treat as low-discovery - until SCOPE.md is written + - automated tender-platform ingestion (out of scope for v1) + - external bidder/partner self-service portals (not built) 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: [] + - 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 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. +`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 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. +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 -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. +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 -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. +Scope-vs-intent expectations are now documented (C1). Feature completeness against the full PRD is not independently verified in this review. ### Reliability -No production consumer telemetry exists yet; reliability level is -intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence. +Pytest-django suite exists across domain apps (structural R1). No CI workflow or production telemetry yet. ## Promotion checklist - [x] ID follows `capability..` 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` +- [x] Relations reference valid capability IDs +- [x] Index entry added in `registry/indexes/capabilities.yaml` \ No newline at end of file diff --git a/registry/indexes/capabilities.yaml b/registry/indexes/capabilities.yaml index e1d5292..1981d4f 100644 --- a/registry/indexes/capabilities.yaml +++ b/registry/indexes/capabilities.yaml @@ -1,12 +1,12 @@ version: 1 -updated: '2026-07-06' +updated: '2026-07-07' domain: helix_forge 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 + vector: D3 / A1 / C1 / R1 domain: communication status: draft owner: vergabe-teilnahme