Repository navigation
Build the layered Practice Pack config: DLC defaults, pack defaults, Consumer overrides #647
Closed as not planned
Description
Question
How does the DLC build the layered config that Practice Packs must stack decided in its decision 6?
The order is .archon/packs/unic-dlc.config.yaml, then each .archon/packs/<prefix>.config.yaml, then the Consumer's .archon/unic-dlc.config.yaml. Each installer replaces its own defaults file, and no installer writes a default into the Consumer's file. On a re-run, /setup reports every key in the Consumer's file whose value equals the current default, as a candidate to remove, and changes nothing.
Split out of #520 on 2026-10-21. It blocks the first Practice Pack that sets a default value, the need #541 raised.
Open for grilling
- Every prompt that reads the config must apply the order. The quality bar puts a rule inline where it is needed, so the rule is written by hand in each prompt, which is the drift this repository keeps meeting. Decide how the text stays one rule.
- Which Boxes and commands read the config today, and which
/setupsteps change. A Box edit waits for #502, as #542 orders.
Activity
fix(unic-archon-dlc): make the /setup prefix rule and Step 7 agree
docs(unic-archon-dlc): correct ADR-0038 claims on unbuilt work and scope
orioltf commentedon Oct 21, 2026
Open question from the review of #649
ADR-0038 §6, written in #649 for #520, orders the config layers as the DLC's defaults, then each pack's defaults file, then the Consumer's file. It does not order two packs' defaults files against each other. When two packs set the same key to different values and the Consumer's file omits that key, nothing defines the winner. Copilot's review comment found this, and #649 records it as open in the ADR.
This ticket decides it before a second pack sets a default. It should also say where the reader sees which pack won.
docs(unic-archon-dlc): leave the order of two packs' defaults open in…
orioltf commentedon Nov 3, 2026
unic-archon-dlc is frozen. This question carries over to adlc, its successor, as input for adlc's map (internal Jira APD-3). Nothing more happens on it in this repository.