19 lines
1 KiB
Markdown
19 lines
1 KiB
Markdown
|
# Intent
|
||
|
|
|
||
|
|
Vergabe Teilnahme is the primary customer service and UI product for the first
|
||
|
|
HelixForge factory delivery lane, as selected by Bernd Worsch on 2026-09-08.
|
||
|
|
It helps a company's team manage tender participation: deadlines, lots,
|
||
|
|
requirements, decisions, evidence, submission and retrospective learning.
|
||
|
|
|
||
|
|
The existing Django product remains the implementation home. The first customer
|
||
|
|
offering should preserve its single-company boundary, with an isolated deployment
|
||
|
|
per admitted company until a separately designed tenancy model is accepted.
|
||
|
|
Customer availability follows verified access, persistence, restore, release and
|
||
|
|
support arrangements; this intent does not claim those gates are complete.
|
||
|
|
|
||
|
|
The product requirements and domain workflows remain in
|
||
|
|
[wiki/ProductRequirementsDocument.md](wiki/ProductRequirementsDocument.md).
|
||
|
|
Factory integration is coordinated by `prj-helixforge-factory/HFACT-WP-0001`.
|
||
|
|
Reuse-surface supplies internal capability discovery before new implementation;
|
||
|
|
customer users interact with the tender UI.
|