Skip to content

docs: update problem statement with progressive discovery details - #14

Open
kurtisvg wants to merge 1 commit into
mainfrom
docs/problem-statement
Open

docs: update problem statement with progressive discovery details#14
kurtisvg wants to merge 1 commit into
mainfrom
docs/problem-statement

Conversation

@kurtisvg

Copy link
Copy Markdown

Initial strawman for a problem statement from @SamMorrowDrums, @helloeve, and myself.

Comment thread docs/problem-statement.md
Comment on lines +119 to +121
3. **Server-provided semantics:** Servers can communicate relationships,
entrypoints, and task-oriented guidance without prescribing the client's
search or prompt implementation.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think one question this raises is if we intend to try and solve disambiguation here - things like tool-prefixing for namespacing purposes, which has the side-effect of causing server-provided primitive usage guidance to not exactly match the client's semantics.

Comment thread docs/problem-statement.md
entrypoints, and task-oriented guidance without prescribing the client's
search or prompt implementation.
4. **Dynamic correctness:** Discovery can reflect authorization, configuration,
and catalog changes while remaining cacheable.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarify that this is about maintaining a stable prompt cache prefix; this will be confused for the TTL work I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants