Claude/add jiron support 0112 bjd f wa wsp zhmd1f7o xi4 #57
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Create comprehensive task specification for adding Jiron hypermedia support: - Server rule/command for building Jiron APIs from requirements - Client rule/command for generating Web Components from endpoints - Dual-render pattern for SEO + agent-optimized views Includes supporting documentation: - Original and enhanced prompts (SudoLang format) - Questions with inferred answers - Expert panel roundtable analysis
Key changes: - Goal: self-describing APIs with ONE browse capability, not just token efficiency - Add jiron-agent rule for agent navigation patterns - Add MCP comparison (Q9) explaining paradigm difference - Update expert panel to emphasize "one capability" architectural win - Server rule now includes root discovery and state transition requirements The core insight: Jiron could replace MCP for web API interactions. Agents don't need predefined tools - they browse self-describing APIs.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a comprehensive planning epic for Jiron support to the aidd framework. Jiron enables self-describing hypermedia APIs that allow AI agents to browse and interact using a single generic capability, rather than requiring explicit tool definitions (like MCP) for each API. The epic includes detailed task breakdowns, expert panel analysis, and supporting documentation to guide implementation of both server-side (API creation) and client-side (Web Components) capabilities, along with dual-render patterns for serving both human-friendly HTML and token-optimized agent views.
Key Changes
- Introduces Jiron support paradigm as an alternative to MCP for agent-API interactions
- Defines 7 implementation tasks covering server rules, client components, and dual-render patterns
- Includes comprehensive planning artifacts (expert roundtable, Q&A, enhanced prompt)
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| tasks/jiron-support-epic.md | Main epic file defining goals, requirements, and 7 task breakdowns for Jiron implementation |
| tasks/jiron-support-epic-roundtable.md | Expert panel analysis providing architectural insights and recommendations |
| tasks/jiron-support-epic-questions.md | Q&A document addressing implementation questions with inferred answers |
| tasks/jiron-support-epic-original-prompt.sudo | Original task prompt as received (contains spelling errors) |
| tasks/jiron-support-epic-enhanced-prompt.sudo | Improved, structured version of the prompt with SudoLang syntax |
| plan.md | Updated project plan to include the new Jiron Support Epic |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Why? | ||
|
|
||
| - Token-friendly AI agent-browsable interaction support for apps | ||
| - Alternate server-rendered view of app pages - we should add an ai/rules and ai/commands pair to create server-rendered views for SEO and agent navigation. For browsers: render HTML. For agents, allow them to get a token-efficient Jiron view of that same document tree by fetching path/pagename.jiron. create a link with a real that clearly identifies this as a token-effient view for agents. Should include and HTML comment with instructions to the agent to fetch the Jiron views, instead. |
There was a problem hiding this comment.
Spelling error: "real" should be "rel" (referring to HTML link relation attribute)
Suggested change
| - Alternate server-rendered view of app pages - we should add an ai/rules and ai/commands pair to create server-rendered views for SEO and agent navigation. For browsers: render HTML. For agents, allow them to get a token-efficient Jiron view of that same document tree by fetching path/pagename.jiron. create a link with a real that clearly identifies this as a token-effient view for agents. Should include and HTML comment with instructions to the agent to fetch the Jiron views, instead. | |
| - Alternate server-rendered view of app pages - we should add an ai/rules and ai/commands pair to create server-rendered views for SEO and agent navigation. For browsers: render HTML. For agents, allow them to get a token-efficient Jiron view of that same document tree by fetching path/pagename.jiron. create a link with a rel that clearly identifies this as a token-effient view for agents. Should include and HTML comment with instructions to the agent to fetch the Jiron views, instead. |
| Why? | ||
|
|
||
| - Token-friendly AI agent-browsable interaction support for apps | ||
| - Alternate server-rendered view of app pages - we should add an ai/rules and ai/commands pair to create server-rendered views for SEO and agent navigation. For browsers: render HTML. For agents, allow them to get a token-efficient Jiron view of that same document tree by fetching path/pagename.jiron. create a link with a real that clearly identifies this as a token-effient view for agents. Should include and HTML comment with instructions to the agent to fetch the Jiron views, instead. |
There was a problem hiding this comment.
Spelling error: "token-effient" should be "token-efficient"
Suggested change
| - Alternate server-rendered view of app pages - we should add an ai/rules and ai/commands pair to create server-rendered views for SEO and agent navigation. For browsers: render HTML. For agents, allow them to get a token-efficient Jiron view of that same document tree by fetching path/pagename.jiron. create a link with a real that clearly identifies this as a token-effient view for agents. Should include and HTML comment with instructions to the agent to fetch the Jiron views, instead. | |
| - Alternate server-rendered view of app pages - we should add an ai/rules and ai/commands pair to create server-rendered views for SEO and agent navigation. For browsers: render HTML. For agents, allow them to get a token-efficient Jiron view of that same document tree by fetching path/pagename.jiron. create a link with a real that clearly identifies this as a token-efficient view for agents. Should include and HTML comment with instructions to the agent to fetch the Jiron views, instead. |
|
|
||
| - Given a Jiron server API endpoint, dynamically build web components capable of interacting with the endpoint: | ||
| - support siren semantics: https://github.com/kevinswiber/siren | ||
| - note: siren is kindof a mapping of html to json, so we can represent entity IDs with html-style URIs to support linking resources to other resources, including side-lining, rather than embedding child objects, collections, etc. |
There was a problem hiding this comment.
Grammar error: "kindof" should be "kind of" (two separate words)
Suggested change
| - note: siren is kindof a mapping of html to json, so we can represent entity IDs with html-style URIs to support linking resources to other resources, including side-lining, rather than embedding child objects, collections, etc. | |
| - note: siren is kind of a mapping of html to json, so we can represent entity IDs with html-style URIs to support linking resources to other resources, including side-lining, rather than embedding child objects, collections, etc. |
Key refinements: - Use AIDD's createRoute + asyncPipe, NOT Express - Add Streaming Middleware task using Web Streams API - Portable across Vercel, Netlify, AWS Lambda, Deno Deploy - Avoid Node.js-specific streams for edge runtime compatibility New task: src/server/middleware/with-stream.js Total tasks: 8 (was 7)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
Adds a comprehensive Jiron Support epic with rules/commands and supporting docs, and updates plan.md (including Context7 section formatting).
tasks/jiron-support-epic.md(scope, constraints, and requirements for server/client, dual-render, streaming, agent navigation)tasks/jiron-support-epic-enhanced-prompt.sudo,tasks/jiron-support-epic-original-prompt.sudotasks/jiron-support-epic-questions.md,tasks/jiron-support-epic-roundtable.mdai/rules/jiron-server.mdc,ai/commands/jiron-api.md,ai/rules/jiron-client.mdc,ai/commands/jiron-component.md,ai/rules/dual-render.mdc,ai/commands/dual-view.md,src/server/middleware/with-stream.js,ai/rules/jiron-agent.mdc(AIDDcreateRoute/asyncPipe, Web Streams API, TDD).plan.md: fixes formatting forContext7 GitHub Action Epicblock; addsJiron Support Epicentry with file link, goal, and task list.Written by Cursor Bugbot for commit 70aaebb. This will update automatically on new commits. Configure here.