Execution architecture¶

English | 日本語

Current interaction sequence¶

This view answers one question: who acts in what order from an interactive request or optional Control wake-up through accepted delivery evidence?

sequenceDiagram
    actor Human
    participant Control as Optional Control
    participant Codex
    participant AIT as AI Teams
    participant GitHub
    participant Provider as Selected provider

    alt Interactive request
        Human->>Codex: Request work and supply authority
    else Trusted orchestrated wake-up
        Control->>Codex: Start isolated work
    end
    Codex->>AIT: Run the coordination contract
    AIT->>AIT: Establish Goal, constraints, profile, and Bet
    opt Bounded independent challenge is justified
        AIT->>Provider: Request one authorized review primitive
        Provider-->>AIT: Return bounded evidence
    end
    AIT->>GitHub: Record Work Item and delivery objects
    AIT->>Codex: Implement and run focused checks
    Codex->>GitHub: Publish exact-head candidate
    GitHub-->>AIT: Return validation and merge evidence
    AIT-->>Human: Report delivery readback, outcome evidence, and Next Bet

The coordinator makes product and authority decisions. Codex/native tools edit and test the workspace. A connected provider performs only the primitive for which it is selected and authorized. AI Teams does not transfer provider credentials or silently substitute another system of record.

Provider resolution¶

For operations in the accepted capability inventory, selection proceeds through host/platform native, installed Plugin, connected Connector or MCP, standard CLI/service, then bundled fallback. Each provider class is observed at most once for one operation. Unknown or unauthorized capability fails to a bounded handoff.

The machine-readable inventory is the source for the generated capability reference. Detailed semantics remain in the provider-resolution contract.

Optional external Control¶

The bounded Control MCP client can connect to independently distributed Qoo257/ai-teams-control. External Control owns Issue discovery, scheduling, persistent queue and recovery state, worker lifecycle, and optional provider-event integrations. This Plugin owns no scheduler, queue, poller, or orchestration runtime. GitHub Issues and pull requests remain authoritative for GitHub delivery, and external Control cannot weaken repository acceptance or trust boundaries.