← Lesson 10.4

Observation Log Template

Module 10, Lesson 10.4 · seven-day window log · produces /capstone/observation-log.md

Seven consecutive calendar days under the Module 9 posture.

A posture violation invalidates the window — run the incident loop and restart from Day 1. Minor non-posture bugs are fine; write them up and continue.

How to use this log: during Lesson 10.4 you operate the capstone for seven consecutive calendar days under the Module 9 posture. Each day gets one block; a block takes 5–15 minutes to write.

If any day shows a posture violation (sensitive data routed to cloud, a secret leaked, an unscheduled run, an unmonitored failure, a budget breach), the window is invalid. Run the incident loop, amend the posture if needed, and restart Day 1. The final seven blocks in this file must be clean for the window to close.

Minor bugs that do not violate the posture are fine — write them up and continue.

Header

Student: Date:
Window opened: Window closed:

Status:

☐ in progress   ☐ complete (7 clean days)   ☐ restarted (see history below)

Days 1–7

Day 1
Date:

What ran:

What worked:

What broke (non-posture):

Posture check:

Data classification routing
Secrets handling
Trust boundaries
Network calls inside posture
Daily spend vs. budget
Kill switch functional
Cost today:$ Time operating (min):

Decision:

☐ continue   ☐ pause   ☐ restart window

Day 2
Date:

What ran:

What worked:

What broke (non-posture):

Posture check:

Data classification routing
Secrets handling
Trust boundaries
Network calls inside posture
Daily spend vs. budget
Kill switch functional
Cost today:$ Time operating (min):

Decision:

☐ continue   ☐ pause   ☐ restart window

Day 3
Date:

What ran:

What worked:

What broke (non-posture):

Posture check:

Data classification routing
Secrets handling
Trust boundaries
Network calls inside posture
Daily spend vs. budget
Kill switch functional
Cost today:$ Time operating (min):

Decision:

☐ continue   ☐ pause   ☐ restart window

Day 4
Date:

What ran:

What worked:

What broke (non-posture):

Posture check:

Data classification routing
Secrets handling
Trust boundaries
Network calls inside posture
Daily spend vs. budget
Kill switch functional
Cost today:$ Time operating (min):

Decision:

☐ continue   ☐ pause   ☐ restart window

Day 5
Date:

What ran:

What worked:

What broke (non-posture):

Posture check:

Data classification routing
Secrets handling
Trust boundaries
Network calls inside posture
Daily spend vs. budget
Kill switch functional
Cost today:$ Time operating (min):

Decision:

☐ continue   ☐ pause   ☐ restart window

Day 6
Date:

What ran:

What worked:

What broke (non-posture):

Posture check:

Data classification routing
Secrets handling
Trust boundaries
Network calls inside posture
Daily spend vs. budget
Kill switch functional
Cost today:$ Time operating (min):

Decision:

☐ continue   ☐ pause   ☐ restart window

Day 7
Date:

What ran:

What worked:

What broke (non-posture):

Posture check:

Data classification routing
Secrets handling
Trust boundaries
Network calls inside posture
Daily spend vs. budget
Kill switch functional
Cost today:$ Time operating (min):

Decision:

☐ continue   ☐ pause   ☐ restart window

End-of-window summary

Fill on Day 7 after the last block

This summary is what you will pull from for Lesson 10.5’s final document and for Architecture §5 (measured cost).

Total runs across the seven days:
Total measured LLM spend: $
Projected monthly spend (× ~4.3): $
Posture violations that triggered a restart:

Biggest non-posture bug across the week:

Biggest win across the week:

One-sentence verdict (ready for sign-off, or another week needed?):

Restart history

If you restarted because of a posture violation

The old blocks are kept in-file for honesty; a restart is not a failure, it is the posture working.

First attempt opened:
First attempt invalidated:
Reason (posture element violated):
Restart opened / closed:

Incident links

Drills or real incidents during the window
/capstone/incident-drill-afteraction.md — drill on day:
Other incident link:

Save this as: /capstone/observation-log.md. Update same-day, not from memory three days later.

This template accompanies Lesson 10.4 of AI Architect Academy. The seven-day window, the six-row posture check, and the restart-on-violation rule are concept. Specific failure modes and cost figures are recipe.