T-CIAA-nested-solutions-ontological-agent-pants-yaml-build-config
State: closed/done · Impact: high · Complexity: medium
The repo’s single root agent-pants.yaml treats content/agent-vault
as the one vault for every plugin. Once sdlc’s plugin files move onto
the vault-note shape, sdlc needs its own build config — most plausibly
a vault root scoped under solutions/ontological/ since sdlc’s plugin
sources (its skills, CLI, scripts) already live there, per the plan’s
own instruction to “add a mode to agent-pants rather than moving skills
away from the CLI.”
agent-pants.yaml (repo root) has one vault:/marketplace: pair
pointing at content/agent-vault/published/marketplaces/sksizer.
agent-pants has no notion of more than one vault root per invocation,
and nothing about it supports a vault nested inside a directory that
also holds non-vault source (the CLI, lib/, converted skill notes
side by side).
Proposed
Section titled “Proposed”A solutions/ontological/agent-pants.yaml nested build config, plus
whatever agent-pants change is required to run against a vault root
that is not the sole vault in the repo (a --config-style invocation,
or agent-pants natively supporting more than one project file walked
independently).
Approach
Section titled “Approach”- Establish what agent-pants needs to build one plugin from a vault root that lives inside a larger
non-vault tree (
solutions/ontological/) without colliding with the root project’s ownagent-pants.yaml/content/agent-vault. - Add that mode to agent-pants (likely a new CLI flag accepting an explicit project-file path, since today it only walks up to find the nearest one).
- Write
solutions/ontological/agent-pants.yamlpointing itsvault:at the directory holding the converted notes and itsmarketplace.outat a build destination distinct frompublished/marketplaces/sksizer. - Verify
agent-pants buildinvoked with sdlc’s nested config builds only the sdlc plugin, and the root invocation is unaffected.
| Area | Note |
|---|---|
solutions/ontological/agent-pants.yaml | New nested build config |
agent-pants crate/CLI | New mode/flag for an explicit project-file path — outside solutions/ontological |
agent-pants.yaml (repo root) | Verifying no regression |
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: solutions/ontological/agent-pants.yaml exists with a vault:/marketplace: pair scoped to sdlc.
- AC-2:
agent-pants buildrun against the nested config produces sdlc’s built plugin tree without touchingpublished/marketplaces/sksizer. Verified correct and complete on an isolated copy of the vault; a real in-repo run is currently blocked by an unrelated, already-tracked issue (T-66RD) in one skill’s test fixtures — see completion_note. - AC-3:
agent-pants buildrun against the repo-root config still builds pr-tools/dev-agent unchanged (no cross-talk between the two vault roots).
Out of scope
Section titled “Out of scope”- Choosing sdlc’s final public build destination (that is Phase 14’s marketplace-sdlc mechanics).
- Any change to how pr-tools/dev-agent build.
Dependencies
Section titled “Dependencies”- The plugin-files cutover task (the converted vault notes this config points at).