Complete System

One product flow documented across product, feature, API, review, and diagrams.

This page surfaces the complete-system sample directly in the published site so a buyer or adopter can see how RepoDocs AI assets fit together in a realistic payments use case.

Product

Payments Platform

The sample product supports payment creation, retrieval, hosted checkout, and operator-facing workflows. It shows how product-level context frames the API and feature docs.

  • Shared API for payment lifecycle operations
  • Hosted and API-driven collection flows
  • Linked ownership and dependency metadata

Feature

Payment Links

The sample feature shows how a merchant operator creates a branded payment link, shares it, and tracks final payment status from the dashboard.

  • Depends on checkout and notifications services
  • Documents workflow, configuration, and limitations
  • Connects feature behavior to API and architecture assets

API Flow

Two endpoint documents anchored to the same OpenAPI source

Endpoint 1

Create Payment

POST /payments documents authentication, request payload, response fields, and error conditions for payment creation.

Endpoint 2

Retrieve Payment

GET /payments/{payment_id} now shows lifecycle validation with a deprecation notice and a migration path to the replacement status endpoint.

Review

Governance closes the loop

The sample review report captures moderate issues, missing SME input, and publication constraints before documentation goes live.

Architecture Diagram

System context

flowchart TD
    Merchant[Merchant Operator] --> Dashboard[Merchant Dashboard]
    Dashboard --> API[Payments API]
    API --> Auth[Auth Service]
    API --> Ledger[Ledger Service]
    API --> Checkout[Checkout Service]
    Checkout --> Customer[Customer Payment Page]
    API --> Notifications[Notifications Service]

Data Flow

Payment lifecycle movement

flowchart LR
    Client[Client App] --> Gateway[API Gateway]
    Gateway --> Payments[Payments API]
    Payments --> Ledger[(Ledger)]
    Payments --> Events[(Event Stream)]
    Events --> Notifications[Notifications]
    Ledger --> Dashboard[Merchant Dashboard]

Repository Assets

The published view mirrors the full example set in the repository.

The underlying Markdown and diagram assets are stored in `examples/complete-system/`, and this page presents the same system narrative as a buyer-facing preview of the docs-as-code workflow, including lifecycle and migration coverage.