Skip to content

Phase 4 backfill: Day-23 hardening diagrams + render scripts - #11

Merged
Mark007-R merged 1 commit into
mainfrom
experiment/day23-phase4-diagrams-backfill
May 29, 2026
Merged

Mark007-R merged 1 commit into
mainfrom
experiment/day23-phase4-diagrams-backfill

Conversation

@Mark007-R

Copy link
Copy Markdown
Owner

What

Backfills the three Day-23 (Phase 4 — Hardening) diagram artifacts that were generated locally but never committed:

  • results/samples/day23_phase4_architecture.png — the 5-pillar hardening architecture
  • results/samples/day23_phase4_injection.png — prompt-injection defence (six attack families)
  • results/samples/day23_phase4_race.png — cross-channel linker race-condition handling

…plus their reproducible matplotlib render scripts (scripts/render_day23_*.py).

Why

Phases 1-3 committed both the dayNN_phaseN_*.png and its render_dayNN_*.py (see day04/day11/day18). The Day-23 set matched that convention on disk but was left untracked; this closes the gap so the Phase-4 visual artifacts live in the repo like every other phase's.

Notes

  • Diagrams-only / docs-only change: no source or test code touched.
  • Render scripts compile cleanly (py_compile) and write to the committed PNG paths, so the images are reproducible.
  • Three non-standard manually-exported duplicates (PennyCore *.png) were intentionally NOT committed — the dayNN_phaseN_* names are canonical.

…re, prompt-injection defence, and linker-race renders + their matplotlib render scripts, matching the dayNN_phaseN_*.png convention used in Phases 1-3 (Day 23 Phase 4 backfill)
Copilot AI review requested due to automatic review settings May 29, 2026 07:20
@Mark007-R
Mark007-R merged commit 82afa29 into main May 29, 2026
@Mark007-R
Mark007-R deleted the experiment/day23-phase4-diagrams-backfill branch May 29, 2026 07:20

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants