Skip to content

architecture.md

Latest commit

 

History

History
40 lines (29 loc) · 1.6 KB

architecture.md

File metadata and controls

40 lines (29 loc) · 1.6 KB

TORII Architecture & Concepts

TORII defines intent, Git executes it.

System Boundaries

TORII operates as a distinct Control Plane, separate from the Git Execution Plane.

Control Plane (TORII System)

  • Responsibility: Management of Repositories, Policies, and Access Bindings.
  • Interface: Synchronous API.
  • Output: Auditable Event Stream.

Execution Plane (Git Host)

  • Responsibility: Storing Git objects, handling git-receive-pack and git-upload-pack.
  • Interface: SSH / HTTP(S).
  • Integration: Server-side Git Hooks + Host Agent Gates.

Core Concepts

Repository as Resource

A Repository in TORII is a managed resource with a unique ID, an owner, and attached policies. It maps to a physical storage location on the Execution Plane.

Policy & Gates

Policies are declarative rules (e.g., "Main branch is protected", "Author email must match verified domain"). Gates are the enforcement points (Pre-Receive Hooks, SSH Authentication Wrapper).

Event Stream

The append-only log of every control action (e.g., "Policy Updated") and enforcement decision (e.g., "Push Rejected: Policy Violation").

High-Level Data Flow

  1. Admin defines Policy via Control Plane API.
  2. TORII persists Policy and emits PolicyCreated event.
  3. Developer initiates git push.
  4. Execution Plane (Gate) intercepts the request.
  5. Gate queries TORII for authorization/policy check.
  6. TORII evaluates request against active Policy.
  7. TORII returns Allow/Deny decision and emits GitOperationGated event.
  8. Execution Plane proceeds or rejects the push.