unic / unic/unic-agents-plugins
bug(unic-archon-dlc): the explore Box asks for CONTEXT-MAP.md on 'if a monorepo', but the trigger is bounded contexts
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 16h 43m
- Merged PRs (30d)
- 19
Description
Found on WI 42995 (2026-08-28) and verified
independently. Upstream in this repository, so it reaches every DLC consumer.
The defect
apps/claude-code/unic-archon-dlc/.archon/workflows/unic-dlc-explore.yaml:178 reads:
- Read CONTEXT.md and (if a monorepo) CONTEXT-MAP.md for the domain model and layering.
"Monorepo" is the wrong condition. /domain-modeling's own CONTEXT-FORMAT.md § Single vs
multi-context repos triggers a CONTEXT-MAP.md on multiple bounded contexts, not on multiple
packages, and it names the failure mode explicitly: an empty CONTEXT.md sitting in five packages that
have nothing to say yet.
A monorepo with one domain therefore wants a single root CONTEXT.md and no map. DXP-DesignSystem is
exactly that, and its .archon/unic-dlc.config.yaml:29 already carries the right answer as
repo_layout: single-context — which the Box does not read for this decision.
Why it matters rather than being cosmetic
The Box sends an agent looking for a file that should not exist, on a condition the repository can
answer wrongly by construction: every consumer of this plugin so far is a monorepo. An agent that
believes a CONTEXT-MAP.md is expected either reports it missing or creates one, and creating one is the
documented failure mode.
Acceptance criteria
- The
exploreBox conditions theCONTEXT-MAP.mdread on bounded contexts, not on a monorepo —
or readsrepo_layoutfrom.archon/unic-dlc.config.yaml, which already carries the distinction. - No Box or command instructs an agent to create a
CONTEXT-MAP.md. The/domain-modelingMethod
creates domain files, and it creates them lazily when a term needs resolving. - Every other Box and command is checked for the same condition in the same pass. This is a wording
defect, and a wording defect is rarely in one file —git grep -n 'monorepo'over the plugin is the
check. - Verified by an
/explorerun in a real Consumer through a marketplace install, in a repository with
one domain and several packages, showing the agent neither reports the map missing nor creates one.
Note on sizing
Small, and it belongs with whoever next touches a Box. It does not block anything.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at apps/claude-code/unic-archon-dlc/.archon/workflows/unic-dlc-explore.yaml:178 and read .archon/unic-dlc.config.yaml:29 alongside the referenced CONTEXT-FORMAT.md section. Run git grep -n 'monorepo' over the plugin to check other Boxes and commands. Done means bounded-context or repo_layout handling is consistent, no instruction creates CONTEXT-MAP.md, and a marketplace-installed /explore run in a single-domain multi-package consumer does neither.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100