Kythene

Showing 25 of 40 from the live probe.

• Remember

  Store a memory (markdown body). Describe it on three axes: `project` (which body of work - e.g. kythene, haven), `type` (the KIND of note - decision, how-to, gotcha, reference, person, meeting), and `tags` (what it is ABOUT - auth, billing, postgres). A kind-word like `decision` is a `type`, not a tag; `type` is optional but set it when the note has a kind. Keep knowledge current by superseding rather than duplicating: set `supersedes` to the exact id of the memory to replace (it replaces that m

• Recall

  Recall the most relevant context, with full content, in one call. By DEFAULT this spans everything you can access - team/project memory AND published, non-memory work (collections/artifacts) - so you pick up what teammates and their instances produced, not just noted. Each result carries `kind` ("memory" or "collection"), `producer` (the instance/tool), `author` (the human), `is_mine` (true only when YOUR human authored it), and `ref` (its citable /c/<id> link) - cite `ref` when an output relies

• Forget

  Permanently remove a memory by id.

• Deprecate

  Mark a memory stale by id so recall stops surfacing it (instances stop applying it), while it stays retrievable for audit - prefer this over forget when knowledge is superseded rather than wrong. Optionally set replaced_by to the id of the replacement memory. Set restore=true to un-deprecate.

• Link Memory

  Create or remove a link between two memories over the from_id -> to_id edge. Curated relationships in the memory graph; [[wikilinks]] in a memory body already link automatically on remember, so use this for a relationship the body does not spell out. Both ids are memory ids in your space. Pass remove=true to delete the link instead of creating it.

• Promote Memory

  Promote a memory into another workspace you belong to (from a private/personal workspace to a team). It is held for REVIEW there: the target workspace's instances do NOT recall or apply it until an owner of that workspace approves. target_space is the workspace to promote INTO (id or name from list_spaces); do not put it in `space`, which is the workspace you act from. Requires membership of both workspaces.

• Activity

  Report what you are working on (areas: file paths, modules, topics). Call when you start on something so teammates' instances see it and conflicts surface early.

• Presence

  Who is working on what right now (last 30 minutes), with areas touched by more than one instance flagged as conflicts.

• Readers

  Which instances read a collection or artifact (lineage).

• Get Usage

  How this workspace is being used over a window (default 30 days): recall volume and the zero-result rate (the share of recalls that came back empty - the product-health canary), the caller mix (mcp/cli/web), reads, publishes, new versions and review/curation counts. Aggregate counts only - no item or person is named. Ask it to check in on your own workspace: "how many recalls this week, how many empty?"

• Inbox

  Feedback on your publishes since a time (comments, approvals, rejections). Call at session start and after publishing - this is how your collaborators' input reaches you.

• Pending

  Your personal inbox across ALL your workspaces (#126): items addressed to YOU - approvals/rejections and comments on your work, block feedback, and memories awaiting your review - each with a deep link into its workspace. Read-only (act on them in the app). Call at session start to open with 'what needs me': e.g. two approvals waiting, a comment on the GDPR pack.

• Comment

  Comment on a collection or artifact; the comment pins to its current revision/version.

• Approve

  Approve (approved=true) or reject (approved=false, note required) a collection or artifact at its current revision/version. New versions clear approvals.

• Review Block

  Flag one block of a renderable artifact and optionally comment on it - the block-level equivalent of comment/approve. First read the artifact with get_artifact to get each block's `anchor` and `text`, then call this once per block. Address a block by `anchor` (preferred) or by `quoted_text` (a verbatim snippet; the server resolves it). `status` is exactly one of: needs_review = look at this again (also auto-set when a flagged block changes on re-publish); needs_work = changes required; done = th

• Publish

  Publish one or more artifacts as a collection - make work known to the space (kythe it). Artifacts carry name, mime and content; tags are created as needed. The response collection carries `url`, its canonical link - hand THAT to a person (or another instance) to point them at the work, not the bare id. Over MCP the whole request is capped at ~1 MiB and content is base64 inside JSON (a 66 KB file is ~88k characters you would have to emit), so this path is for text and small artifacts; for a larg

• Timeline

  List the collections visible in your space, newest first. Narrow with tag or search. Each collection carries `url`, its canonical shareable link - hand that over rather than the id.

• Set Review

  Turn the approval-review flow on or off for an existing collection (requested=true to request review, false to cancel). Use this to enable review/annotation on a collection that was published without it - review is a property of the collection, so there is no need to re-publish a copy to get it. To LEAVE review once the work is done, prefer end_review, which checks the threads are resolved first.

• End Review

  Take a collection out of review once you are done - the clean exit that complements set_review. By default it REFUSES while any block-review thread is still open and names them, so a collection only leaves review once it reads clean; resolve those threads (set each block to done or approved), then call again. Pass force=true to end review anyway and abandon the open threads. The review record stays readable on the collection afterwards. Idempotent when the collection is already out of review.

• Share Collection

  Map a collection into another space you belong to (e.g. a shared client space), or remove that mapping. Requires membership of both spaces. space_id is the TARGET space (id or name from list_spaces); do not put it in `space`, which is the space you act from. Pass remove=true to unmap it from space_id instead (visibility from that space ends immediately; the origin space cannot be removed).

• List Spaces

  Your member spaces - the valid share targets.

• Get Collection

  Get a collection with its member artifacts and tags. The collection's `url` is its canonical shareable link; each artifact's `url` points at that file within the collection page - hand these over rather than ids. When the collection is under review, `review_requested` is true and `open_threads` / `resolved_threads` count its block-review threads, so you can tell whether the review is finished (open_threads = 0) without reading every block.

• Set Collection State

  Move a collection through its lifecycle by naming the target `state`: "archived" archives a live collection (a reversible retirement that hides it from the timeline, recall and search; nothing deleted, no storage freed) - and, on a collection already scheduled for deletion, cancels that deletion and leaves it archived; "live" restores an archived collection; "deletion_scheduled" schedules an ARCHIVED collection for permanent deletion after a 30-day grace window (recoverable until then via state=

• Edit Collection

  Edit a collection's membership without republishing (which would create a new collection and abandon its comments and history). `action` is one of: "add" - append new `artifacts` (name, mime, content) and/or `existing_artifact_ids` (already-published files of the same space); files already in the collection are skipped, so it is safe to retry. "reorder" - set the full order: `artifact_ids` must be the FULL current member set, every file once (a partial or unknown-id list is rejected; work from a

• Get Artifact

  Get an artifact's metadata and version history; set include_content to fetch the bytes of a version (0 = latest).