`case_study_pipeline.ipynb` is the fourth notebook to come across and the
first to arrive without a new class of defect: eighteen modules, every prompt
carried over character for character, and the three faults the earlier ports
each contributed a bug to - an agent factory passed instead of called, a model
that comes back from the store as a dict, and an int key that comes back as a
string - all covered by tests before the first run rather than after it. Five
dry tests exercise the JSON round trip, the int-key restore, the review
corrections and both exporters without opening a socket.
The instructional-design type was four independent producers behind one
checkbox list. The notebook's own comment says why they must not share a crew;
nothing in them shares anything else either, so someone who wanted a pre/post
test was picking one box out of four on a form that asked for all of it. Each
is a type of its own now - «أنشطة تدريبية», «أدوات تطبيقية», «اختبار قبلي
وبعدي», «دراسة حالة تحليل…
«Did the deploy land?» had no answer on this API, so it was answered by
picking a marker and polling for it - and the marker picked was the static
pipeline's step order, which had shipped in the *previous* commit and was
already true. The Space was still building; a run was resumed against the old
code and failed with the exact error the deploy was meant to fix.
`/health` now returns `build`, read from `app/BUILD.txt`, which the deploy
writes the SHA into. One curl, no guessing.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
`infographic_pipeline.ipynb`, third of three: seven agents that turn raw
content into a complete interactive element - one of four screen patterns, a
zoom-in opening, an introduction and tips, the main screen, every element with
its definition and points, interactions with feedback, a storyboard for every
scene, and the two covers. Text only, and the scene description is written for
the graphics team in Arabic.
Every standard, every pattern brief, every agent and every prompt is the
notebook's to the character - including cell [10], the largest in the file,
which holds every measurable constraint and decides what an agent is asked to
do again. `test_interactive_infographic_fidelity.py` proves it in forty-two
checks.
This notebook writes its standards as `"""\` with a line continuation and keeps
several of its tables as tuples, so the fidelity test compares the *evaluated*
value rather than the source text - stricter, and honest about what the agent
actually reads.
The platform's par…
`static_infographic_crewai_pipeline.ipynb`: seven agents that turn raw subject
content into a complete infographic element - a layout profile chosen from
three, a definition box and stations with their points, interactions with their
feedback, a visual description for every station and every interaction, and the
two covers.
Every standard, every layout brief, every agent's role and backstory and every
prompt is the notebook's to the character. `test_static_infographic_fidelity.py`
reads the .ipynb and proves it in thirty-eight checks, including one that walks
every Arabic line the notebook puts in front of a model and finds it in the
ported module.
Three of those checks were wrong about the notebook before they were right
about the port, which is the useful kind of failure: `STD_LINK_PHRASES` is
assembled from a list rather than written out, `STD_GENERAL_DESIGN_NOTES` is a
list, and `STD_ALL_BODY` joins a chosen six rather than all of them - the
title-design and storyboard standards …
`motion_video_multiagent_v2.ipynb`: seven agents that turn raw teaching content
into a production-ready script - voice-over, an executable scene description
for the graphics team, the interactions, and the two covers every video opens
on - for three kinds of video, each with its own structure.
Every prompt, every standard, every agent's role and backstory, every JSON
skeleton and every lint pattern is the notebook's to the character.
`test_motion_video_fidelity.py` reads the .ipynb and proves it: forty-two
checks, including one that walks every Arabic line the notebook puts in front
of a model and finds it in the ported module.
What the platform adds is the orchestration. Each of the seven becomes a step,
so a failure costs that stage rather than the script and a resumed run picks up
where it stopped. The run stops once, at the instructional design - the title,
the axes, the objectives, the visual system and the scene plan - because the
six steps after it are all written against that…