0pt.structure.* registered 5 of ADR-027's 7 areas yesterday (cl0ud
PR#270, grounded at this repo's main@ec48774): entity resolution,
lineage, quality (x4) and parsing-orchestration. routing and
normalization were left out because this repo's own contract had no
operationId/path for either yet, even though both have real,
INTEGRATION_TESTED code in sax3l/0pt-motor
(motor/parsing/routing.py, motor/normalization/{amounts,identifiers}.py)
that is simply not deployed behind an HTTP route.
Adds the two target-status operationIds, following the exact pattern
of 0pt.resolve_entities / 0pt.get_provenance already in this file
(TARGET summary prefix, x-siax-status: target, security: [], dedicated
request/response schemas):
- POST /v1/0pt/parsing/route -> 0pt.route_parsing
(BTI-DOC-02/03/04/05 parser-routing / selective-OCR decision)
- POST /v1/0pt/normalize -> 0pt.normalize_value
(BTI-NLP-02/03 amount/percent/date normalization + identifier
checksum validation, one operationId per ADR-027's "normalization"
being a single area)
Contract-only change; no route handler exists yet (correctly reflected
by x-siax-status: target). Registering these in cl0ud's capability
registry is deliberately deferred to a follow-up PR in that repo.
projections is NOT touched here -- no code exists anywhere for it, so
it stays unregistered rather than becoming an empty stub.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
adminandClaude Sonnet 5