Skip to content

docs: research Vision page inspection APIs - #19

Merged
privatenumber merged 3 commits into
developfrom
docs/vision-page-inspection-research
Aug 11, 2026
Merged

privatenumber merged 3 commits into
developfrom
docs/vision-page-inspection-research

Conversation

@privatenumber

Copy link
Copy Markdown
Owner

Summary

  • Adds source-backed research for Vision's horizon, document-segmentation, and image-feature-print APIs
  • Records macOS 26.5.2 characterization results alongside the API contracts
  • No user-visible behavior change; gives a future page-inspection feature a safe evidence boundary

Problem

Vision exposes geometry and similarity evidence, not semantic page decisions. A future implementation could read a document boundary's topLeft label as reading orientation, or treat a small feature-print distance as a duplicate verdict.

For example, a generated invoice whose number changed from 1048 to 1049 had a feature-print distance of 0.014, and a 180-degree-rotated page produced the same detected boundary corners. Treating either result as an automatic action could rotate, skip, or delete a distinct page.

Changes

Adds one note for each request, covering availability, legacy and modern APIs, result shape, limits, source links, and follow-up characterization. The notes record the raw local measurements with their Xcode, SDK, macOS, architecture, revision, and crop-mode context.

The documented adoption boundary is inspection-only: future commands can report raw horizon, document-boundary, or similarity evidence, but need a separate product decision and behavior coverage before changing OCR, document recognition, or searchable-PDF behavior.

@privatenumber
privatenumber merged commit 708f36f into develop Aug 11, 2026
2 checks passed
@privatenumber
privatenumber deleted the docs/vision-page-inspection-research branch August 11, 2026 01:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant