EO Engineering Learning OS
CORE FOUNDATION · F04
Back to map ↑
NON-NEGOTIABLE FOUNDATION · TARGET L3 · 5–7 days
F04

Git & software delivery

Move a reviewed change from source to a recoverable deployment with clear history and ownership.

01 / CONCEPT MAP

Know what the parts mean.

Learn each concept deeply enough to recognize it, place it in the system and reason about normal and failed behavior.

01

Repository, working tree and history

Define it · locate it · observe it · explain its failure mode.

02

Commit quality and branches

Define it · locate it · observe it · explain its failure mode.

03

Remotes, clone, fetch, pull and push

Define it · locate it · observe it · explain its failure mode.

04

Pull requests and review

Define it · locate it · observe it · explain its failure mode.

05

Merge conflicts

Define it · locate it · observe it · explain its failure mode.

06

Ignore rules and secret hygiene

Define it · locate it · observe it · explain its failure mode.

07

Build, artifact, deploy and rollback

Define it · locate it · observe it · explain its failure mode.

02 / SYSTEM FLOW

Trace it end to end.

Change→Commit→Branch→Pull request→Test / review→Artifact→Deploy→Verify / rollback

For every transition: identify input, output, identity, protocol, state, trust boundary, evidence and owner.

03 / GUIDED BUILD

Build, observe and explain.

Documentation and AI are allowed. The engineer must review every output and demonstrate the result from direct evidence.

  1. 01Create a focused feature branch
  2. 02Commit logical changes
  3. 03Open and review a pull request
  4. 04Resolve a controlled conflict
  5. 05Build a versioned artifact
  6. 06Deploy and verify the exact version
  7. 07Roll back while preserving evidence
04 / INCIDENT

Production contains code that is not in the expected commit. Inject an uncommitted server edit and wrong artifact version.

Required investigation

State impact → collect evidence → form competing hypotheses → test the cheapest discriminator → isolate root cause → contain → correct → verify.

Evidence pack

Timeline, relevant logs/metrics, failed assumptions, root cause, correction, verification and one prevention action.

AI ownership

AI may suggest causes and commands. The engineer must explain why each check is safe, what result is expected and how the result changes the hypothesis.

05 / DESIGN CHALLENGE

Defend the decision.

Design a lightweight delivery policy for a six-person team: branches, reviews, approvals, artifacts, environments and emergency fixes.

06 / VERIFY, SUBMIT & REVIEW

Submission evidence

Architecture review

  • Explain git & software delivery without relying on memorized commands.
  • Draw the flow and name what crosses every arrow.
  • Identify the most likely, highest-impact and hardest-to-detect failure.
  • Show the evidence that proves the solution works.
  • Defend one security, reliability and cost trade-off.

Definition of Done

  • Acceptance criteria pass
  • Flow is drawn and explained
  • Security implications considered
  • Logs/metrics checked
  • Failure is tested
  • AI output is understood
  • Runbook is reusable
  • Mentor review passes
07 / MENTOR GUIDE

Do not score memory. Score the engineer’s ability to form a model, collect evidence, make a safe change and defend the trade-off.

1 Cannot explain2 Understands with gaps3 Implements and troubleshoots4 Designs and reviews