VRS: define runner-owned stable launch identity - #80
Closed
myobie wants to merge 1 commit into
Closed
Conversation
myobie
force-pushed
the
agent/issue-64-stable-identity-vrs
branch
from
July 30, 2026 22:16
49fcb0a to
a31099b
Compare
This was referenced Jul 31, 2026
25 tasks
Contributor
|
Superseded by merged presentation and runner-owned launch identity work (#136 and #180). Posted on behalf of @schickling
|
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.
Problem
Issue #64 requires one stable agent identity boundary before child start without depending on session-name inference or late runtime enrichment. Issue #108 additionally requires mutable display names to remain presentation-only and outside that identity boundary.
Draft contract
ST_AGENT=<host.identity>for every declared task.role=agent,run.role=coding-agent, andagent.actor.path=<host.identity>.ST_AGENTbut no canonical-agent PTY tags.ST_AGENT, bus paths, task IDs, resource anchors, or the running process, and never restarts work. Issue Add first-class display-name authoring without changing agent identity #108 owns the authoring surface.Scope
This is a thin, source-linked VRS clarification only:
docs/vrs/requirements.mdadds R23.docs/vrs/spec.mdseparates the accepted contract from current implementation evidence and gaps.R23 avoids the R20-R21 requirements already on live main and the concurrent R22 draft. No runtime, parser, validator, generator, test, or vision change is included. The draft explicitly records that runner derivation, explicit-form tag parity, richer stable tags, and authored-conflict validation remain implementation gaps.
Exact evidence
c6846f6239329f0803142afc06c15a07b93937c1a31099bc2426f35935bd176e3b53e03b6300bb5bcargo test --test invariants -- --test-threads=1cargo test --doc --workspacecargo doc --workspace --no-deps(5 pre-existing warnings)git diff --check origin/live-mainNo merge or rollout.
Tracks #64 and #108.