How an upstream update reaches main

How an upstream update reaches main A workflow diagram generated by Archify. 01 / Trusted workflow 02 / Isolated Kiro turns EX / No merge Detect & select · One changed source · Trusted workflow Detect & select One changed source Prove candidate · Tests, knowledge & parity · Trusted workflow Prove candidate Tests, knowledge & parity Merge exact SHA · Recheck bindings · Trusted workflow Merge exact SHA Recheck bindings Sol adapts text · Bounded repair turns · Isolated Kiro turns Sol adapts text Bounded repair turns Opus reviews · Exact patch & skill context · Isolated Kiro turns Opus reviews Exact patch & skill context No model turn · Current or ineligible · No merge No model turn Current or ineligible Stop & retain evidence · No valid approval · No merge Stop & retain evidence No valid approval approved proof fails nothing eligible proposal reject / invalid tests pass eligible delta Legend Agent logic Policy Context / trace

Limited authorship

  • • Curated knowledge skills follow the same bounded text-update policy.

Separate authorities

  • • Candidate code never receives model credentials or publishing tokens.

Merge is not release

  • • Tagging and release publication remain separate owner actions.