Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt

Use this file to discover all available pages before exploring further.

May 8, 2026 Documentation update Review recommended

​
Affects

Teams using the public Matcher documentation to implement, review, or maintain integrations. This update applies to the public documentation portal. It does not change the runtime API behavior.
The public documentation portal is the customer-facing reference. Repository source files should not be treated as integration artifacts or downloaded API specifications for client use.

​
What changed

​
Fee-rule routes

The public API reference now shows the real Matcher fee-rule routes. Five fee-rule endpoints were previously documented under a phantom /v1/config/... prefix. The documentation portal now points to the working /v1/contexts/... and /v1/fee-rules/... routes.

​
Schema and field names

The reference now follows the Go DTOs and JSON tags used by the released v2.1.1 binary. Key cleanup:
  • 36 field names moved from snake_case to camelCase.
  • 9 schemas were renamed to canonical Go names.
  • Input schemas were renamed to Request where that matches the Go convention.
  • $ref links and required arrays were updated.

​
Removed phantom wrappers

The documentation no longer shows wrappers or duplicate schemas that the API does not return. For example, AdjustmentResponse now shows the fields inline instead of a non-existent adjustment wrapper. CloneContextResponse now points to the canonical reconciliation context schema and uses feeRulesCloned.

​
Missing fields and schemas

Fields and schemas present in the Go DTOs were added to the documentation portal, including audit log fields, extraction request bridge fields, variance report fields, and export helper schemas.

​
Impact

This is a documentation update. It reduces drift between the public reference and the released Matcher API. If your integration already works, no migration is required from this release note alone. If you use the documentation to generate examples, review routes, or check field names, use the updated documentation portal.

​
What you need to do

1
Review Matcher fee-rule routes before your next integration change.
2
Use the updated field and schema names when reading the public documentation.
3
Do not treat repository source files as client integration artifacts. Use the documentation portal as the customer-facing reference.

​
Deadline

None.

​
Why

The previous reference mixed real Matcher behavior with stale routes, duplicate schemas, and fields that did not match the released DTOs. The new version is clearer and harder to misread.

​
Resources