Domain surface · synthetic · client-mimic sandbox

From robot event to completed human-approved workflow

LensDNA executes the browser, phone, documentation, coordination, and evidence work that remains after an education or therapy robot creates an event. This surface demonstrates one narrow residual loop — not a general learning platform, avatar product, or robot-control system.

Trust boundary: Synthetic demonstration only. No real student, patient, teacher, therapist, or family data. No endorsement, partnership, integration, or customer relationship with any named robotics or education provider is claimed or implied. LensDNA does not make educational or clinical determinations. Irreversible actions require explicit human approval.

What the residual layer does

Robots and intelligent education platforms can create presence, interaction, instruction, observation, and events. They often leave fragmented operational work: portal entry, staff notification, family coordination, support tickets, case notes, escalation, scheduling, evidence, and audit records.

Receive the robot/avatar event and preserve case context
Classify the operational follow-up required
Navigate the relevant synthetic portal or support surface
Stage fields, notifications, and evidence packets
Pause before any external communication or irreversible log
Present the complete action set for human review
Record approved / rejected / amended actions + audit trail

Start synthetic event → Reset session

Primary demonstration (synthetic)

Event: Companion-3 (fictional therapy support robot) completes a scheduled social-emotional check-in with student “Jordan Lee” (synthetic) in Room 14B, Cascadia Learning Academy (fictional district). Engagement drops below threshold; sensory-overload protocol flags residual work.

Residual still required: open district support portal → log observation + attach evidence → draft teacher + SPED notification → stage caregiver update → human gate before any external send or irreversible action → produce Residual Evidence Artifact (REA).

All names, identifiers, organisations, and outcomes are fictional. No live systems are contacted.

Capabilities made visible

Voice interaction & telephony path
Optic / screen interpretation notes
DOM extraction + deterministic field control
Synthetic portal navigation
Continuous case context

Staged actions (not uncontrolled automation)
Human approval before irreversible steps
Action status: proposed → staged → approved
Audit provenance + dossier generation
Zero-retention / synthetic boundary stated

Install pattern (identical to production client)

<script
  src="https://lensdna.app/embed.js"
  data-overlay-url="https://lensdna.app/overlay.html"
  data-tenant-id="sensorlens-sandbox"
  data-theme="dark"
  data-position="bottom-right">
</script>

Overlay controls only the origin that embeds it. This surface uses the same production embed path clients use.

Reusable runtime · other domains

The same client-side runtime is intended for HealthAdminDNA residual, Deploy Robotics care-setting events, PropTech, industrial claims/permitting, and critical-minerals intelligence. Domain pages define event types, workflow steps, approval rules, synthetic portals, terminology, evidence requirements, and pilot metrics. The execution kernel stays domain-agnostic.

← SensorLens residual practice (health-shaped)