Service Boundary Analysis
Intent
- Goal: One compact report of a backend service's inputs and visible outputs with evidence and confidence.
- Limits: Static only: no execution, edits, security review, schema design, or certainty for dynamic wiring.
- Fails if: A row lacks
file:line and discovery method; confidence is inflated; names are trusted without tracing cross-file wiring and each candidate to its peer/destination.
Context
- Reads: Manifests and target files (language/framework); routes, annotations, registrations, imports, handlers, clients, repositories, publishers, schedulers, config, healthy graph edges.
- Never reads: Local debug logs as outputs.
- Persona: Static boundary tracer.
- Scope: One backend service, module, worker, or API; require target, scope, exclusions, report path. One report per service.
Expectations
- Scenarios: WHEN reflection, generation, missing config, or indirection blocks resolution THEN list under
Uncertain.
- Done means: One report below. Keep empty mandatory tables with
No evidence found in inspected scope.; omit empty Uncertain and Limitations.
- Quality needs: Group equivalent boundaries; include symbol when available.
Method
Inputs: HTTP/API, RPC, messages/streams, WebSocket/SSE, scheduled jobs, CLI/batch/workers, file/object triggers, config loading.
Outputs: database writes, external calls, event publishing, cache changes, file/object writes, search/vector writes, notifications, job scheduling, boundary-relevant telemetry.
Confidence: high direct mechanism and peer/destination evidence; medium corroborated registration, convention, or cross-file wiring; low plausible, incomplete, or dynamic.
# Service Boundary Report
## Scope
<target, inspected paths, exclusions>
## Inputs
| Category | Mechanism | Source/peer | Evidence | Confidence | Notes |
|---|---|---|---|---|---|
## Outputs
| Category | Mechanism | Destination | Evidence | Confidence | Notes |
|---|---|---|---|---|---|
## Uncertain
- <finding, evidence, limit>
## Limitations
- <uninspected or runtime-only behavior>
1---2name: oc-boundary3description: "Trigger: service boundary analysis, microservice inputs/outputs, API/consumer/output mapping. Map one backend boundary with evidence and confidence."4license: MIT5metadata:6 source: https://skillmd.com/skills/andresnator/oc-boundary7 author: andresnator8 status: testing9 version: "3.1.0"10---1112# Service Boundary Analysis1314## Intent1516- **Goal:** One compact report of a backend service's inputs and visible outputs with evidence and confidence.17- **Limits:** Static only: no execution, edits, security review, schema design, or certainty for dynamic wiring.18- **Fails if:** A row lacks `file:line` and discovery method; confidence is inflated; names are trusted without tracing cross-file wiring and each candidate to its peer/destination.1920## Context2122- **Reads:** Manifests and target files (language/framework); routes, annotations, registrations, imports, handlers, clients, repositories, publishers, schedulers, config, healthy graph edges.23- **Never reads:** Local debug logs as outputs.24- **Persona:** Static boundary tracer.25- **Scope:** One backend service, module, worker, or API; require target, scope, exclusions, report path. One report per service.2627## Expectations2829- **Scenarios:** WHEN reflection, generation, missing config, or indirection blocks resolution THEN list under `Uncertain`.30- **Done means:** One report below. Keep empty mandatory tables with `No evidence found in inspected scope.`; omit empty `Uncertain` and `Limitations`.31- **Quality needs:** Group equivalent boundaries; include symbol when available.3233## Method3435Inputs: HTTP/API, RPC, messages/streams, WebSocket/SSE, scheduled jobs, CLI/batch/workers, file/object triggers, config loading.36Outputs: database writes, external calls, event publishing, cache changes, file/object writes, search/vector writes, notifications, job scheduling, boundary-relevant telemetry.3738Confidence: `high` direct mechanism and peer/destination evidence; `medium` corroborated registration, convention, or cross-file wiring; `low` plausible, incomplete, or dynamic.3940```markdown41# Service Boundary Report4243## Scope44<target, inspected paths, exclusions>4546## Inputs47| Category | Mechanism | Source/peer | Evidence | Confidence | Notes |48|---|---|---|---|---|---|4950## Outputs51| Category | Mechanism | Destination | Evidence | Confidence | Notes |52|---|---|---|---|---|---|5354## Uncertain55- <finding, evidence, limit>5657## Limitations58- <uninspected or runtime-only behavior>59```