coulomb/vergabe-teilnahme
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Require invited login and private downloads for the company pilot

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
This commit is contained in:
tegwick 2026-09-11 16:35:13 +02:00
parent 56bf193193
commit b7d7828f30
27 changed files with 584 additions and 111 deletions
Download patch file Download diff file Expand all files Collapse all files

15
SCOPE.md
View file

@ -41,7 +41,7 @@ It operates on three levels, per `wiki/ProductRequirementsDocument.md`:
Primary customer service/UI repository for the HelixForge factory, selected by
the user. Initial delivery preserves a single-company boundary; customer release
requires explicit deployment, access, persistence, restore and support acceptance
in VERGABE-WP-0018. The original internal collaboration workflows remain valid.
in VERGABE-WP-0019 (invited pilot) and VERGABE-WP-0018 (factory delivery). The original internal collaboration workflows remain valid.
## In Scope
@ -60,7 +60,7 @@ in VERGABE-WP-0018. The original internal collaboration workflows remain valid.
- External user accounts for partners/subcontractors/service providers (data
objects only in this build stage, no system access of their own)
- Multi-tenancy
- Shared-application multi-tenancy; invited companies use isolated deployments
- Automated ingestion from tender platforms, SharePoint, Teams, CRM, ERP,
email, or calendars (deliberately manual-entry-first for v1)
- Certification or legal validity of submissions — the system tracks
@ -95,7 +95,7 @@ in VERGABE-WP-0018. The original internal collaboration workflows remain valid.
feedback, lose, marktbegleiter, nachbetrachtung, partner, preise); 17
workplans (WP-0001–WP-0017) implemented in sequence from project
scaffold through whynot-design token adoption
- Stability: evolving — manual-entry-first v1; no CI workflow configured yet
- Stability: evolving — manual-entry-first v1; Forgejo gates images with application/container acceptance
(`.gitea/`/`.forgejo/` absent)
- Usage: internal collaboration tool, not yet published for external use
@ -159,3 +159,12 @@ Product and architecture documentation (`wiki/`) is in German; this SCOPE.md
is in English per the reuse-surface registry's Markdown-first, agent-facing
convention. Refer to `wiki/ProductRequirementsDocument.md` for the
authoritative German-language product definition.
## Invited-pilot milestone — 2026-09-11
One company, several manually onboarded users; pricing follows later by user
decision. Django login and protected downloads are source-tested. Native release,
data recovery, user acceptance and support remain in VERGABE-WP-0019 and
RAPPS-WP-0014. Automated source/container acceptance already exists in Forgejo;
older current-state statements about missing CI are historical.