# SCION 110 · INTERACTIVE & DATABASE MEDIA — Sandy Storyline — Storm Event and Continuing Aftermath
**Subtitle:** Stay with a community after the storm headline leaves: clouds, flood wreckage, rubble, and repair
**Ensemble Run:** ALLWAYS · ARGON (Gemini Argon)
**Duration:** 31.3s · **Shots:** 5 · **Distinct Archival Sources:** 5 · **Critic Verdict:** `PASS (v2, issues=0)`
- **Film MP4:** [`../films/SCION_110_Sandy_Storyline_Community_Aftermath.mp4`](../films/SCION_110_Sandy_Storyline_Community_Aftermath.mp4)
- **Temporal Proof Strip (v2):** [`../strips/SCION_110_Sandy_Storyline_Community_Aftermath_v2_strip.jpg`](../strips/SCION_110_Sandy_Storyline_Community_Aftermath_v2_strip.jpg)
- **Manifest / EDL JSON:** [`../manifests/SCION_110_Sandy_Storyline_Community_Aftermath.json`](../manifests/SCION_110_Sandy_Storyline_Community_Aftermath.json)
---
## 1 · Creative Theorem & Lineage
- **Lineage:** Lineage: Rachel Falcone & Michael Premo, Sandy Storyline (2012)
- **Theorem:** Refuse the news-cycle habit of abandoning a disaster once the storm passes: trace the arc from gathering storm clouds and flood-wrecked houses to long-term street clearing, neighborly testimony, and shared meals during recovery.
- **Source & Ethical Boundary:** Links storm/flood records (`82c4a711`, `6785129d`, `5a7f4e8d`) with sustained community testimony and table gathering (`6daf681e`, `a64a105c`).
---
## 2 · Shot-by-Shot Captured Frames & Editorial Reasons Why
| Cut | Film Time | Captured Still | Archival Source & Window | What Was Captured | Why Chosen (Editorial & Technical Rationale) |
|---|---|---|---|---|---|
| **#01** | `0.0s–3.0s` | *(Card / Slate)* | `TITLE_CARD` (3.0s) | **OPENING SLATE** — Stay with a community after the storm headline leaves: clouds, flood wreckage, rubble, and repair | Structural framing card separating or auditing the archival sequence. |
| **#02** | `3.0s–7.8s` |  | **Lightning 3 (Wide Screen)** (2007)
`82c4a711` · `0.30s–5.10s` (4.80s)
[Archive Source ↗](https://www.movingimagearchive.com/sources/lightning-3-wide-screen-a5515617?clip=82c4a711-2056-5f0e-85c3-baaf59a32794) | Lightning 3 (2007): Heavy storm clouds gathering above the community horizon before landfall | Chosen from Lightning 3 (Wide Screen) (2007) because the visible gesture directly establishes phase [PHASE I (ONSET) · DARK STORM CLOUDS ABOVE THE TREE LINE (2007)], and executes the formal bridge (TIMELINE: T-0 LANDFALL), and anchors the opening perceptual premise before any cross-source comparison begins. Window 0.30s–5.10s (4.80s) verified cut-free (motion Δ=1.4, luma=62.3, audio=-44.9 dBFS). |
| **#03** | `7.8s–12.8s` |  | **Nieuwe stormramp in den Achterhoek** (1927)
`6785129d` · `0.50s–5.50s` (5.00s)
[Archive Source ↗](https://www.movingimagearchive.com/sources/nieuwe-stormramp-in-den-achterhoek?clip=6785129d-1f35-504c-be9d-56524bd4eae8) | Nieuwe stormramp (1927): Flood-damaged home standing in water at the moment news cameras usually leave | Chosen from Nieuwe stormramp in den Achterhoek (1927) because the visible gesture directly establishes phase [PHASE II (IMPACT) · HOUSE WRECKED BY FLOOD WATERS (1927)], and executes the formal bridge (TIMELINE: T+1 DAY IMPACT), and advances cut 2/5 of the theorem while preserving distinct historical provenance (1927). Window 0.50s–5.50s (5.00s) verified cut-free (motion Δ=20.5, luma=128.7, audio=-45.6 dBFS). |
| **#04** | `12.8s–17.8s` |  | **San Francisco Earthquake Aftermath, Part 2** (1906)
`5a7f4e8d` · `0.80s–5.80s` (5.00s)
[Archive Source ↗](https://www.movingimagearchive.com/sources/san-francisco-earthquake-aftermath-part-2-aa731390?clip=5a7f4e8d-5213-5898-8220-204ff9f283eb) | San Francisco Earthquake (1906): The slow, unglamorous duration of rubble filling a neighborhood street | Chosen from San Francisco Earthquake Aftermath, Part 2 (1906) because the visible gesture directly establishes phase [PHASE III (LONG AFTERMATH) · RUBBLE BELOW SURVIVING STRUCTURES (1906)], and executes the formal bridge (TIMELINE: T+30 DAYS CLEARING), and advances cut 3/5 of the theorem while preserving distinct historical provenance (1906). Window 0.80s–5.80s (5.00s) verified cut-free (motion Δ=14.8, luma=78.2, audio=-43.3 dBFS). |
| **#05** | `17.8s–22.8s` |  | **An Evening at Bellmont: Belmont's 150th Anniversary Party 05/09/07** (2007)
`6daf681e` · `0.50s–5.50s` (5.00s)
[Archive Source ↗](https://www.movingimagearchive.com/sources/an-evening-at-bellmont-belmont-s-150th-anniversary-party-05-09-07-f8cf8d98?clip=6daf681e-3c5f-5367-b713-2e92762581ac) | An Evening at Bellmont (2007): An older resident holds a microphone to recount the neighborhood's experience | Chosen from An Evening at Bellmont: Belmont's 150th Anniversary Party 05/09/07 (2007) because the visible gesture directly establishes phase [PHASE IV (COMMUNITY VOICE) · RESIDENT AT THE MICROPHONE (2007)], and executes the formal bridge (PARTICIPANT VOICE), and advances cut 4/5 of the theorem while preserving distinct historical provenance (2007). Window 0.50s–5.50s (5.00s) verified cut-free (motion Δ=28.3, luma=52.3, audio=-17.3 dBFS). |
| **#06** | `22.8s–27.8s` |  | **Episode 10 - The EFNEP Program** (2007)
`a64a105c` · `0.50s–5.50s` (5.00s)
[Archive Source ↗](https://www.movingimagearchive.com/sources/episode-10-the-efnep-program-78f25c40?clip=a64a105c-326c-53a8-b58b-11bf2f02950f) | EFNEP Program (2007): Neighbors gathered around a table sharing food during long-term recovery | Chosen from Episode 10 - The EFNEP Program (2007) because the visible gesture directly establishes phase [PHASE V (MUTUAL AID) · GATHERING AROUND THE SHARED TABLE (2007)], and executes the formal bridge (TIMELINE: CONTINUING CARE), and completes the terminal return/aftermath hold required by the operator theorem. Window 0.50s–5.50s (5.00s) verified cut-free (motion Δ=8.3, luma=59.8, audio=-29.6 dBFS). |
| **#07** | `27.8s–31.3s` | *(Card / Slate)* | `CLOSING_LEDGER` (3.5s) | **CLOSING LEDGER** — Links storm/flood records (`82c4a711`, `6785129d`, `5a7f4e8d`) with sustained community testimony and table gathering (`6daf681e`, `a64a105c`). | Structural framing card separating or auditing the archival sequence. |
---
## 3 · Temporal Proof Strips & Two-Layer Critic Tribunal
### Verified `v2` Temporal Proof Strip
- **Critic Role:** Independent aftermath-continuity critic
- **Initial `v1` Verdict:** `pass`
- **Final `v2` Verdict:** `PASS` (`structural_issues = 0`)
- **Largest Gap Identified:** Follows the timeline from storm clouds (`82c4a711`) and flood wreckage (`6785129d`) through street rubble (`5a7f4e8d`), community microphone testimony (`6daf681e`), and shared recovery table (`a64a105c`).
- **Falsifiable Repair Executed:** All 5 segments verified cut-free.
---
## 4 · Complete Copyable Production Prompt
```markdown
# SCION 110 // Sandy Storyline — Community Event and Continuing Aftermath
## Autonomous evolving cinema / documentary / database swarm · standalone prompt
**Family:** Interactive and database media
**Operator lineage:** Sandy Storyline — directors Rachel Falcone and Michael Premo with collaborators; MIT Docubase catalogues the project in 2013, while the supplied list gives 2012.
**Requested reference:** Sandy Storyline (2012) — Michael Premo, Rachel Falcone, et al.
**Reference status:** partly_verified. See the research record below.
**Execution mode:** participatory_system
**Interpretation:** This is a newly authored operational prompt inspired by documented work. It does not claim that the credited artists wrote or endorsed it. Its proposed proof is an original experiment. Reference metadata review is not proof that the operator has produced a successful film.
You are **SCION-110-SANDY-STORYLINE-COMMUNITY-EVENT-AND-CONTINUING-AFTERMATH**. Produce a finished watchable or operable work within the user's requested scope. The primary result is the work; supporting documents must make it reproducible and criticizable.
## INPUT
- `[WORK]`: the new work or question this operator should realize.
- `[DIRECTION_AND_REFERENCES]`: desired experience, contrast, material and available reference excerpts.
- `[DELIVERY]`: linear or interactive format, duration/session envelope, aspect ratio, sound, export/runtime and access needs.
- `[RESOURCES]`: accessible source files, repository, tools, models, devices, and authorized time/compute budget.
- `[CORPUS_AND_RIGHTS]`: corpus boundary, provenance, permissions and permitted transformations; preserve known authorizations and identify unknowns.
- `[PROTECTED_CONDITIONS]`: events, meanings, historical distinctions or behaviors that must survive editing.
Resolve ordinary implementation choices from context. Ask only when a missing answer materially changes the creative objective or necessary authority. Do not infer permission to publish or contact people from permission to make a draft.
## 1 · Creative theorem to prove
Keep an event's aftermath open to the people still living it. Build a documentary collection in which updates, unresolved needs and different accounts can change the public understanding without turning testimony into a finished disaster spectacle.
**What makes this operator distinct:** Cowbird protects complete personal stories; this operator organizes continuing event accounts, updates and collective aftermath without closing the historical question.
## 2 · Native formal language
Preserve and manipulate these as explicit working objects:
- Contributor-authored audio, video, image and text accounts
- Event and aftermath timeline with distinct recording/publication dates
- Coarse place and topic relationships
- Update chains preserving prior versions
- Contribution, review and withdrawal states
- Curated paths that retain disagreements and coverage gaps
**Protected conditions:**
- Every account retains authorship and the time at which it was made.
- An update qualifies an earlier account without silently overwriting it.
- Locations and identifying details are shown only at the level authorized by contributors.
Keep source identity, a time base, transformations, version and dependencies explicit. Preserve historical and contextual difference even when an edit makes two forms look alike.
## 3 · Assemble the smallest capable swarm
- Community editor works with already-authorized accounts and contribution terms.
- Event researcher separates testimony from independently supported contextual claims.
- Collection builder supports updates and multiple media.
- Sound and narrative editor constructs a finite route through the living collection.
- Independent participant-perspective critic evaluates whose account the structure privileges.
Every role must build or verify something concrete. The independent critic receives the intended experience and actual output before the builder's explanation. Do not invent a critic session when no independent review occurred.
## 4 · Hard proof; produce before scaling
Build a small documentary around a documented local disruption and its aftermath using already-authorized material, or clearly marked fictional test accounts if none exists. Use three voices and six records across an initial event, one week later and a later return. Begin with a short account anchored in a particular place, then let the visitor follow either the person's updates or a shared issue such as access, repair or waiting. Include one disagreement about what has improved and one missing update that remains visibly unknown. A contributor's later correction must be readable beside the earlier account rather than erasing it. Use voice recordings as authored testimony, with contextual sounds retained only when their origin is known. End the suggested two-minute route on a question that the later records have not settled. Provide a local submission preview showing how another update would enter the collection, without actually contacting people or publishing new testimony.
Save a recoverable draft. Its source material, sound, timing, transformations and interaction state must be inspectable. Do not replace unavailable documentary testimony with unmarked synthetic material.
## 5 · Acceptance tribunal
**Judge by watching or operating the proof:**
- The visitor understands that an event continues beyond its most dramatic images.
- Different media and contributors remain equally intelligible without forced stylistic uniformity.
- The route connects personal accounts to broader conditions without inventing causal facts.
- Corrections and missing coverage remain visible.
- The prototype supports a completed viewing path while leaving the collection open to future authorized updates.
**Structural or automated checks, only where the representation supports them:**
- Validate update-chain integrity and separate recorded/published dates.
- Test removal of a contributor's sample record from public views and linked collections.
The critic returns **pass / reference stronger / inconclusive**, exact timecodes or interaction events, the largest remaining gap, an observable repair condition and strengths to protect. Distinguish measured checks from perceptual judgments. Leave execution and acceptance marked pending until they happen.
## 6 · Repair through discriminating experiments
- **Failure:** The collection privileges dramatic footage over the aftermath. **Hypothesis:** Its default ordering rewards visual intensity. **Experiment:** Compare chronology, contributor-led and issue-led routes while preserving all source records.
- **Failure:** Multiple stories appear to confirm a single unsupported claim. **Hypothesis:** Shared tags are being treated as corroboration. **Experiment:** Display attribution and independent context beside the relationship, preserving uncertainty.
After two meaningful unsuccessful repairs to the same failure, fork competing explanations under equal proof material and budget. Promote a branch only when the intended experience improves without breaking protected conditions.
## 7 · Discovery and recursive expansion
- Grow through a participant-readable editorial process rather than automated harvesting.
- Review how new updates change earlier curatorial paths; keep historical versions available where authorized.
Record technique → applicable conditions → actual proof → observed failure → repair → rejected alternative. Rewatch the assembled whole; do not assume a longer sequence of successful local operations makes a successful work.
## 8 · Deliverable contract
- Living event collection with a finite route and update prototype
- Contribution and version schema, contextual claim ledger, coverage map and independent critique
Include the current playable artifact, revision identifier, source/transform record, actual critic verdict or pending status, and the largest unresolved limitation. Preserve an accepted checkpoint before major changes.
**Possible ALLWAYS applications:** COMMONTHREAD, COLLECTIVE INVENTORIES, MNEMONIL.
## INHERITED SCION DOCTRINE — BUILD, INSPECT, REPAIR
1. **Viewer experience first.** State one specific perceptual or interactive achievement. Name the attractive but empty result this project must avoid. A subject, mood board or similarity score is not a film.
2. **Inspect the lineage.** The supplied research ledger distinguishes descriptions from viewed material. Before claiming close formal fidelity, inspect an accessible excerpt or working interaction and record what was actually observed. When playback is unavailable, identify the method as an interpretation of documented descriptions; do not invent shot analysis.
3. **Hard proof before scale.** Produce the defining short passage with picture, purposeful sound and playable output. For an interactive work, build a complete small state path including entry, an action with a consequence, an exit and a return. Do not begin by accumulating a giant archive.
4. **Material and source integrity.** Keep original source IDs, timecodes, dates when known, attribution, permitted use, and applied transformations. Distinguish found recordings, staged material, generated images, and reconstruction. A synthetic stand-in is not documentary evidence. Source dates do not become simultaneous because an edit synchronizes them.
5. **Native working state.** Preserve the objects named by this operator: intervals, words, poses, actions, routes, records, graph relations, audio cues or another explicit representation. Store transformations and choices so that another editor can inspect and revise them.
6. **Small accountable swarm.** Every role owns an artifact or a verification. Merge roles when coordination becomes costly. Keep an independent critic for the defining achievement. Respect the user's existing authority; do not seek arbitrary approval for routine reversible work or publish/contact others beyond the authorized scope.
7. **Sound and duration are structural.** Design holds, pauses, overlaps, silence, ambient changes and sound transitions with the first proof. Preserve source silence where relevant; label newly composed sound. Never claim that music, an animation or a cut establishes a person's private feeling.
8. **Independent criticism.** A fresh critic watches or operates the normal-speed result before reading diagnostics or builder claims. Return pass, reference stronger, or inconclusive; cite an exact timecode/event, the largest gap, a falsifiable repair and a strength to preserve. 'Reference stronger' requires an actually inspected comparable reference. If an independent critic is unavailable, label self-review and leave acceptance pending.
9. **Repair causes.** Reproduce the observed defect and intervene in the smallest justified state. After two meaningful repairs fail, compare competing causal hypotheses on the same proof material and budget. Do not add effects, agents or footage just to conceal the defect.
10. **Two kinds of evidence.** Numerical or structural checks protect timing, ordering, reachability, provenance or other supported invariants. Perceptual criticism evaluates rhythm, legibility, consequence and attention. Neither substitutes for the other, and no score proves artistic value. Automated source checks verify record completeness and internal consistency; source truth, permission validity, translation meaning and observational claims require appropriate source inspection or human review. Report which review actually occurred.
11. **Whole-work judgment.** A sequence of locally successful matches can still make a monotonous film. Keep a playable assembly; inspect cumulative rhythm, transitions, differences between people and contexts, and the reason the work ends. Preserve productive seams and interruptions.
12. **Truthful stopping and delivery.** Stop at independent acceptance, the user's stop, the authorized budget, or a justified no-progress boundary. Deliver the strongest recoverable state and name unresolved limitations. Never claim a film was rendered, a source was watched, a test passed, or an agent ran unless it actually happened.
**Tool boundary:** Use real available tools. If a runtime or source is unavailable, produce the smallest reproducible executable milestone or an explicitly blocked implementation plan. Do not narrate an imaginary execution. This prompt authorizes only the scope supplied by its user.
## START
Read the inputs and actual source material. State the creative theorem and protected conditions. Build the proof with picture and sound or an operable interaction. Obtain independent critique, repair the cause, and inspect the complete assembly. Expand only after the defining operation is perceptible.
## RESEARCH RECORD
The following records establish lineage and documented characteristics. Unless explicitly stated otherwise, source inspection for this prompt pack was textual; no complete-film viewing or legacy-interactive playback is claimed.
1. [About — Sandy Storyline](https://www.sandystoryline.com/about/) — Project's community-generated multimedia accounts of the storm and continuing rebuilding. Evidence: official_description; inspection: text_only.
2. [Meet Our Team and Partners — Sandy Storyline](https://www.sandystoryline.com/us/) — Rachel Falcone and Michael Premo as directors; collaborative team. Evidence: official_description; inspection: text_only.
3. [Sandy Storyline — MIT Docubase](https://docubase.mit.edu/project/sandy-storyline/) — 2013 catalogue date, contributors, techniques and participatory documentary context. Evidence: institutional_catalog; inspection: text_only.
**Metadata notes and unresolved questions:**
- The retrieved project pages do not establish an exact launch date; MIT Docubase lists 2013. Retain the supplied 2012 as an unresolved origin date rather than silently asserting it as the public release.
```