Skip to main content

​
Source API contracts

  • /health and /api/health: application identity, process uptime, ports and sample radar counters.
  • /api/radar/status: static target records plus a time-derived sweep angle.
  • /api/radar/scan: a fixed success response without a target request or visual-test execution.
  • /api/pipelines: a static synthesis-pipeline demonstration array.
  • /api/synthesis-jobs: a static synthesis-job demonstration array.
  • /api/models: static model declarations.
  • /api/brand/manifest: the checked-in asset manifest when present.
The handlers branch on request path. Their target status, latency, regression rate, parity percentage and job status are demonstration fields rather than measured execution results. The scan response alone cannot establish that any property was verified.

​
Google and Eyedbase

The selected owner is techtradepro23@gmail.com. The project is eyemech-production; the planned Google callback is the production Eyedbase google-eyemech broker endpoint. Google configuration, issued credentials, broker hydration, the product OIDC consumer and tenant authorization are separate acceptance steps. Retain credentials in infrastructure’s approved authority, never in public documentation or browser code.

​
Synthesis and visual acceptance

Actual synthesis requires a source-bound inference execution and its generated artifact. Visual verification requires the canonical EyeParity flow and proof custody. A static job record, displayed hash fragment or perfect parity percentage does not replace those results. Fleetboots owns execution and Mechscrum owns workplans and orchestration.

​
Documentation delivery

The assigned Mintlify project is eyemech, owned by the same primary app owner. Desired binding is canonical GitLab project 116, branch master, content root mintlify. Existing hosted starter presence is separate from source-backed content publication, custom-domain verification and automatic synchronization.