Skip to content

fix(baa-dev): route session analysis to session-analyst; ground architect reviews in tool evidence #255

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sadlilas merged 1 commit into from
Jun 18, 2026
+7 −1
Merged

fix(baa-dev): route session analysis to session-analyst; ground architect reviews in tool evidence #255

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion experiments/behavioral-anchor-amplifier-dev/agents/architect.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,8 @@ tools:
source: git+https://github.com/microsoft/amplifier-module-tool-filesystem@main
- module: tool-search
source: git+https://github.com/microsoft/amplifier-module-tool-search@main
- module: tool-web
source: git+https://github.com/microsoft/amplifier-module-tool-web@main
---

# Architect
Expand All @@ -37,4 +39,4 @@ You produce actionable specifications and design reviews.
1. Every abstraction must justify its existence.
2. Start with the simplest viable design.
3. Specs must include: file paths, interfaces with types, success criteria.
4. Reviews must cite specific `file_path:line_number` evidence.
4. Reviews must cite specific `file_path:line_number` evidence read via a tool call in THIS session. Never assert line counts, file contents, or duplication you have not actually read or fetched (use `tool-web` to fetch a PR/diff before reviewing it). If you could not read it, say so — do not describe it.
2 changes: 2 additions & 0 deletions experiments/behavioral-anchor-amplifier-dev/behavioral-anchor-amplifier-dev.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,8 @@ agents:
- behavioral-anchor-amplifier-dev:git-ops
- behavioral-anchor-amplifier-dev:researcher
- behavioral-anchor-amplifier-dev:amplifier-dev-expert
# Session analysis/repair: required route for events.jsonl + broken-session work
- foundation:session-analyst
---

# Behavioral Anchor
Expand Down
2 changes: 2 additions & 0 deletions experiments/behavioral-anchor-amplifier-dev/context/system.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,4 +46,6 @@ Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.co

**Delegate dev-ecosystem questions.** "How does Amplifier work?" and "how do I author a bundle?" both go to the amplifier-dev-expert agent — it holds the authoritative knowledge.

**Delegate session analysis.** Analyzing, debugging, searching, or repairing Amplifier sessions — and any reading of `events.jsonl` — goes to the `foundation:session-analyst` agent. Never read `events.jsonl` directly; its lines can exceed 100k tokens and will crash the session.

Ecosystem and bundle-authoring knowledge lives in the **amplifier-dev-expert** agent.
Loading