angada
Sign inStart with GitHub

AI Wiki

Find the right starting point in your codebase.

Angada generates repository documentation that gives a team a readable starting point, with source citations, diagrams, retained generations, and visible freshness signals.

Start with GitHub
Review
Wiki
Notifications
Workspace
Wikiorbit / payments
Generated wiki Fresh from 7d91c2a

Payments repository overview

The payments package owns capture, webhook normalization, and ledger writes. It sits between product clients and external payment processors, with the event bus carrying durable updates to downstream services.

Client apps and payment processors connect to the payments service, which connects to the ledger and event bus

System architecture

The payments service exposes capture and webhook handlers at one boundary. Client applications use the service, while provider callbacks return through the same normalized path.

Payment boundaries

The event ID is retained before payment and ledger writes complete, making a repeated provider delivery safe to recognize and ignore.

Core glossary

Normalized payment events are persisted in the ledger and made available to downstream consumers through the event bus.

Relevant source filespackages/payments/README.md · lines 1–18
packages/payments/src/webhooks.tspackages/payments/src/ledger.tspackages/payments/README.md

Documentation with a trail

A map your team can inspect.

Wiki pages are useful when they show where an explanation came from and how recently the repository was refreshed.

Source citations

Trace a page back to the repository paths that informed it instead of treating generated prose as an authority.

Pages and diagrams

Move from a readable page to a focused architecture diagram or the source context behind a section.

Refresh with a signal

Regenerate when needed and see freshness indicators for configured automatic refreshes. Refresh is asynchronous, not instant.

A starting point that stays connected to source.

Source citations and freshness indicators keep the generated pages useful as your repository evolves.

Search the page index

Find pages by their title or path in the wiki navigation and open the source-linked context.

Keep generations available

Retained generations make it possible to compare what changed as the repository evolves.

Automatic means configured

Teams can configure refresh behavior, with freshness indicators showing the state of the latest generation.