API overview
Checked-in contracts and handlers exist for the listed scope; public integration management and specialist APIs are incomplete.
Generated references describe checked-in wire contracts, not deployment or implementation completeness. The source contract and its handler/tests must agree before an operation is considered available.
| Surface | Status | Current boundary | Reference |
|---|---|---|---|
| Platform | Partial | Go workspace API plus Next server routes; Next repositories still access product PostgreSQL | Platform API |
| Legal Public | Partial | Preview facade with configured clients and in-memory quotas | Legal Public API |
| Legal Private | Implemented for listed operations | Workload-authenticated search and pinned corpus reads | Legal Core API |
packages/contracts/openapi/ owns wire shapes. services/product-api/internal/httpapi, services/public-legal-api/cmd/server and services/legal-core-api/internal/handlers own the corresponding Go transports. The live public-gateway and platform-search Hermit suites exercise the legal boundaries through HTTP.
Contract changes
Section titled “Contract changes”Edit contract sources, run pnpm contracts:generate, then run drift and handler tests. Generated files are overwritten on regeneration, so manual edits are not durable. .github/workflows/ci.yml checks generation drift and OpenAPI lint.
New operations need reviewed methods, resource semantics, authorization and error behavior before entering the contract. Specialist legal capabilities such as LEX, FORUM, valuation and citation analytics are not in the published contract and cannot be called through these APIs.
External integrations owns the preview/public and target MCP distinction. Services & ownership records the actual process boundaries.