A shared understanding

A little care.
Clear expectations.

One person checks in. Their family sees the reply and knows whose turn it is to follow up.

Kin is for everyday coordination, not emergency monitoring, diagnosis, or medical advice.

Go to your circleWhat you need firstJudges: start here

For judges and reviewers

One care loop. No Kin sign-in.

Try the isolated local story on your computer. It uses real Streamable HTTP MCP calls and shared application state, with synthetic people, clock and notifications. It does not require a Kin account, AWS credentials, an Echo, a microphone or phone permissions.

  1. Open Kin’s source repository and check out the submitted revision. Repository access is required; if it is still private, use the access arranged with your submission. Use Node 22.23.2, as pinned in the repository.
  2. In the project folder, run:
    npm ci --ignore-scripts --no-audit --fund=false
    npm run build
    npm run demo:story
    Keep the terminal running and open http://127.0.0.1:3030/story.html on that same computer. This is a local address, not a hosted online demo. Do not enable the optional model or dictation modes for this credential-free path.
  3. Choose Not yet, review and confirm. Advance the synthetic clock to 9:31 AM, then acknowledge Theo’s follow-up. The check-in stays incomplete. Draft Done, review and confirm, then inspect the weekly evidence and MCP trace.

This local demonstration uses synthetic people and an accelerated clock. Its notifications stay in the demo; no phone message is sent. MCP calls and state changes are real. The separate Echo demonstration uses a classic Alexa development skill—not native Alexa+ toolkit integration. Restart the local process to reset the story; never seed or sweep the live family to reset a demo.

The family workspace stays private. No public password or judge bypass is provided. If dedicated live access is separately arranged, use only the credentials supplied in your private judging instructions. Never use the owner’s account. See docs/testing-instructions.md in the source repository for the full guide.

Start with one small check-in.

  1. Agree on the plan. A caregiver adds an everyday check-in in Plan, then chooses coverage in Turns. Choose something together, such as an afternoon walk.
  2. Reply in your own time. Open Ask Kin, or use your linked Echo. Say or choose Done, Not yet, or Skip. Review the proposed change before confirming.
  3. Catch up without chasing. The family sees the response in Today. If a follow-up is listed, the caregiver can acknowledge it separately from completing the check-in.

Before you start

Check your setup.

You need an existing Kin account and accepted access to the family circle. A roster name alone does not give someone access. If you have an invitation code, sign in to Kin and choose Review invitation. If you don’t have an account yet, ask your organizer to arrange account setup before creating your code.

Phone alerts are off unless delivery is enabled. They also need a connected, consented phone. Assigning a turn is not enough; check Today directly until phone delivery is verified.

Using an Echo? On a configured, account-linked test device, say “Alexa, open kin family.” Kin’s web conversation uses real MCP calls; the Echo uses a separate classic development skill, not native Alexa+ toolkit integration or a published skill.

Open your family workspace

Clear expectations

The details, when you need them.

A check-in is someone’s response.

Done, Not yet, and Skip record what a person tells Kin. They are not independent proof that care happened. Not yet keeps the task open and starts a fresh grace period from the later of the due time or the reply.

A name identifies the account used.

Shared history records the signed-in Kin account, not a verified human speaker. Anyone using a linked Echo may be able to report through that account. Kin does not recognize which person spoke. Link only the intended account, explain this to everyone using the device, and disconnect it when access should end.

One person takes the next turn.

A duty assignment identifies the caregiver responsible for new follow-ups. A handoff does not redirect an alert already queued. Next-week proposals preserve existing assignments and fill uncovered days by fewest assigned days, then longest since the previous turn.

These counts describe scheduled responsibility, not time spent caring or anyone’s contribution to the family.

Routing, sending, and acknowledgment are different.

Phone alerts require a consented destination and enabled delivery. A provider-accepted message is not proof that a phone received it. Delivery can fail, and uncertain retries can produce duplicates. Acknowledgment records that a caregiver has seen the follow-up. It does not mean they contacted the parent, and it does not complete the check-in or cancel a message in progress.

Kin’s notification text omits care details. Open the authenticated workspace for the shared update. Device notification previews are controlled by your phone settings.

The weekly notes stay close to the evidence.

Every observation links to a recorded event. When enabled, Amazon Bedrock selects from those facts; Kin validates its selections and supplies the wording. If generation fails, the factual summary remains available. Response timing uses recorded provider acceptance, not handset delivery, and missing timing is labeled.

Access belongs to people, not roster names.

Adding a person to Circle does not create their account, invite them, or subscribe a phone. An invitation is tied to a verified account and requires that person’s acceptance. Closing a workspace session does not revoke membership. Organizers can review eligible memberships in Access.

Two ways to use your voice.

Kin’s web conversation calls the MCP server directly; it is not Amazon’s Alexa+ interface. Kin also has a separate classic Alexa development skill for linked test Echo devices. This is not native Alexa+ toolkit integration or a published skill available to everyone.

On a configured Echo, say “Alexa, open kin family.” Your Kin account must be linked before the skill can read the family plan. Check-ins and reminders require confirmation.

With your reminder-sync consent and synchronization enabled, Kin attempts to cancel its own reminders when their check-ins no longer need them. Cancellation is not guaranteed: check the Alexa app if Kin reports an uncertain result. Moving a check-in does not move its reminder or create another one; a new reminder needs fresh consent.

Optional browser dictation starts only on request, may use the browser’s speech provider, and fills a draft for review.

Kin records replies and responsibility. It does not verify anyone’s safety.