Repository navigation
Spec S-001: stale proposals - #71
Merged
Merged
Conversation
S-001: a proposed decision is stale when a host its basis names has a newer observation; worked out on read, never stored, shown in decisions list, show and why, filtered with --stale, and named in the approve prompt without refusing it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
@romamo Decision needed: approve spec S-001 (stale proposals, #26)? Merging this PR is the approval, so triage won't merge it under "merge when green". The choices it makes, for you to confirm or change:
Merge for 1, or reply with a number or your own answer; shipmill takes this up on the tick after your reply. |
Contributor
Author
|
Decision by @romamo, relayed by Claude Code 1, merge as is. Roman merges this PR himself. |
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.
Spec for #26 (its last open part,
stale, back for a decision after 0.6.0 shipped stable).docs/specs/001-stale-proposals.md,status: approved. Merging this PR approves the spec; no build starts before then.What the spec settles, for review:
proposeddecision is stale when a host itsbasis.observedAtnames now has a laterobservedAtin the basis folder. The observation timestamp only: the basis records no repository commit, so a commit rule needs the basis to grow first (out of scope)cloudfall. This departs from D-1's pattern of a stored status, on purpose: a storedstalewould need a trigger that writes recordsstaleandstaleHostsonproposeddecisions indecisions list,decisions showandwhy; a--stalefilter ondecisions listandwhyspecs.py checkpasses.🤖 Generated with Claude Code