Audiences and shared posts
An audience names who receives something. Its rules can name a person, an
organization, an organization role, a project, or a project role. Matching any
rule includes a person. Org roles carry to every project in the org. A role
rule matches people at or above its rank: owner = admin > operator > viewer.
A higher project grant can raise a person's effective role. Membership follows
current grants: joining a role
reveals open work; leaving it removes that work and the right to answer it.
An audience grants no action by itself. Decision requests keep their own
approval policy: any needs one answer; all needs an answer for each addressed
role or person. Operator questions keep their own answers and history.
Named audiences can be reused within their owning project. Inline audiences belong to one use and stay out of named lists. List or create a named audience:
yoke audiences list --project-id 10
yoke audiences create --project-id 10 --name Reviewers --rules '[{"scope_kind":"project","scope_id":10,"role_name":"owner"}]'
A post is durable shared work addressed to an audience. Its title, body,
source label and optional key/value fields appear under Posts in the web
Inbox and in yoke inbox list. It does not expire. Posting requires the
project's items.write permission; being addressed does not grant that
permission. Current audience members with project read access can mark it
Done for everyone. The record keeps the first person's name and time;
repeating Done reports that same completion.
yoke inbox posts create --project-id 10 --title 'Review this request' --body 'Details to review' --source 'External form' --audience-name Reviewers
yoke inbox posts done 7
Other systems use the typed functions audiences.create, audiences.list,
inbox.posts.create and inbox.posts.done. Unknown or empty audiences and
missing posting permission refuse with a named reason and a recovery step.
Audience definitions and posts may have no members today; future role members still
see its open posts. Questions, approvals and QA gates refuse
empty_audience_members when nobody can answer: use --to <person>, choose
--audience <name> with reachable people, or grant someone a project role. Fleet messages remain individual deliveries with a 24-hour
expiry. Delivery notices report results and use Dismiss; posts ask for
shared work and use Done.
Related
Address an operator question
Use yoke decision-requests ask --to PERSON (repeat for each actor id or unique
human name) or --audience NAME to replace the default project owner/operator
audience. Only members can answer; named audiences retain live membership.
Use --project PROJECT for a visible project, or --item ITEM to use its project
without holding the item. Without either, an addressed question has no project:
it belongs to the one organization shared by asker and recipients, or the named
audience's organization. Ambiguous organizations refuse; choose a named audience.
A named audience must be owned by that project or organization and have rules.
Without explicit recipients, the session project and its owner/operator roles
remain the defaults; a project-less question requires --to or --audience.
See operator questions for filing and answers.