Keelya

Scripted observation · Fictional lives

Follow a labelled walkthrough of join and isolation

These lives are fictional. They are sample fixtures, not anonymized customers and not a hosted Keelya instance.

This page is a scripted observation you can read without JavaScript. It is not a live demonstration assistant, not a seeded Attention Plate, and not a trial signup. The isolated hosted demonstration path is separate and cannot be promoted from this walkthrough.

The two stories come from landed Companions fixtures: a multi-producer join, and cross-context isolation. Outbound send, real mail, real SMS, and real money stay stubbed. This story cannot be promoted into a customer instance.

What you are not looking at

  • Not a live assistant and not a customer account.
  • Not a seeded plate of invented obligations presented as the product.
  • Not a Platform workspace, tenant, or demo runtime.
  • Not a path that turns this story into your instance.

COMP-7 multi-producer join

One night out becomes one plate case

Join is one matter. A confirmation number for one night out arrives through more than one channel. Attention joins those producers into a single plate case. You are not asked to reconcile a sibling task, bill, briefing, and calendar event.

  1. A confirmation number appears on one channel

    In the fictional life, a booking for one night out produces a confirmation number on a first channel — the kind of message a venue or ticket service would send.

  2. The same night out appears on a second channel

    The same confirmation number shows up again on another channel. Two producers, one night out — not two evenings, and not a new obligation invented by the assistant.

  3. Attention joins them into one case

    The Attention capability joins those producers. What lands on the plate is one case for that night out. The Personal Assistant product presents that one case. It does not mint a second plate.

If the story instead handed you a task, a bill, a briefing, and a calendar event to file yourself, that would be a fork — not the join fixture. This walkthrough shows one matter.

COMP-7 cross-context isolation

personal and job stay isolated

Isolation uses two suite life-context labels — personal and job — inside one customer workspace. These are not Platform workspaces or tenants. Contacts and outbound send stay with their label. A cross-context action still Asks.

  1. Two suite labels, one workspace

    The fictional life carries the suite labels personal and job. Companions owns that label-plus-isolation contract. Keelya names the contexts; it does not invent a second schema.

  2. Contacts stay with their label

    A job contact belongs to job. A personal contact belongs to personal. The address book does not blend them because the assistant “knows” both people.

  3. Outbound send stays with its label

    Send from personal uses the personal identity. Send from job uses the job identity. In this story, outbound send is stubbed — no real mail, SMS, or money moves.

  4. Crossing the boundary still Asks

    If you ask the assistant to tell a job contact something while acting in personal, it Asks. It does not disclose or send across contexts on its own.

A Platform workspace would be a different isolation story — tenant versus tenant. This fixture is two suite labels on one fictional life.

What this walkthrough does not claim

This is current evidence for a labelled fictional walkthrough only. It does not complete a public interactive hosted-assistant experience.

Demo state cannot become a customer instance. Export from a demonstration, when that exists, stays fictional and labelled.

Unsigned future capabilities — such as Study or bookkeeping — are not part of this walkthrough and are not offered as live specialists.

Current surfaces remain Keelya web and owner chat. A consumer mobile application is deferred. iMessage is not supported.