Example Profiles
These pages show how the shared integrations generator turns a repo profile into a consistent artifact pack. Each example mirrors a real RepoFactsExampleProfile shipped in docs_ui, so you can compare the expected REPO_FACTS.json shape, provenance fields, and rendered outputs before drafting your own repo context.
Use this section when you want to answer one of three practical questions:
- What does a service-oriented profile look like when commands, integration inputs, and runbooks are the important context?
- How much parity and wire-contract detail belongs in an SDK-focused profile?
- What should a frontend-oriented profile emphasize when the integration surface is browser flows and backend APIs?
Compare the shipped examples
| Example | Repo kind | Language | Primary use | Source repo path | Snapshot date |
|---|---|---|---|---|---|
| Go service | service | go | Go notification delivery service centered on notify-sender over triggers-v2. | momentum-online/notify | 2026-06-05 |
| Python SDK | sdk | python | Python SDK for the Triggers orchestrator with explicit Go parity expectations. | momentum-online/triggers-sdk-python | 2026-06-05 |
| Frontend dashboard | frontend-dashboard | typescript | Next.js admin dashboard for Lumio workflows, analytics, and document management. | momentum-online/lumio_admin_dashboard | 2026-06-05 |
Choose a starting point
- Go service example: best when you are documenting a runtime service with concrete entrypoints, local stack commands, and transport dependencies.
- Python SDK example: best when your repo is a library with public behavior, parity expectations, and protocol-sensitive verification.
- Frontend dashboard example: best when your repo centers on UI routes, backend API integration, and operator-facing browser workflows.
What these examples are meant to teach
- The facts stay aligned with the generator model:
repo,entryPoints,commands,integrationSurface,sourceDocs,lifecycle,ownership, andagentBehavior. - Provenance is first-class context, not an afterthought. Each example carries
sourceRepoPath,snapshotDate,ownerOrSteward, and a note describing how the profile was derived. - The rendered artifact pack is shared across examples. Once the facts are coherent, the same renderer path can produce
REPO_FACTS.json,REPO_CONTEXT.md,AGENTS.md, andSYSTEM_PROMPT.md.
Open one of the detail pages to inspect the profile fields and the generated artifact preview for that example.