Synthesis

Synthesis

TeamLoop’s synthesis feature generates structured documents from your knowledge graph. Transform curated subgraphs into ADRs, PRDs, executive briefs, and more.

How Synthesis Works

1. Create a subgraph with relevant entities
2. Select a template (brief, PRD, ADR)
3. Start synthesis job
4. Poll for completion and get output

┌─────────────┐    ┌─────────────┐    ┌─────────────┐
│  Subgraph   │───▶│   Template  │───▶│   Output    │
│ (entities)  │    │   Engine    │    │  Document   │
└─────────────┘    └─────────────┘    └─────────────┘

Starting a Synthesis Job

teamloop_synthesize:
  subgraph_id: "your-subgraph-uuid"
  template_type: "adr"
  additional_context: "Focus on security implications"

Parameters:

Parameter	Required	Description
subgraph_id	Yes	The subgraph to synthesize from
template_type	Yes	brief, prd, or adr
additional_context	No	Extra instructions or focus areas

Response:

Synthesis job created!

- **Job ID:** abc-123-def-456
- **Template:** Architecture Decision Record (adr)
- **Status:** pending

Use `teamloop_get_synthesis_job` with this job_id to check progress.

Checking Job Status

teamloop_get_synthesis_job:
  job_id: "abc-123-def-456"

Response (in progress):

## Synthesis Job Status

- **Job ID:** abc-123-def-456
- **Status:** processing
- **Progress:** 45%
- **Started:** 2024-12-15T10:30:00Z

Response (completed):

## Synthesis Job Status

- **Job ID:** abc-123-def-456
- **Status:** completed
- **Progress:** 100%
- **Completed:** 2024-12-15T10:32:00Z

---

## Output

# ADR-001: Adopt OAuth 2.0 for Authentication

## Status
Accepted

## Context
The team needed to implement single sign-on (SSO) capabilities
for enterprise customers...

## Decision
We will adopt OAuth 2.0 with PKCE for all authentication flows...

## Consequences
### Positive
- SSO support for enterprise customers
- Industry-standard security
...

Template Types

Brief

Executive summary of the knowledge in a subgraph.

Best for:

• Leadership updates
• Project summaries
• Quick overviews

Structure:

• Executive summary
• Key decisions
• Timeline highlights
• Current status
• Next steps

PRD (Product Requirements Document)

Product requirements derived from knowledge.

Best for:

• Feature specifications
• Project scoping
• Planning documents

Structure:

• Overview
• Problem statement
• Goals and non-goals
• User stories
• Requirements
• Success metrics

ADR (Architecture Decision Record)

Formal documentation of architectural decisions.

Best for:

• Technical documentation
• Decision records
• Architecture reviews

Structure:

• Title and status
• Context
• Decision
• Consequences (positive/negative)
• Alternatives considered

Workflow Example

Step 1: Build Knowledge

First, query and extract relevant knowledge:

# Query for authentication-related content
teamloop_query:
  query: "authentication architecture decisions"
  sources: "github,notion"

# Save extracted entities
teamloop_save_knowledge:
  entities:
    - type: DECISION
      name: "Adopt OAuth 2.0"
      rationale: "Need SSO for enterprise"
      event_date: "2024-06-15"
      alternatives: ["SAML", "Custom JWT"]
    - type: COMPONENT
      name: "Auth Service"
      description: "Central authentication service"

Step 2: Create Focused Subgraph

teamloop_create_subgraph:
  name: "Auth System ADR Context"
  query: "authentication OAuth SSO"
  limit: 25

Step 3: Expand if Needed

teamloop_expand_subgraph:
  subgraph_id: "..."
  depth: 1
  include_types: ["DECISION", "COMPONENT"]
  auto_add: true

Step 4: Synthesize

teamloop_synthesize:
  subgraph_id: "..."
  template_type: "adr"
  additional_context: "This ADR documents our move from session-based auth to OAuth 2.0"

Step 5: Get Result

teamloop_get_synthesis_job:
  job_id: "..."

Canceling Jobs

Cancel pending or in-progress jobs:

teamloop_cancel_synthesis_job:
  job_id: "abc-123-def-456"

Best Practices

1. Curate Your Subgraph

Better input = better output:

# Too broad
teamloop_create_subgraph:
  query: "decisions"
  limit: 100

# Better - focused
teamloop_create_subgraph:
  query: "database technology PostgreSQL MySQL"
  limit: 20

2. Use Additional Context

Guide the synthesis:

teamloop_synthesize:
  subgraph_id: "..."
  template_type: "prd"
  additional_context: "Focus on the mobile app requirements. Target audience is the iOS development team."

3. Review and Iterate

Synthesis output is a starting point:

• Review for accuracy
• Add missing context
• Adjust tone and style
• Validate technical details

4. Right Template for Right Purpose

Use Case	Template
Leadership update	brief
New feature spec	prd
Technical decision record	adr

Output Quality

Synthesis quality depends on:

1. Subgraph richness - Include decisions, rationale, alternatives
2. Entity completeness - Fill in descriptions, dates, relationships
3. Context clarity - Use additional_context to guide focus
4. Temporal coverage - Include historical context

Limitations

• Synthesis may take 30-120 seconds
• Maximum subgraph size: 100 entities
• Output is AI-generated - always review
• Complex topics may need multiple synthesis runs

Saved Outputs

Completed synthesis outputs are saved as entities:

**Saved as Entity ID:** ghi-789-jkl-012

Query them later:

teamloop_query:
  query: "Auth System ADR"

Next Steps

• Subgraphs - Create better inputs
• Knowledge Graphs - Build richer entities
• MCP Tools Reference - Full tool documentation