An agent's publication is answered in the window's approval box with whom it is for, picked by digit from the audiences this terminal learns from artifact.list when the request arrives, the agent's proposal picked first and nothing where it named nobody; a team's artifact is shown as the team's wherever a row says whose it is, and troupe artifacts publishes for a team as the team's unless --owner me and hands one on with transfer¶
TUI decision 169 · accepted · 2026-10-28 · issue #62
Root #62's team artifacts: an artifact may be a team's, every member its owner, and when
an agent publishes the person says whom it is for at the approval. The plane's contract is
the root's (the owner_team, may_transfer and role of a row; artifact.publish's
owner; artifact.transfer; approval_requested's publication and
approval.respond's answer); this is how the terminal shows and answers it.
- In the approval box, not a screen of its own. The window's approval box is where a
TUI person answers approvals, and a delegation at the gate is drawn and answered there
(TUI Decision 157), so a publication is too: the
PUBLISH “title” (a page, 3 files)line with the keys, whom the agent proposed it for and whose, its note, then the audiences numbered with the one picked marked. A digit picks,ypublishes for the one picked,ndenies,apublishes and lets the agent go on unasked. Only the digit is new:y/n/akeep their meanings, and digits already pick a question's option in the window. - The audiences come from
artifact.list. The person's teams and profiles are what the plane says of them for artifacts, whichartifact.listanswers (teams,profiles, the organisation), through this computer's daemon as everyartifact.*goes; there is nomethrough the daemon. The server reads it when a publication's request arrives (audience_asked/2), once per request since teams change, and keeps it for the view; where the daemon cannot say (signed out, Local only) the box offers only you, the organisation and what the agent proposed, which is always among the choices. Each team is offered twice, as the team's and as the person's own, since that is the one choice the plane will not change afterwards withoutartifact.transfer. - The proposal is picked first; nobody is nothing. The agent's
visibilityandowner(a team's where it said nothing of a team's) is the choice marked, soyalone sends what the agent meant. Where it named nobody there is no choice,yandaare refused here with "say whom it is for", as the harness refuses an allow without a visibility, andais not offered at all: there is nothing to repeat for the session. - A new version offers no ownership. Whose an artifact is does not change with a
version (the plane refuses a
publishwithidandowner), so for apublicationwithidthe choices carry no owner, each team once, and the answer is the visibility alone. - Headless denies it, as every request with nobody to ask, with a line saying what
the publication is and whom the agent proposed it for; one the agent named nobody for
says
--auto-approvewould not have answered it either.
Governs: clients/tui/lib/troupe/ui/tui/model.ex, clients/tui/lib/troupe/ui/tui/artifacts_page.ex, clients/tui/lib/troupe/client/artifacts.ex