Repository navigation
docs: plan repository separation for a slim standalone Accelerator - #259
Merged
Merged
Conversation
lweberru
marked this pull request as ready for review
November 16, 2026 10:33
lweberru
requested review from
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
November 16, 2026 10:33
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Architecture concept only. Record the user's primary motivation: make the native Accelerator smaller and clearer for consumers who do not use the Configurator. No repository extraction or runtime/IaC/workflow change is implemented.
The full English/German concept defines a native-first ownership boundary, verified versioned Accelerator bundles consumed by the Configurator, a proposed four/seven workflow split, independent releases and updates, current path/history/trust couplings, migration and single-writer cutover, preliminary effort and measurable acceptance. It explicitly separates a smaller current tree/distribution from full historical Git storage and preserves existing source pins, releases and customer state. README and architecture references link the proposal.
Effort remains a preliminary 10–20 engineering person-day assessment for a production-safe split; installer/auth/private-runner implementation and disruptive history rewriting are separate scope.
Validation: both concept/local index link sets checked; ten matching section structures; both Mermaid diagrams parsed/rendered locally (5 nodes/4 edges each), German rendering inspected; workflow-map freshness and whitespace checks passed. No cloud flavor test, model-service calls, deployment, repository creation or file extraction.
German concept · English concept.