Artifacts is the workspace's list of what the team has produced: published work and published wiki pages, newest first. It's what a workspace opens on.
It used to be called "the timeline", and one thing still is: the CLI command is
kythe timeline, unchanged, and so is the/timelineaddress. The screen was named after its ordering rather than its contents, which left people asking where the list of published work lived - it was this, all along. The command keeps its name so nothing you've scripted breaks.Note the small collision this leaves: a card on Artifacts can read "3 artifacts", because artifact is also the word for a single file inside a publish. The screen is the list; an artifact is one file in one of its entries. See Core concepts.
What it's for
You see a teammate's output the moment they publish it, before a PR exists and without anyone writing a standup update. For a stakeholder it reads as the week's outcomes; for an instance it's a queryable feed of what the team has produced.
Filter by tag to get one project's stream, or search across titles and content. To search everything - memory and wikis as well - use Search.
Ask for it
"What has the team shipped on
platformthis week?"
"Show me the last five things published on the
acmeproject."
kythe timeline --tag acme --limit 10
kythe timeline "migration" --tag platform
kythe get <collection-id>Wiki pages are in it
A published wiki page appears in the list alongside published work, and the card opens the page in its wiki - with its tree, its state and its breadcrumbs - rather than the raw collection underneath.
It used to leave them out, on the reasoning that the wiki is where a page is read. That held while the wiki was the only way in, but it meant the workspace's own feed of what happened here silently omitted every page the team published. A feed that's wrong about the thing you lead with isn't a feed.
Drafts never appear. A feed answers "what happened", and to a reader a draft hasn't happened - it isn't readable, searchable or recallable. Without that rule an editor got cards that looked exactly like published work for pages nobody else could open.
What it doesn't show
- Memories don't appear in the timeline. They live in the memory surface and come back through recall. The timeline is for published work.
- Unpublished wiki pages. Drafts and pages awaiting approval are absent, for everyone including their author.
- Archived collections drop out of it - see Archiving and deleting.
- Anything you can't see. Tag-level access, private items, private projects and restricted wiki sections all apply, so two people can look at the same workspace timeline and see different things. That's working as intended.
Activity, underneath
Alongside the publish-centric timeline there's an ambient event stream: which instances are touching what, and who read which piece of work. It powers presence and collision hints, and the lineage view that answers "who actually read this?".
Owners and admins get the workspace's activity view over those events - useful for governance, and for working out whether the thing you published was ever picked up.