Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-07 15:46:55 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

To-repo-arkitekturen dokumenteret: BCQuality (intake) + QualityHub (produkt)

Browse source 
Michaels arkitektur: den offentlige fork bestaar - uden custom-laget -
som intake fra og bidragsvej til microsoft/BCQuality; QualityHub er
produktet og opdateres fra forken via rent git-merge (delt ancestry).
Ny vedligeholdsbevaegelse: Opdater QualityHub fra BCQuality =
fetch -> merge-PR -> CI validerer det mergede korpus -> merge ->
promote. Aldrig upstream direkte i stable.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Michael Dieringer 2026-07-03 18:04:22 +02:00
parent 68a3f6dffa
commit 12fe324500
1 changed files with 18 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

19
CONSUMPTION.md
View file

@ -5,7 +5,24 @@ Microsoft/BCQuality architecture: an orchestrator invokes `/skills/entry.md`,
Entry dispatches layer action skills, each skill runs Source → Relevance → Entry dispatches layer action skills, each skill runs Source → Relevance →
Worklist → Action and emits DO-shaped findings. That document is the Worklist → Action and emits DO-shaped findings. That document is the
*architecture*. This document is the *actual state* — which consumption paths *architecture*. This document is the *actual state* — which consumption paths
are live in the CURABIS fork, and which are dormant upstream inheritance. are live, and which are dormant upstream inheritance.
## The two-repo architecture
- **`Curabis/BCQuality`** (PUBLIC, fork of microsoft/BCQuality): the intake.
Carries only upstream content — `microsoft/`, `community/`, `skills/`,
`tools/`. Synced from Microsoft via GitHub's *Sync fork*. It is also the
contribution path: community-layer improvements go upstream through it.
It NEVER contains the custom layer.
- **`Curabis/QualityHub`** (PRIVATE, this repo): the product. Custom layer,
agents, setup machinery, release channel, governance — everything below.
Because QualityHub shares git ancestry with microsoft/BCQuality, upstream
updates arrive as a clean merge.
**"Opdater QualityHub fra BCQuality":** fetch the `bcquality` remote → merge
`bcquality/main` on a branch → PR (CI validates the merged corpus, catching
upstream schema drift at the gate) → Michael merges → promote. Never merge
upstream directly into `stable`.
## Active: the CURABIS Standard session model ## Active: the CURABIS Standard session model