docs: add backlog.md for deferred capabilities and their triggers - #82
Merged
Conversation
Give intentionally-deferred work a home separate from design.md: each entry records what the capability is, why it is worth doing, and the concrete trigger condition for picking it up — guarding against both premature v1 scope creep and re-doing the research when the trigger fires. Pure open design questions stay in design.md §7. Seed with three entries distilled from the 2026-07 tutti review (443c8574..6e4f96d2): - Provider vs AgentTarget layering — wait for a second launch config per provider or third-party dynamic agents - Capability-style runtime preparation — a capability's prompt, skill and env must start/stop together; wait for skill injection or multi-host deployment - Opaque NodeRef / lazy ReferenceHandle — align when M5 lands mention:// and @ sources grow beyond BatonSession Also index backlog.md from AGENTS.md References.
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
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.
Give intentionally-deferred work a home separate from design.md: each
entry records what the capability is, why it is worth doing, and the
concrete trigger condition for picking it up — guarding against both
premature v1 scope creep and re-doing the research when the trigger
fires. Pure open design questions stay in design.md §7.
Seed with three entries distilled from the 2026-07 tutti review
(443c8574..6e4f96d2):
per provider or third-party dynamic agents
and env must start/stop together; wait for skill injection or
multi-host deployment
mention:// and @ sources grow beyond BatonSession
Also index backlog.md from AGENTS.md References.