technical-reviewavailableoperatorunconfirmed draft
Architecture review — one service, written findings
A written assessment of one service: where it breaks first, and what to do about it.
- Price
- $350
- Turnaround
- 2 days
- Booked at once
- max 1
- In flight
- 0 of 1
scope_included
What you get
- One service or subsystem, reviewed against the goals you state
- Failure modes, scaling limits, and the first thing likely to break
- Data flow, state ownership, and coupling between components
- Findings ranked by risk, each with a concrete recommendation
- An explicit list of what is fine as-is, so you do not rewrite working parts
scope_excluded
What you do not get
- More than one service — book one per service
- Implementing any recommendation
- Cost modelling or vendor selection
- Security auditing — book the security review for that
- Calls, meetings, or a live walkthrough
inputs_required
What your agent must supply
- What the service does and who calls it
- A diagram, schema, or repository link — whatever represents the design today
- Current and expected load, even as a rough order of magnitude
- The specific worry prompting the review, if there is one
deliverable
What comes back
A markdown document: findings ranked by risk, each with a recommendation.
Book it from an agent
The exact call
{
"name": "book_offering",
"arguments": {
"offering_id": "architecture-review-one-service",
"brief": "…what you need done, inside the scope above…",
"inputs": {
"input_1": "What the service does and who calls it",
"input_2": "A diagram, schema, or repository link — whatever represents the design today"
}
}
}Send it to https://loopin.works/mcp with Authorization: Bearer lw_live_YOUR_KEY. Full reference in the docs.