Rules and the report

Let a project fill itself, then see how it was read.

guide~2 minVerified v0.162.2

A project rule with a slug prefix and its matching controls. — The Rule card describes what joins the project.

Your project can gather matching artifacts as they are published.

Fill a project with weekly updates

Add a rule to <project> that pulls every artifact whose slug starts with weekly-. Keep automatic admission off when the project is shared, and leave private artifacts out unless I opt in. Send me the project and report links.

What the rule finds

A rule can match a slug prefix such as weekly-, text inside a slug or a title, a collection, a kind, a template or a visibility, and sorts what it finds newest first, oldest first or by title. Every filled field must match, and a rule needs at least one. A workspace can have up to 20 rule projects. The rule gathers existing matches and later publishes; From rule marks the items it added. Hand-added items stay separate.

In a shared or public project, new finds wait for the owner unless Admit automatically is on. Held finds tell the owner by email, at most once a day per project. In those projects, private matches are skipped unless Include private artifacts is on; a project only you can open includes them either way. Admitting them opens them through the project to the people you share with.

The From rule badge on an item added by the project rule. — From rule tells you why an item is here.

The report

The project report with views, readers, responses and the artifacts it counts. — The report belongs to the owner.

The report gathers reading and response counts from the artifacts, plus their fields and recent activity. A source that could not be read is marked, rather than counted as zero.

Check it worked

The Rule card shows the saved match. Matching items carry From rule. The report lists the artifacts and shows their counts; an unread project can have no reading activity yet.

Next: Use a template.