Repository navigation
Write the tracker contract files in DXP-DesignSystem #388
Description
Question
Write the tracker contract for DXP-DesignSystem by hand, as two files in the Consumer repo. This is
the Consumer half of #387, and it lands first
because it unblocks #379 on its own: the four Methods installed at .archon/methods/ read these files
directly, so they work before any Box is edited.
The work happens in the Consumer's clone, on feature/42928_initial-DLC-installation.
Today that repo has no docs/agents/ directory at all, and code-review — which /pr-review reads —
already looks for one.
Every fact needed is on #387: the tenant-facts comment carries the three area paths, the tag usage and
the two load-bearing roles; the resolution comment carries the section list and the rule that decides
what belongs in a section.
Acceptance criteria
-
docs/agents/issue-tracker.mdstates which MCP server serves the tracker, the organisation,
project and repository, and the area path that scopes this repository's work items — including
that every search filters on it. -
docs/agents/triage-labels.mdstates all seventeen roles, and each row names its axis. The two
load-bearing roles resolve to the tags the Consumer already uses, not to a state. - Neither file contains a CLI subcommand or flag. The
Operationssection is written only if the
registered MCP server cannot supply an operation, and the file says which one. - Both files state at the top that DLC
/setupowns them, and that running
setup-matt-pocock-skillsovertriage-labels.mdreverts the vocabulary. - A Method reads the contract without a follow-up question: run
/triageon one work item in
dxpand record what it resolved the state role to.
Activity
orioltf commentedon Aug 18, 2026
Resolution
The tracker contract exists in
DXP-DesignSystemand is merged. PR !5769 completed on 2026-08-18(
4a9e227), work item 42928 isResolved.docs/agents/issue-tracker.md— Access, Addressing, Work-item scope.docs/agents/triage-labels.md—the seventeen roles, each row naming its own axis. Both name DLC
/setupas their owner and warn thatsetup-matt-pocock-skillsreverts the vocabulary.Matt's two-file split was kept rather than merged into one, for compatibility: someone who knows his
system looks in
triage-labels.mdfor the vocabulary, and onlycode-reviewhard-codes a path.Criteria
Four of five met. The fifth moved to #390,
which owns it explicitly.
Operationssection is absent because the
azure-devopsMCP server supplies every operation the DLC needs —verified against the running server, which exposes
wit_work_item(_write),wit_work_item_comment_write,wit_work_item_link_write,wit_query,search_workitem,repo_pull_request(_write)andrepo_pull_request_thread(_write).reviewnode ofunic-dlc-pr-reviewreasoned from both files and cited them by line —issue-tracker.md:38for thearea path,
triage-labels.md:18-22for the write-nothing roles. What is not done is resolving astate role through
/triage, because the command Boxes are not installed. Install the DLC's command Boxes in DXP-DesignSystem #390 does that.What writing it found
Three defects that no amount of deciding would have surfaced.
needs-triage,needs-infoand
ready-for-humanonto StateNew. Triage a work item that is alreadyActiveand that writemoves it backwards on a client board. All three now write nothing:
Newalready states anuntriaged item, a question belongs in a comment, and a human picking work up is an assignment.
pnpm formatwas forking the Method Bundle. The Consumer's Prettier glob is**/*.{ts,tsx,md}and nothing excluded.archon/methods/, so one run rewrote thirteen files ofupstream text pinned to a
mattpocock/skillsversion. Fixed with one.prettierignoreentry, andfiled on #383 because every Consumer with
a Markdown glob has it.
docs/agents/unic-archon-dlc.mdnow carries it, plus what is not installed — the Claude Codecommands are a different Container, so a file copy never reaches them, which is why Install the DLC's command Boxes in DXP-DesignSystem #390 exists.
The Box reviewed its own installation
Three
unic-dlc-pr-reviewruns against !5769, which is how most of the above was caught.Iteration 1 found two defects in the branch: the install sequence was not in the repository, and the
Azure DevOps findings were not on the work item. Both are #376 acceptance criteria that were written
on the GitHub ticket and never read back against WI 42928. Iteration 2 classified
5 fixed · 5 still present · 0 regressed · 4 new and updated its summary thread in place.
Its sharpest catch had nothing to do with the DLC:
pnpm devnever started theui-reactwatchers —turbo.jsonuses nowithandui-reactdeclares nodevscript — whileCLAUDE.mdand the READMEsaid otherwise in three places. That bug predates this branch.
Every Azure DevOps path in that Box has now run: read work items, find the PR from the branch, scan
threads, post a summary, update it in place, open inline threads. The MCP server registered in the
Consumer's
.mcp.jsonloads inside an Archon worktree at a path no human approved — unknown beforethis, and the thing every "compose the registered skill" instruction depends on.