Technical evidence records

This dated Visitt and Visitt+ supplement contains 1,668 records: 125 findings, 848 client API variants/documents, 120 selected routes, 20 client-selected model families, 67 selected native-function metadata records, and 488 provenance records. Counts describe extraction inventory, not shipped features or full backend coverage.

Source snapshots: October 11–12, 2026. Publication: October 13, 2026. Static implementation evidence does not establish authenticated behavior, server authorization, delivery, payment or accounting outcomes. Visitt+ remains a separate app label within the Visitt company namespace.

• Team brief and demo comparisons
• Full technical dossier
• All records as JSONL
• All records as JSON
• Canonical sources
• Exact workflow links
• Manifest, verification scope and checksums

The website record browser provides search, family filters, stable links and individual JSON downloads. Source URNs identify withheld artifacts, not public downloads. Original binaries, full source mirrors, native code dumps, credentials and test account identifiers are excluded.

With the read-only MCP at https://crefieldnotes.com/mcp, use list_research with kind technical_finding or technical_catalogue; search_research accepts those same kinds. get_record retrieves the full record. Choose format: "json" to paginate complete metadata and source coordinates; concatenate the returned text slices in next_offset order before parsing JSON. get_related_evidence retrieves exact workflow and provenance links. get_document paginates the brief and dossier as Markdown.

Start with visitt-rea:finding:cw09 for amenity conflicts, visitt-rea:finding:cw10 for charge verification and sync, or visitt-rea:model:visitt:issue for a larger model catalogue entry. Retrieval does not make backend calls to a competitor or incur collection/analysis charges.

For product answers, retain the existing workflow's review status. Linked implementation observations supplement it; they do not turn an outline into a verified end-to-end flow. Ask the caller to verify private PRISM behavior through their own authorized product context.