Pages an agent publishes, and Materials
Ask an agent for a report and it can hand you a link instead of a wall of text: a real page, served at an address you can send to somebody who has no account here.
Everything a team's agents have made is listed on one screen — Materials — and that is where a page is deleted from.
What the agent does
Two verbs, and no more than two:
| publish a page | it writes the files, it gets back an address |
| update a page | it rewrites them — the address survives, so a link you already sent keeps working |
There is deliberately no third verb:
- No listing an agent can call. A listing is how one conversation reaches a page another conversation made. An agent that wants to change its own page still has the address, in the conversation where it made it.
- No deleting an agent can call. Publishing is undone by ignoring it; deleting is not undone at all, and the person who would want it undone is the one holding the link. Deletion is a person's verb, and only a person's.
- No binary files. The content is text. A picture is a drawing written into the page.
A person has to be in the room
Both verbs are refused unless a real person asked for them in this conversation. A schedule cannot publish, and it cannot rewrite either — a page changing under a reader nobody told is the same defect from the other end.
The reason is sharper than politeness: a team may hold 100 sets, an agent waking every ten minutes would fill that in a day, and every one of them is billed. Materials makes the ceiling clearable; it does not make filling it cheap.
The page already looks like this product
The agent writes meaning; the platform puts the finished stylesheet into the set. That is a decision with a story: the first report an agent published had a violet gradient across the whole screen, emoji for headings and shadows everywhere — and violet appears nowhere in this product. The model was not at fault. It was asked to invent an appearance with nothing to invent it from, so it invented a different one every time.
So: one house stylesheet, added to every set, linked from every page in it. And a page may not colour itself — a stylesheet file, a <style> block or an inline style carrying a colour is refused before anything is stored, and the refusal says to delete it, because the house stylesheet already has an answer for it.
A drawing is the exception, named out loud: a chart has no palette to reach for, so its own fills and strokes are left alone. If a report ever comes out looking wrong again, that is the first place to look.
One thing worth knowing about a served page
It runs sealed: it cannot call out to anything. A page that pulls a chart library off a CDN renders blank, silently. The agent is told this in the tool's own description, because a model that has not been told writes exactly that page — it is what a page on the open web looks like.
Materials — the screen
Workspace rail → Materials (/teams/<team>/artifacts).
| what it lists | everything this team's agents produced, newest first, with the link on each |
| filter | by kind. Only pages are produced today; the other kinds are there so you know where to look the day something makes one |
| the counter | how many of the 100 places the team is holding |
| Delete | the files go, the row goes, and the link goes with them — including for anyone already sent it, and so does the public address if there is one |
| Publish to the world / Revoke the address | the permanent public address — see the section below |
Three things about it that are decisions rather than details:
- Every member may delete, not only an owner or an admin. A page is produced by an agent in a conversation, and the member who was in that conversation is the one who knows the report is wrong or was never meant to leave the room. A rule that lets you make a hundred and delete none is not a safety rule.
- A row with no address is still listed and still deletable. On an installation that cannot serve pages at all, the row says so plainly instead of vanishing — that is exactly the installation where rows used to pile up against the ceiling with no way to see or remove them.
- Another team's id answers as an id that never existed. Not «yours, but forbidden»: otherwise any id becomes a way to ask whether something exists.
Publishing to the world — a person's verb, never the agent's
The link an agent hands out is for the team: it lives 7 days and it is not the address you give a client. That address is a second thing, and it is made on Materials, by a member, with a button called Publish to the world.
| what it is | a permanent address — no expiry, no signature to run out. It names the page, not a file inside it, so the agent can go on updating the page under it |
| who makes it | a member of the team, on Materials. An agent cannot: there is no tool for it, on purpose |
| who may open it | anybody holding the address. It is unlisted — search engines are told not to index it — but not secret: once somebody opens or forwards it, it is out of your hands |
| Revoke | one press, two confirmations, and the address stops opening immediately — for the client too. The record stays, with whether anybody ever opened it |
| sites that may embed it | none, unless you name them. A client's portal can show the page in a frame only if its address is on the list; the list can be changed without changing the address |
Why it is a person's decision and not the agent's: publishing outward is the one act here that cannot be undone. Revoking closes the door, but a page somebody already opened has been seen — which is also why the screen tells you, before you revoke, whether anybody opened it.
What the agent's fate does to a published page: nothing. The page belongs to the team, and the decision to publish was a person's; archiving or deleting the agent that wrote it changes neither. Deleting the material takes the address with it, and so does deleting the team.
Limits, in one table
| files in one set | 200 |
| bytes in one set | 10 MiB |
| sets per team | 100 |
| how long a link lives | 7 days from the moment it was minted; the screen mints a fresh one each time it lists. A published address does not expire; it lives until somebody revokes it |
| sites allowed to embed a published page | 10 |
When the installation cannot serve pages at all
Serving needs an address to serve from, and it has no default. Without it the two verbs are not offered to the agent at all — not offered and then failed at the end, which is what used to happen: the files were stored, the row was written, the team was billed, and only then did it fail on minting the address. None of that could be taken back.
An agent on such an installation says it cannot publish. That is the right answer, and it is better than an address that goes nowhere.
Check it end to end
- In a chat with an agent that can publish, ask for something worth a page: «Собери отчёт по … и опубликуй страницей.»
- The answer carries an address. Open it — the page renders, in this product's colours, on a plain system font.
- Ask the agent to change something on the same page. Open the same address again: the change is there, the address did not move.
- Workspace rail → Materials. The set is listed, newest first, with its file count and its link.
- Delete it. Reload the address from step 2 — it is gone, for you and for anybody you sent it to.
If step 1 comes back saying it cannot publish, the installation has no serving address configured; see the section above.