Skip to content

specs/tools: the tri CLI and the MCP servers as first-class .t27 specs (layer 5) - #3548

Closed
gHashTag wants to merge 1 commit into
feat/specs-agentsfrom
feat/specs-tools
Closed

specs/tools: the tri CLI and the MCP servers as first-class .t27 specs (layer 5)#3548
gHashTag wants to merge 1 commit into
feat/specs-agentsfrom
feat/specs-tools

Conversation

@gHashTag

@gHashTag gHashTag commented Sep 9, 2026

Copy link
Copy Markdown
Owner

Layer 5 -- the tri CLI and the MCP servers as first-class .t27 specs

Closes #3547. Stacked on #3546 (feat/specs-agents); retarget to master once #3546 merges.

What

  • specs/tools/tri/<command>.t27 x52 (module tool_tri_<command>), one per variant of the clap Commands enum in cli/tri/src/main.rs; specs/tools/mcp/<server>.t27 x10 (module tool_mcp_<server>), one per MCP server of gHashTag/t27 (5) and gHashTag/trinity (5). Schema and witness rule in specs/tools/README.md.
  • Witness: source-parse 52/52 -- cargo was not run; the enum and its /// docs were read at commit 3cb7a4352492. help-output (list diffed against tri --help) is 0/52 until someone runs it. Variants without a doc quote the source they borrow from in ABOUT_SOURCE.
  • MCP: 235 tools with input-schema keys from the server code / manifests; 5 servers EXTERNAL = true (published packages, tool list not in the repo) and say so in TOOLS_NOTE. tri-mcp is not registered in .mcp.json (CONFIG = ""); tri-ssot's manifest names a module the tree lacks -- recorded, not resolved.
  • Two CLIs are two lists: trinity has no tri binary at its pinned commit, so its tools are its MCP servers only (REPO = "gHashTag/trinity").
  • Agent bindings both ways, evidence-gated: tri/gen (C, T), tri/test (T, V), tri/verdict (V), tri/experience (E), tri/cell (W) -- specs/agents/{c,e,t,v,w}.t27 gain TOOLS; 22 letters carry TOOLS = [] + TOOLS_NOTE; 57/62 tools carry AGENTS = [] + AGENTS_NOTE naming the sources checked.
  • specs/i18n/agents-ru.t27 SCOPE -> [4]str (+ specs/tools); specs/OWNERS.md row tools/ -> T-Queen; docs/now/2026-09-09-the-tri-cli-and-mcp-servers-as-t27-specs.md.

Measured (site side, gHashTag/trinity PR): 62/62 typecheck ok under the vendored wasm 4d9c0447b5ca2887..., nothing discarded; ru 62/62.

Checks run here: python3 tools/check_devhome_paths.py (no FAIL new; the FAIL fixed lines are the sparse checkout), PR_BASE_SHA=$(git rev-parse origin/master) GITHUB_BASE_REF=master python3 tools/check_now_entry_shape.py (OK, 2 entries), Cyrillic/ASCII scan of specs/tools/**, specs/agents/*, docs/now.

Boundaries: English-only, ASCII-only files; no absolute home paths (the checkout is T27_ROOT / git rev-parse --show-toplevel); the three pre-existing files at the top of specs/tools/ are untouched corpus specs; no --bless; gate-topology and untrusted-input are the known pre-existing reds. Not merged -- review requested.

phi^2 + 1/phi^2 = 3 | TRINITY

…s (layer 5)

52 tri command specs read from the clap enum in cli/tri/src/main.rs (witness
source-parse at 3cb7a43; cargo not run) and 10 MCP server specs from the
.mcp.json entries, manifests and server sources of gHashTag/t27 and
gHashTag/trinity (5 external). Agents C, E, T, V, W gain TOOLS where a source
binds a command; the other 22 carry TOOLS_NOTE. specs/i18n/agents-ru.t27 SCOPE
gains specs/tools. specs/tools/README.md states the schema and the witness
rule; OWNERS row tools/ -> T-Queen; docs/now entry.

Closes #3547
@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant