Conversation
Natural voice and text interaction.
THE COMPLETE ORB WEAVER PIPELINE
SCAN. COMPILE. DEPLOY.
THEN GUIDE.
ORB Weaver first turns the website into verified, structured intelligence. The Website ORB then turns that intelligence into natural conversation, spatial guidance, permissioned action, and verified outcomes.
STAGE 01 — SCAN
220+ scan types. Fourteen intelligence categories.
ORB Weaver discovers the public website—or the authenticated owner section when explicitly included—and inspects structure, content, controls, workflows, documents, layout, accessibility, brand, schema, and change state.
- Route and subdomain discovery
- Page purpose and content extraction
- Menus, buttons, CTAs, forms, modals, tabs, and dialogs
- DOM anchors, ARIA labels, bounding boxes, and screen positions
- Login, signup, purchase, checkout, booking, lead, and support flows
- Tesseract Weave for images, PDFs, and Office documents
- LiDAR Weave for DOM occupancy and movement guidance
STAGE 02 — COMPILE
Evidence becomes a Site World.
Raw findings are normalized, deduplicated, cross-referenced, timestamped, versioned, and confidence-scored.
- Structured knowledge graph
- Verified pointer manifest
- Route capsule set
- Workflow and funnel maps
- Catalogs and price references
- A priori knowledge vault
- Deployment configuration
STAGE 03 — DEPLOY
The ORB begins informed.
The completed intelligence package is delivered to the Website ORB as a structured deployment artifact. The assistant receives the website’s world immediately—without bespoke hard-coding and without relearning the site during every visitor session.
THE VISITOR OPERATING SEQUENCE
UNDERSTAND → LOCATE → GUIDE → ASK → ACT → VERIFY
01 — UNDERSTAND
Weaver identifies the visitor’s intent.
Visitors can speak naturally instead of translating their goal into menu labels, search terms, or whatever mysterious phrase the website designer used three redesigns ago.
Weaver interprets the request in the context of:
- The current page
- The visitor’s journey
- The available website pathways
- Relevant products, services, documents, and controls
02 — LOCATE
Weaver identifies the verified destination.
He connects the visitor’s goal to the correct page, section, form, button, product, document, or process.
No invented links.
No vague guesses.
No ritual clicking through twelve browser tabs while hope slowly leaves the body.
03 — GUIDE
Weaver directs attention to a verified live target.
Using awareness of the rendered page, current target geometry, and the Ping Light, Weaver can travel to the applicable element and visibly Point/Ping it.
If the browser resizes or the page reflows during travel, the system can refresh the geometry. If the target disappears, it can refuse the stale Point/Ping instead of acting on an obsolete coordinate.
04 — ASK
Weaver requests permission before acting.
When an action affects the visitor’s journey, account, choices, or information, Weaver explains what will happen and asks for approval.
The visitor remains informed and in control.
05 — ACT
Weaver completes the approved browser action.
Depending on the experience, Weaver can assist with actions such as:
- Opening the correct destination
- Moving between pages
- Selecting an approved option
- Advancing a guided process
- Assisting with forms
- Supporting bookings, purchases, and account workflows
06 — VERIFY
Weaver confirms the result.
After an action, Weaver checks the outcome and tells the visitor what happened.
The experience does not end with a mysterious click and a cheerful little spinner.
It ends with clarity.
PERSIST AND RECOVER
THE SITE-SPECIFIC ORB STATE SURVIVES THE SESSION.
A manufactured Website ORB package has demonstrated one canonical Vault carrying compiled site knowledge, learned observations, and the provenance or ledger beneath that learned state.
It has also demonstrated restart and recovery using that same canonical persisted state rather than beginning as a blank generic assistant after every restart.
ONE CONNECTED EXPERIENCE
Site understanding
A connected model of the website and its pathways.
Spatial awareness
Knowledge of the current route, viewport, and visible controls.
Permissioned action
Explicit approval before meaningful browser actions.
Controlled memory
Information retained only when the visitor permits it.
Responsive embodiment
A consistent presence across desktop, tablet, and mobile.
SEE WHAT CHANGES WHEN THE WEBSITE CAN PARTICIPATE.