Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

## Unreleased

- Accept the user-requested, reviewed Skills update at `472c216f2f043f0add1f83540cc46ea53d20a7cd` as `0.1.0-dev.5`, including collaboration principles and bundled quality-validation guidance. Preserve automatic sensitive-change holds; this update uses a separate protected PR.

- Record independently verified live source-push dispatch, automatic protected update/merge, post-merge no-op, and sensitive-change hold receipts; retain explicit host-runtime and scheduled-timer coverage limits.

- Update packaged skills from `ffb5025dfa9f25fab868a4f12f9fb661ac7bfb87` to `14b8ad3dbba8ea820478d3ea2d379c2863de56d9` (0.1.0-dev.4).
Expand Down
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.1.0-dev.4
0.1.0-dev.5
2 changes: 1 addition & 1 deletion plugins/claude/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,5 +5,5 @@
"description": "Vstack portable workflows and engineering principles.",
"license": "MIT",
"name": "vstack",
"version": "0.1.0-dev.4"
"version": "0.1.0-dev.5"
}
44 changes: 22 additions & 22 deletions plugins/claude/SOURCE.json

Large diffs are not rendered by default.

Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@

1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow.
2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof.
3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`.
3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable.
4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open.
5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate.
5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment.
6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria.

## Pitfalls
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@

1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow.
2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof.
3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`.
3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable.
4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open.
5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate.
5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment.
6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria.

## Pitfalls
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@

1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow.
2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof.
3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`.
3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable.
4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open.
5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate.
5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment.
6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria.

## Pitfalls
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@

1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow.
2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof.
3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`.
3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable.
4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open.
5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate.
5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment.
6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria.

## Pitfalls
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@

1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow.
2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof.
3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`.
3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable.
4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open.
5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate.
5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment.
6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria.

## Pitfalls
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@

1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow.
2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof.
3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`.
3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable.
4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open.
5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate.
5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment.
6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria.

## Pitfalls
Expand Down
Loading
Loading