Building rules: use a recipe, customize it, or write your own

The mental model: when this, do that, here

Every rule is three parts:

• Conditions — when a rule applies. "Title contains Practice," "Source is School," "Tag Fan Club is not present." Choose whether an event has to match all of your conditions or any of them, and group conditions for more involved AND/OR logic. A rule with no conditions matches everything in its scope.
• Actions — what happens to a matching event. Rename it, replace just part of the text, prepend an emoji, set its color, exclude it, hide it, add a note, set its duration, or assign a category, person, or tag. A rule can do several at once.
• Applies to — where it runs: the whole workspace, specific calendars (views), or specific sources (feeds).

The fastest path: start from a recipe

Open Workspace → Rules and click Recipes. You'll find a cheat-sheet of common rules, grouped by what they do:

• Rename & clean up titles — turn "B11 Select White - Practice" into "Jack: Soccer Practice", shorten birthday labels, or strip a "(Tentative)" a feed keeps appending.
• Include or exclude events from a view — drop practices, hide all-day clutter, or keep only one category.
• Recolor events — color a whole category, a tag, one person's events, or anything matching a keyword.
• Auto-classify — assign a category, person, or tag to a whole feed, or tag by keyword.
• Annotate — add a standing note or a location hint to a feed's events.

Pick one, and it drops straight into your rules list as an editable, ready-to-run rule. If it does exactly what you need, you're done.

Customize a recipe to fit your feeds

Recipes are starting points, not black boxes. Every one lands fully editable, and each comes with a short "how to customize" note telling you which bits to change. Usually that's one or two fields:

• The keyword or text it matches or replaces — change Practice to Scrimmage, or the feed prefix it strips to match your feed's exact wording.
• The color, emoji, category, person, or tag the action applies.
• The scope under Applies to — narrowing a rename to Specific sources so it only touches the one feed with that quirk, instead of the whole workspace.

Add conditions to make a recipe pickier (match any of several keywords by adding a condition for each), or stack extra actions — a single rule can recolor and add an emoji and tag an event at once.

Write your own from scratch

When no recipe fits, build one directly. In Workspace → Rules, click Add rule and:

1. Name it and add conditions

   Give the rule a name you'll recognize later. Add a condition like Title contains Concert, set match all or match any, and add a second condition if you need to (e.g. Source is School and Tag Fan Club is not present). Leave conditions empty to match every event in the rule's scope.

2. Add the actions

   Choose what happens — rename, replace, prepend/append, set color, exclude, hide, set a note, set duration, or assign a category, person, or tag. Add as many as you want; they run together.

3. Set where it applies, and save

   Under Applies to, choose Whole workspace, Specific calendars, or Specific sources, then save. Scoping a rule to one view keeps your own "All events" calendar complete while a shared view stays curated.

A few things worth knowing

• Order matters. Rules run top to bottom — drag a rule card to reorder. If one rule renames and a later one recolors, both apply in sequence.
• Toggle, don't delete. Disable a rule to see your calendar without it; nothing is lost, and flipping it back on reinstates the effect instantly.
• Rules feed your published calendars too. A rename, emoji, or exclude shows up in the ICS feed your other apps subscribe to — not just inside Tapestry.
• Combine with views. Rules shape how events look; views decide which events appear. Together they're how a noisy pile of feeds becomes a calendar your whole family can follow.

That's the whole engine. Start with a recipe to get a feel for it, then bend it to your household. Open Tapestry, head to Workspace → Rules, and try one.