Skip to main content

Team Topology

@webframp/team-topologyv2026.09.15.1· 1d agoMODELS
01README

Agent-guided team topology and value stream mapping model. Captures teams (type, cognitive load, domains), interactions (modes, health), system ownership, and value stream flows as versioned snapshots. Designed for incremental discovery through structured conversations — the agent interviews, the model persists.

Draws on Team Topologies (Skelton & Pais), Conway's Law, Westrum organizational typology, GROWS method tracer bullets, and Ruth Malan's evolutionary architecture thinking.

02Release Notes

2026.09.15.1

Changed: Bump zod 4.4.3 → 4.6.5

2026.08.28.1

Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.

Upgrade note: License text only. No API, schema, or runtime behavior changed.

2026.08.26.3

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

03Models1
@webframp/team-topologyv2026.09.15.1team-topology/mod.ts

Global Arguments

ArgumentTypeDescription
organizationContextstringBrief description of the organization, its size, and primary business
scopestringScope of this topology instance: 'full' org, a division name, or a product area
fn discover_topology(teams: array, interactions: array, systemDependencies: array, notes?: string)
Discover and record team topology through structured conversation. AGENT GUIDANCE: You are mapping an organization's team structure using Team Topologies concepts. Guide the conversation through these phases: 1. TEAM INVENTORY Ask: "What teams exist in this area? For each team, what is their primary responsibility?" List them out. Don't worry about classification yet — just get names and purposes. 2. TEAM TYPE CLASSIFICATION For each team, determine its fundamental type: - str
ArgumentTypeDescription
teamsarrayTeams discovered through conversation
interactionsarrayInteractions between teams
systemDependenciesarraySystem-level dependencies that cross team boundaries
notes?stringContext about this discovery session
fn map_flow(streams: array)
Map value streams through structured conversation. AGENT GUIDANCE: You are mapping how work flows through the organization end-to-end. Use a tracer-bullet approach: pick ONE flow first, map it completely, then add more. 1. STREAM IDENTIFICATION Ask: "What are the main flows of work in this area? Think about it from trigger to customer outcome. Examples: - Feature request → shipped feature - Incident → resolution - New hire → productive engineer - Security finding → remediate
ArgumentTypeDescription
streamsarrayValue streams mapped through conversation
fn record_assessment(findings: array, summary: string)
Record an assessment of the current topology and flows. AGENT GUIDANCE: You have read the topology and flows resources. Now analyze them for problems and opportunities. Look for these categories of findings: 1. COGNITIVE LOAD - Teams where intrinsic + extraneous exceeds capacity - Teams owning too many domains or systems - Platform teams that are actually doing stream-aligned work 2. CONWAY'S LAW MISMATCHES - System dependencies that don't match team interaction patterns - Tea
ArgumentTypeDescription
findingsarrayFindings from analyzing the topology and flows
summarystringBrief narrative summary of the assessment

Resources

topology(infinite)— Snapshot of team structure, interactions, and system ownership
flows(infinite)— Value stream maps with step-level metrics
assessment(infinite)— Agent-produced findings about the topology (load, mismatches, friction)
04Previous Versions9
2026.08.28.1

2026.08.28.1

Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.

Upgrade note: License text only. No API, schema, or runtime behavior changed.

2026.08.26.3

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.26.3

2026.08.26.3

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.26.1

2026.08.26.1

Fixed: Added missing description field to upgrade entry for version 2026.08.24.2. The omission caused swamp extension pull to fail with a catalog validation error ("upgrades.N.description: Invalid input: expected string, received undefined").

2026.08.24.3

2026.08.24.3

Added: Output metadata attributes for observability.

  • durationMs: Method execution duration in milliseconds.
  • collectedBy: Extension name that produced the data.
  • fetchedAt: ISO 8601 timestamp when data was fetched (added to resources that previously lacked it).
2026.08.24.2

2026.08.24.2

Added Troubleshooting section documenting referential integrity validation in discover_topology, strict method ordering, agent-context-only global args, and JSON input requirements.

2026.08.21.2

2026.08.21.2

Changed: discover_topology now rejects a call where an interaction's source/target or a system dependency's ownerFrom/ownerTo names a team that isn't present in that same call's teams array. Previously a typo'd or stale team name was written into the topology snapshot without complaint, producing a graph edge that pointed at nothing — the error now names the unknown team(s) and lists the known team names.

Upgrade note: No schema changes. If you were passing interactions or system dependencies that reference teams outside the current call's teams list, include those teams in the call or the write will now fail with a descriptive error instead of silently succeeding.

2026.08.21.1

Changed: Added .describe() to previously undocumented fields across the schema — the team-type/interaction-mode/Westrum-culture enums, the notes fields on interactions/flow steps/value streams, the Finding fields (category, severity, title, description, affectedTeams, recommendation), and the top-level TopologySchema/FlowsSchema/ AssessmentSchema fields. No behavioral change.

2026.07.18.1

Added: An upgrades array entry (no-op) to mod.ts for proper typeVersion tracking on existing instances. No schema or behavior changes.

2026.08.21.1

2026.08.21.1

Changed: Added .describe() to previously undocumented fields across the schema — the team-type/interaction-mode/Westrum-culture enums, the notes fields on interactions/flow steps/value streams, the Finding fields (category, severity, title, description, affectedTeams, recommendation), and the top-level TopologySchema/FlowsSchema/ AssessmentSchema fields. No behavioral change.

2026.07.18.1

Added: An upgrades array entry (no-op) to mod.ts for proper typeVersion tracking on existing instances. No schema or behavior changes.

2026.07.18.1

2026.07.18.1

Added: An upgrades array entry (no-op) to mod.ts for proper typeVersion tracking on existing instances. No schema or behavior changes.

2026.06.29.1
05Stats
A
100 / 100
Downloads
2
Archive size
25.1 KB
  • Has README or module doc2/2earned
  • README has a code example1/1earned
  • README is substantive1/1earned
  • Most symbols documented1/1earned
  • No slow types (deprecated)1/1earned
  • Dependencies pass trust audit2/2earned
  • Has description1/1earned
  • Platform support declared (or universal)2/2earned
  • License declared1/1earned
  • Verified public repository2/2earned
06Platforms
07Labels