# GitHub-Native Agentic Engineering Operating Model

## Slide 1 - Thesis

The operating model is the product. Agents are only useful when GitHub, CI, review, and platform policy make work legible.

## Slide 2 - Control Surface

Issues express intent. Branches isolate work. Pull requests carry evidence. CI enforces checks. Reviewers approve risk.

## Slide 3 - Repository Readiness

Each repo needs ownership, instructions, build and test commands, generated-file policy, forbidden areas, and rollback guidance.

## Slide 4 - Issue Contract

Issues need acceptance criteria, non-goals, affected components, risk class, validation expectations, and escalation boundaries.

## Slide 5 - Worktree Discipline

Use short-lived worktrees from protected trunk. Keep `develop` as scratch only. Never push trunk directly.

## Slide 6 - CI Guardrails

Run formatting, linting, typechecking, tests, schemas, security checks, preview builds, and artifact validation before merge.

## Slide 7 - Review Loop

Agent review is useful but not authoritative. Human review owns judgment, system context, and production risk.

## Slide 8 - Control Plane

Centralize manifests, ledgers, approvals, evaluations, provenance, and publish history. Keep agents narrow.

## Slide 9 - Platform Integration

Join GitHub repos, AWS tags, Terraform state, service ownership, dashboards, alerts, and deployment records.

## Slide 10 - Autonomy Boundary

Automation may increase only inside proven policy, telemetry, CI, rollback, and approval boundaries.