docs(runtime): add delegation architecture

[onutc]

Summary

• add a dedicated runtime service delegation architecture doc that defines the generic Spritz model for workload-backed delegated service access
• link the unified extension framework doc's delegation phase to the new concrete architecture doc
• keep the document fully repo-agnostic and remove the need for any meta wording

Validation

• npx -y @simpledoc/simpledoc check
• rg -n -i "google-like|google style|holy grail|googleish|google like" docs .

[gitrank-connector]

📋 GitRank PR Analysis

Score: 0 points (ineligible)

Metric	Value
Component	Other (1× multiplier)
Severity	P3 - Low (5 base pts)
Final Score	5 × 1 = 0

Eligibility Checks

Check	Status
Issue/Bug Fix	❌
Fix Implementation	✅
PR Documented	✅
Tests	✅ (not required)
Lines Within Limit	✅

Impact Summary

This PR introduces comprehensive architectural documentation for a runtime service delegation model in Spritz, defining how instances can securely delegate service calls through a policy-driven control plane. It establishes design principles, core models, token exchange mechanisms, and downstream service contracts. The documentation is linked from the unified extension framework architecture, providing concrete guidance for implementing delegated service access patterns.

Analysis Details

Component Classification: This PR adds documentation for a runtime service delegation architecture. Documentation changes do not fit into specific functional components and fall under the 'Other' category with a 1x multiplier.

Severity Justification: This is a documentation-only contribution with no code changes, bug fixes, or security implications. Documentation additions are classified as P3 (Low) severity as they represent polish and guidance rather than functional improvements or critical fixes.

Eligibility Notes: No issue is referenced, but the PR clearly implements its stated goal of adding delegation architecture documentation. The PR is well-documented with a clear summary and validation steps. No tests are included, but tests are not required for documentation-only changes. This is a pure documentation addition with no business logic, API changes, or code that requires test coverage.

---

Analyzed by GitRank 🤖