L’Ayalga — From invitation to arrival

Two hosts share a rural home, but invitations arrive as informal messages and overlapping stays need more judgment than a normal calendar can provide. L’Ayalga turns each message into a private guest link, finds safe dates and guest-visible rooms, confirms exact room choices, follows up before arrival, and asks a host only when a social exception needs a human decision. The calendar is the result of that coordination, not the product.

Documentation

The documentation index lists every current document. The host and guest manuals describe complete journeys; the roadmap separates released work from the remaining steps. L’Ayalga began as an AWS Agents for Humans hackathon entry; the hackathon archive keeps the submission material, which describes the judged demo as of 2026-10-14.

Production runs v2.3.0 with the Next.js 16.4.2 security hotfix (2026-10-22) at commit 339b62a9370dd097b0ca929176bff24c0f424b5a, with AgentCore runtime version 42 from v2.3.0. Demo mode is gone: hosts sign in with Google (the header shows which account is signed in, and Google always offers its account picker), invited guests can sign in with the Google account that claimed their invitation, and the household starts with no rooms. The release passed the production probe gate on fixture households. Human time savings have not been measured; guest-email activation and real-recipient delivery proof remain separate work.

Release preparation: v2.3.1 contains the reliability fixes in CHANGELOG.md, with no migrations. Production promotion and matching AgentCore deployment are pending release verification.

The household

L’Ayalga serves one real household with two hosts, Juan González and Jordan Lynn. Home 00000000-0000-4000-8000-000000000001 was the synthetic demo home during the hackathon. The real-use conversion migration keeps the home, both hosts and their sign-in claims, and deletes the synthetic guests, invitations, rooms and demo clock. The hosts then add the real rooms in the room ledger.

Hosts sign in with Google. A Google account can sign in only when a host_identity_claims row maps its email to a host of the household; any other account sees "This Google account is not on the host list for this house." and is signed out. There is no self-service sign-up. The host manual explains how to add a host. Guests do not need an account: each guest uses a private invitation link, and can optionally sign in with Google to claim the invitation.

How it works

The architecture source shows the web and agent boundaries. Next.js accepts work into a durable PostgreSQL queue. The selected runtime architecture dispatches to Amazon Bedrock AgentCore Runtime. The repository model configuration selects Claude Sonnet 4.6; the release must verify the deployed model and matching IAM allowlist. Tests use a scripted model through the same agent factory, hooks and storage; production refuses MODEL=scripted, and the AgentCore bundle does not include it. Executed agent completions record executedOn; retired cancellation work instead records its cancellation outcome. Vercel Cron recovers leases, drains queued runs and runs due follow-up jobs; PostgreSQL remains authoritative.

This is the beginning of the README. Read the rest at the original. Read the full README ↗