Home

Home is the entry pane. It collects the surfaces you orient on at the start of a session — the domains you’ve declared, the items you’ve pinned, the documents you share across your fleet, the federated chats you participate in, and the day’s rollup. Nothing on Home runs work; everything on Home tells you what is there.

What You See

The pane is a stacked column of sections, each scoped to one substrate area:

Section	What It Shows
Domains	The list of domain slugs you’ve declared (e.g. family, work, home, property-sandy-bay). Domains are the user-curated routing vocabulary that scopes pins, filters messages, and gates skills. Empty by default; the platform never invents domains.
Pins	Items you’ve pinned to keep visible — a memory, a skill, a recent DispatchRun, a card. Each pin is typed (memory / skill / dispatch-run / card etc.) and shows enough identity to be useful at a glance.
Pads	Collaborative documents shared across your fleet. Pads require a configured transport in Fabric settings; without one, this section is empty.
Federated Chats	Inter-device or inter-fabric chat channels you’ve joined. Also requires a configured transport in Fabric settings.
Today	The day’s rollup card — captures count, digest status. A summary surface; the full Today pane lives one level down at Today.

Each section shows an empty state honestly if nothing is configured or present. Home does not invent content to fill its sections.

Domains

Domains are short slugs the user owns. They are the routing vocabulary the platform uses to filter pins, scope skills, route messages, and bind capability declarations. Examples: family, work, home, property-sandy-bay, trustee-corporate, school-education.

Why declare them at all? Because once a domain exists, the platform can apply it as a filter — a pin tagged work only surfaces in work-scoped views; a skill that requires family consent only runs when the caller bears that scope. Domains are how partitioning becomes useful instead of theoretical.

The Domains section on Home shows the current list and offers an Add domain affordance. See Domains for the full domain surface and Scope and ACL for the substrate behind it.

Pins

Pins are user-elected items kept visible on Home. Pinning is the user’s way of saying “I want this on hand without searching for it”. Pin types include:

Pin type	What It Anchors
Memory	A specific memory record — an observation, a precedent, a decision the platform should hold close.
Skill	A named skill the user invokes often.
DispatchRun	A specific run (success, failure, or in-progress) the user wants to track.
Card	A vault note representing a person, organisation, project, or other persistent entity.

A pin is not a side effect of work — it’s an explicit choice. Pinning a failed DispatchRun, for instance, keeps the failure visible so the user can decide whether to retry, dig in, or write it off. See Pin for the substrate definition.

Pads And Federated Chats

Pads and federated chats are fabric surfaces — they live on the cross-machine substrate that lets one user’s instance reach across their own devices. Both require a configured transport before they’re usable. The Home sections for pads and federated chats render empty (with a Fabric Settings jump link) until that transport is configured.

• Pads — collaborative documents synced across the user’s fleet. Useful when the user wants the same document open on multiple devices and edits to flow between them.
• Federated chats — chat channels that span devices (within the user’s own fabric) or across fabrics (when federation ships). The Home section shows joined channels; the channel UI itself lives elsewhere.

See Fabric for transport configuration and Cross-machine for the substrate picture.

The Today Rollup

The Today section on Home is a rollup — a compact summary card showing the day’s status: captures count, whether a digest is available, whether there are recommendations pending. It’s a pointer, not a full surface. Click through (or open the Today pane directly) for the full day-level view.

The rollup deliberately stays small on Home so that the pane’s purpose — orientation — isn’t overtaken by the day’s noise. See Today for the full pane.

When Home Is Empty

A new Stallari has an empty Home: no domains declared, no pins, no pads, no federated chats, no digest yet. This is the platform’s honest opening state — the user has not yet done anything for the platform to surface.

The path to filling Home is: declare a domain or two (Domains section’s Add domain), let the platform run a digest workflow (Today pane), pin one or two items as you start using them. Nothing else is required.

Related concepts

• Domains — the full Domains surface
• Today — the day-level pane Home rolls up into
• Fabric — transport configuration for pads and federated chats
• Scope and ACL — what declaring a domain enables substrate-side
• Cross-machine — the substrate behind pads + federated chats