# Artifacts > Read the quiet hours report, triage what waits for you, and open what your agents published, each as a page of its own. **Artifacts** holds what your agents and quiet hours produced. **Needs you** lists only what waits for your decision: a finding whose fix may have a side effect on the product, and feedback people sent. A finding whose fix only makes the product better is fixed by itself and never waits there; until its fix starts, the line above the list counts it as queued. **Library** keeps everything else - each quiet hours report, and the documents, pictures and recordings your agents published - each on a page of its own. It is a log: nothing there waits for you, so nothing there is dismissed. **Content** holds the posts, announcements and replies Iterada drafted for you to post by hand. **Decisions** keeps what your sessions decided - product decisions, designs, architecture and new features - so you can find why the product is the way it is. Each finding is written as a person using the product would see it, so you never have to run anything to understand it. ## Read the quiet hours report Every run of quiet hours ends with a report, headed **Quiet hours report**. The newest one sits at the top of **Artifacts**, under **Latest quiet hours report**. 1. Press **Read report**. Its name says when those quiet hours ran, on your clock - whether they ran in your usual hours or you started them yourself. Two sentences at the top say what they came to, the numbers under them count where each finding stands now, and the line below counts the artifacts the tasks generated: findings filed, reports, opportunities. A run in which tasks failed says so there, rather than that it found nothing. 2. Read down the list: every finding quiet hours touched, grouped by what happened to it - Fixed, Needs you, Not fixed, Being fixed, Next quiet hours, Gone by itself and Dismissed. Each row says in a sentence what the problem was for somebody using the product, then either what is different now that it is fixed or why it was not fixed. The buttons above the list show one group at a time. 3. Press a finding to open everything about it in place: the screenshots before and after, what should happen and what did, how far its fix got and **Open the fix session**. **Fix now** and **Dismiss** work right there. 4. At the end, **Published in these quiet hours** lists what the tasks published, and **How quiet hours ran** says what went wrong, how much of each subscription was set aside and used, and what each task did. When tasks failed, **How quiet hours ran** comes first. Where each finding stands is read every time you open the report, so a fix that merges or goes live later shows without the report being written again. Every earlier report is in **Library**. ## Triage a finding 1. Open **Artifacts** from the left rail. **Needs you** holds what waits for you. 2. Each line starts with how bad it is: Critical puts people's data, money or security at risk or takes the product down, Blocker stops someone finishing what they came to do, Major leaves the product wrong or misleading, and Minor is everything smaller. 3. Press a line to open it: **Expected**, **Actual** and **How to fix**, beside a screenshot or a log of what happened. **How to fix** says what the fix would change besides the problem, so you know what you are deciding. 4. Press **Fix now** to start a session on it straight away, or **Dismiss** to close it for good. To see one kind only, such as Product quality or Feedback, choose it from **Show** above the list. Write in the comment box before pressing **Fix now** to steer the fix, or to ask a question the agent answers first. An opened finding also says who last changed it and when. Press **Show every change** to read its whole history. :::tip Several at once? Tick them and press **Fix selected now** or **Dismiss selected**. Iterada asks you to confirm once for the whole group. ::: ## Open an artifact An agent that produces something meant to outlive its conversation - a report, a document, a dataset, a picture or a recording - publishes it as an artifact, and it is kept in **Library**. The conversation that published it says so, with **Open Artifacts**. 1. Open **Library**: the artifacts are grouped by day, newest first, each a card with its kind, name, date and what it says. When one source published several on the same day, they stack into one card with the earlier ones listed under it. Press a card and it opens as its own page, with an address you can share. A report an agent wrote reads as a document, its pictures in place; press a picture to see it full size. Recordings and video play in place, anything else opens as a file. What the artifact carries for other agents is folded under **Details for agents**. **Back to Artifacts** returns to the list. 2. Press **Hand to an agent** to start a session that picks it up, with its files attached. Write in the comment box first to say what to do with it. ## Explore what your sessions decided A session records a decision only when it settles something worth keeping: a product decision you made or accepted, a design, a change to how the product is built, or a new feature. Most turns record nothing. The conversation says so when one does, with **Open decision**. 1. Open **Decisions**. The decisions are grouped by area, each group one line with its count; press a group to open it. Type in **Find a decision** to narrow the list as you type. 2. Choose another grouping from **Group by** - **Category**, **Tag**, **Session** or **Kind of session** - to see the same decisions another way. **Open all** opens every group at once. 3. Press a decision to read it on its own page: what was decided and why, beside the session that recorded it, its area, category and tags. Press any of them to see every decision that shares it. **Back to Decisions** returns to the list. Only the session that recorded a decision can revise it. A later session that changes it records a decision of its own, which names the one it replaces: the earlier one is kept, marked **Superseded**, with a link to what replaced it. Session details lists the decisions each session recorded, and the agents of later sessions read them too. ## What happens next A finding you fix becomes a session under **Automated** in the session list, with everything the quiet-hours pass recorded, and merges the way your project merges. A fix that quiet hours opened by itself is archived once it is live and its finding marked resolved, unless you stepped in; one you started with **Fix now** is yours to archive. A dismissed finding is kept at the end of **Needs you**, under **Dismissed**, and is never filed again; **Reopen** puts it back in the list. The same fault found again in a later quiet-hours run is the same finding, seen once more, not a new line. When Platform tidying finds two findings about the same problem, it dismisses the repeat and names the one it kept under **Duplicate of**. ## Tell us something The **Feedback** tab on the right edge of every screen sends a note straight to the Iterada team. Write what happened or what you wish Iterada did, then press **Send feedback**. On a paid plan you choose whether to tick **Attach screenshot**, **Attach diagnostic info** and, inside a session, **Attach this session**; on the Free plan they always go with the note. To report one reply that went wrong, press **Report incident** under it instead. ## Answer the drafts in Content **Content** lists every post, announcement and reply Iterada drafted for you, grouped by what you do next: **Due to post**, **Waiting for you**, **Planned**, and a fold of what was posted, missed or skipped. Iterada never posts anything itself. Open a draft to read its words, the picture drawn for it, the sources it rests on and the claims Iterada checked against them: each is marked as backed by a source, to check, or to change. Then answer it: - **Accept** plans it for the time in **Post at**, which starts at the first free hour of that network's usual posting times. - **Edit** lets you change the words yourself, and **Save and plan** plans your version. - **Send comment** has Iterada rewrite it into a new version. A comment that starts with the word rule and a colon is also kept under **Rules for every draft**. - **Skip** sets it aside; **Reopen** brings it back. When a planned draft's time comes, Iterada hands it to you here, in the Notifications menu and on Telegram, with a button that opens X, Bluesky or Threads with the post filled in, or copies it for LinkedIn. After you post it, paste the post's address and press **Mark posted**. A draft nobody posts within three days counts as missed. **Draft a reply** takes a thread you read, its address and its words, and drafts a reply for it. Switch on **Announcements from release notes** and Iterada drafts announcements of what just went live: at most two a week, the ones that matter most first, and a roundup of the week from Friday. Under **Drafting**, switch on Weekly posts to draft the week's posts from public research every Monday, and Daily replies to draft replies every weekday. Each runs on your own agent and is saved in **Agent factory**, where **Open in Agent factory** takes you to change its steps or times. **Draft now** runs one straight away. **Start a trial** writes the same evidence two ways so you can compare them without knowing which wrote what. These runs are listed under **Automated**, never among your sessions. ## See what your posts did A posted draft shows its numbers: visits and sign-ups from your site's links, and LinkedIn's impressions, clicks and reactions once you choose your LinkedIn analytics export and press **Add LinkedIn export** under **Results**. Mark a posted draft **Led to a conversation** or **Led to a pilot** when it did. Under **Results**, describe one change to try, choose the network and what judges it, and press **Start**. Iterada judges it only once there are eight posts on each side, and calls it better or worse only past a clear difference. **End this experiment** stops it. Every Monday a weekly review of the week before lands in the Library: what you posted, what it did, the replies you sent, the running experiment and whether each network is earning its place. ## Your own channels A blog article and a LinkedIn newsletter issue are drafts like any other. When a blog article's time comes, **Publish on the blog** starts a session that adds it to your site, which you review and merge like any change. A newsletter issue is copied for you and LinkedIn's article editor opens to paste it. **Plan a Show HN** prepares notes for one Show HN: what to show, candidate titles, an outline of your first comment with its sources, the questions to expect and the checklist. Hacker News takes no generated text, so you write and post it yourself.