CAIOS x CARLI Home Pet Agent

What it does

CAIOS x CARLI Home Pet Agent turns Alexa+ into a safe ambient interface for longitudinal companion care. Instead of generic voice chat, CARLI retrieves bounded pet context, prepares a proposed care action, requires explicit owner approval for any mutating action, executes only the exact approved payload, and records the resulting observation/outcome back into the CAIOS event model.

The judge flow uses synthetic Pika data. An owner reports that Pika did not finish dinner. CARLI prepares the observation locally without writing anything. Only after the owner selects Approve & Record does the server issue a short-lived confirmation token bound to the exact payload and invoke the MCP record_observation tool.

Alexa+ / MCP implementation

The project implements a self-hosted MCP surface aligned to spec 2025-11-25 and Streamable HTTP. It supports initialize, tools/list, and tools/call and exposes six tools: get_pet_context, get_today_summary, get_recent_changes, record_observation, create_follow_up, and generate_health_story.

Read tools cannot mutate state. Write tools require payload-bound confirmation. The simulated Alexa+ web experience calls the same MCP gateway used by the agent, so the demo is not a separate fake UI path.

AWS Builder integration

CARLI uses a CAIOS-owned AgentRuntime interface so the product is not coupled directly to one model vendor. The submission includes a deterministic degraded-mode runtime for safe local fallback; an AgentCore HTTP runtime adapter with HTTPS-only endpoint handling, bounded timeout, and fail-closed non-2xx behavior; a deployment-ready TypeScript AgentCore service slice using Strands Agents SDK and Amazon Bedrock; and bounded context only, so AWS reasoning never receives unrestricted CAIOS persistence access.

A real Amazon Bedrock AgentCore Runtime proof is documented in the public repository: the runtime is READY, negotiates MCP 2025-11-25, exposes the six CAIOS tools, and successfully completed a read-only get_pet_context invocation for synthetic Pika data. The separate Strands/Bedrock TypeScript sidecar is not claimed as independently deployed unless additional deployment evidence is added.

Canonical write-back

Approved care outcomes are projected into the existing CAIOS PetEvent(OBSERVATION) contract instead of inventing a hackathon-only CARE enum. The mapping preserves source, provenance, runtime provider/model, owner-approval state, and an idempotency key (carli:).

Safety and privacy

• Synthetic Pika data only in the public submission.
• Non-diagnostic: CARLI does not diagnose, prescribe, or replace veterinary judgment.
• Consequential writes require explicit owner confirmation.
• CAIOS remains the canonical companion record; the LLM/runtime does not.
• No production credentials, owner PII, private veterinary records, or proprietary retrieval/scoring logic are included.

What was significantly updated during the hackathon window

CAIOS existed before August 31, 2026. The Amazon AppDev work is a significant new execution layer: the Alexa+/MCP tool surface, Streamable HTTP gateway, synthetic Pika context provider, confirmation-bound ActionGuard, guarded mutation store, CARLI runtime abstraction, AgentCore/Strands/Bedrock service slice, canonical care write-back mapping, judge simulator, automated tests, friction log, prior-work disclosure, and public-repository extraction boundary.

This converts CAIOS from a primarily web-based longitudinal pet intelligence system into an ambient, agent-compatible care workflow while preserving deterministic safety and canonical data ownership.

Built With

• alexa+
• amazon-bedrock
• amazon-bedrock-agentcore
• mcp
• next.js
• playwright
• strands-agents-sdk
• streamable-http
• typescript
• vitest
• zod