Article 01

Architecture Governance in a Pull Request

A refund consumer starts non-compliant, is blocked in GitHub, is remediated, receives human approval, and is merged with full lifecycle evidence.

ArkSentinel AI · 18 Article Series

Where this article fits in the ArkSentinel journey

Article 1 of 18 · Current focus

Follow the progression from pull-request governance through enterprise architecture intelligence, developer enablement, evidence, and proactive governance.

Article 1PR GovernanceCurrent focus

Article 2Policy Versioning Article 3Organizational Governance Article 4Accountable Architectural Approval Article 5Portfolio Intelligence Article 6Governance Cost Article 7Architecture Risk Article 8Drift & Technical Debt Article 9Cross-Repository Intelligence Article 10ADR Governance Article 11AI Architect Article 12From Violation to Fix Article 13Compliance & Evidence Reports Article 14Governance Data to Decisions Article 15Architecture Audit Trail Article 16Enterprise Governance Platform Article 17Proactive Architecture Governance Article 18Beyond Pull Requests

All 18 articles are now published and clickable. The highlighted card shows your current position in the complete ArkSentinel AI journey.

1. A normal change creates architecture risk

Alice adds a refund-message consumer. The code works functionally, but the initial implementation omits idempotency, retry/failure handling, and an explicit consistency boundary.

ArkSentinel detects three findings, 25% compliance, and returns FAIL/BLOCK.

2. GitHub enforces the decision

The ArkSentinel status check is required, so a failed governance decision prevents the pull request from being merged.

GitHub blocks the merge because the required ArkSentinel Architecture Governance check failed.

3. Architecture passes, but the human gate remains

Alice remediates the findings. ArkSentinel reaches 100% compliance with zero findings, but the repository still requires one human approval.

Architecture Governance PASS; Human Review PENDING; Overall Merge Readiness BLOCKED.

4. Human approval completes governance

Bob approves the corrected code. ArkSentinel reports the pull request as READY.

Architecture PASS + Human APPROVED = READY.

5. The lifecycle closes with evidence

Alice merges. ArkSentinel preserves the approver, merger, final SHA, timestamp, and policy evidence.

Final pull-request lifecycle recorded as MERGED.