Delivery architecture¶

English | 日本語

Normal path¶

GitHub Issue
  → exact Issue-linked branch and registered worktree
  → focused implementation checks
  → review-stable required profile
  → pull request at an exact head SHA
  → exact-head hosted validate
  → eligible merge
  → Issue/check/commit readback
  → remote and local topic-branch cleanup

GitHub and Git are the system of record. Ordinary work never pushes directly to main. Existing user changes are not included, tested, or removed. A failed, skipped, stale, or unavailable hosted validation blocks acceptance until the isolated self-hosted runner/workflow produces a new exact-head success.

Verification relationship¶

Focused checks provide fast iteration evidence. The required profile proves a review-stable repository candidate. Merge acceptance requires evidence bound to the pull request head. Release gates are cumulative and separate from merge.

The disposable self-hosted runner receives no host mount, Docker socket, or delivery credential. Local test results are iteration evidence, never merge evidence.

The executable contract is trusted delivery.