Code Swan · film principal · guion nuevo

Doce beats, registro factual.

Abre a nivel organización, suma búsqueda semántica y el ahorro de tokens. Falta regrabar la locución.

Every team runs on context.

#engineering-help

MO Maya Ortizengineering · 9:41 AM who owns payments-api these days? need someone to review a change

Inbox

Can we promise partial refunds this quarter?

TW Tom Weberproduct · 9:58 AM to team-payments

a customer is asking. what would we have to touch to do it?

PAY-1183 Refund stuck for customer #8812

NL Nora Langsupport · commented 2 hours ago which service owns refunds now? I need to tell the customer something

acme/checkout-web#482

DK Dana Kimarchitecture · requested changes does this break anyone downstream? I cannot tell from the diff

Nobody knows the whole system.
Everyone asks the same two or three people.

Today

ARCHITECTURE.md

# Architecture Last updated 14 months ago ## Services - payments-api - orders-service …8 listed · 23 in the code

Payments / System overview

Payments — system overview Last edited 2 years ago · 3 people still watching

The checkout flow calls the billing service, which writes to the ledger…

This page may be out of date.

architecture-final-v3.png · exported 2 years ago

settle.goledger.go

142func settle(o Order) error { 143 // TODO: document this 144 return ledger.Write(o) 145}

the rest is in people’s heads

Reading your code

scanning 41 repositories

payments-api / settle.go r.POST("/v1/charges", s.createCharge)

payments-api / settle.go sql.Open("postgres", cfg.PaymentsDSN)

payments-api / settle.go producer.Send(ctx, "orders.settled", evt)

orders-service / consumer.ts kafka.subscribe("orders.settled", onSettled)

orders-service / consumer.ts fetch("http://payments-api/v1/charges")

infra / payments.tf resource "aws_sns_topic" "orders_settled" {}

fraud-detection / Scorer.java @KafkaListener(topics = "orders.settled")

billing-api / refunds.go r.POST("/v1/refunds", s.refund)

accounting / ledger.cs s3.GetBucket("ledger-exports")

checkout-web / CODEOWNERS /checkout/ @team-web

catalog

apiPOST /v1/charges

resourcepayments-db

eventorders.settled

consumerorders.settled

callspayments-api

topicorders.settled · sns

consumerorders.settled

apiPOST /v1/refunds

resourceledger-exports · s3

owner@team-web

One question, one session

claude — code swan — -zsh — 80×24

> I need to add partial refunds to the payments API. What will this touch?

Crunching… (esc to interrupt)

⏺ codeswan - search_components (MCP)(query: "payments API")

⎿ 1 match · payments-api · 8f3c1d2a-4b71-4e0d-9a55-2c6f7d10ab34

⏺ codeswan - get_component (MCP)(id: "8f3c1d2a-4b71-4e0d-9a55-2c6f7d10ab34")

⎿ payments-api · service · Go · @team-payments

apis POST /v1/charges · GET /v1/charges/:id

resources payments-db · orders.settled

⏺ codeswan - get_dependents (MCP)(id: "8f3c1d2a-4b71-4e0d-9a55-2c6f7d10ab34")

⎿ 4 consumers

orders-service api

ledger-sync api

accounting event orders.settled

fraud-detection event orders.settled

> and where do we already handle refunds?

Searching by meaning… (esc to interrupt)

⏺ codeswan - semantic_search (MCP)(query: "where do we already handle refunds")

⎿ 3 matches, by meaning

billing-api/credit-notes 0.91

payment-retry-worker 0.84

dunning-scheduler 0.79

Measured against code search

3×the accuracy of code search35% → 94% of an architecture question

−32%tokens per answerthe same answer, a third less to pay for

5×fewer hallucinations40 → 8 wrong services per 100 answers

Three models · 2,200 scored answers · four frontier models · 3,300 scored answers.

Read the benchmark

Before the change is written

build test codeswan · impact deploy

3 services · 2 features · 2 teams

Your code, grouped into features.

engineeringproductsupportread the same thing

Code Swan.
The context layer for your team.

Book a demo

Code Swan

Every software organisation
runs on context.

0:00

Guion — 93 s · 244 palabras0:00Every team runs on context: who owns what, what connects to what, what breaks when you change it.
07Nobody knows the whole system. Engineering, product and support end up asking the same two or three people. Code Swan gives them the answer directly.
17Documentation goes out of date. The rest stays in people’s heads.
22Code Swan reads every repository and understands your code exactly as it is.
27From that it builds a software catalog that mirrors every service, API and cloud resource you have, updated the moment your code changes.
36Your agents ask over MCP and get accurate answers, even for async APIs like Kafka or Pub Sub.
43And it searches by meaning, so your agents find the code that does the job even when no file uses those words.
51We measured it. With Code Swan MCP, agents answered ninety four percent of an architecture question, against about a third without it, with five times fewer wrong services and a third fewer tokens.
03Your agents can see how services connect, so before a change is even written they know what it will touch: other services, other features, other teams.
13It also groups your code into features and writes the design document for each one, kept current with the code. Engineering, product and support read the same thing, so most questions get answered without asking anyone.
27Code Swan. The context layer for your team. Want to see it on your own code? Book a demo.