Skip to case study

Creative practice · October 18, 2026

From a Wall of Eyes to an Ethics Hearing

How I use AI to develop a story: a record of my source material, associations and direction, alongside the assistant’s interpretation and generated draft.

The creative path

  1. Choose the image: a man facing a wall of watching eyes.
  2. Connect it to the graduate student trapped with PIXIE.
  3. Supply my earlier Fogg workshop from A to Z of Magic.
  4. Identify Synchronicity II and No Place Like Home as musical associations.
  5. Move into the rescuer’s viewpoint and introduce Dr. Meyers.
  6. Use AI to compare the material and draft a committee scene; record its additions.

Creator: Dominique Devereaux / IBLoud

Process record: October 18, 2026, America/Chicago

Status: AI-assisted process documentation and proposed creative direction. The scene was developed as an AI-generated draft. Dominique subsequently supplied its published PIXIE link: https://pixie.pckt.blog/pixie-incident-review-r417uz7. Publication does not independently establish every proposed detail as wider project canon.

This document records the visible conversation that produced the PIXIE incident-review scene. It distinguishes Dominique’s source material and creative decisions from AI interpretation and newly generated prose. It does not claim to reproduce unseen earlier conversations or the complete Wattpad archive.

1. The starting object

Dominique supplied renmakesmusic-story-4010159851270897080.mp4, a roughly 20-second clip. Its imagery shows a seated figure, viewed from behind, facing a wall of older televisions displaying eyes.

The assistant extracted and inspected still frames. It interpreted the image through surveillance, public scrutiny, identity, and the reversal of the viewer’s gaze. These were interpretations, not verified statements of Ren’s intent.

Capability limit: The assistant did not reliably listen to the audio. Its initial promise to listen overstated its available capability; it corrected that claim. Subsequent musical interpretation was grounded in the song references and lyrics Dominique supplied, not an analysis of the uploaded soundtrack. The clip’s music was not identified.

2. Dominique supplied the narrative situation

Dominique connected the image to a fictional graduate student injured after a laboratory power surge while connected to a Matrix/Animus-like environment. She becomes trapped; PIXIE fuses with her organic tissue; others describe her as “brain damaged.” Dominique proposed a university president’s voice or a research ethics committee meeting as the setting.

These elements came from Dominique. They were not discovered in the image by AI. Matrix and Animus were Dominique’s analogies, not verified technical descriptions or claims of affiliation.

Dominique required the assistant to ask when it could not access the referenced associations. The assistant initially asked for blog names before adequately checking the archive. Dominique corrected it and directed it to the archive.

3. What the archive did—and did not—establish

Retrieved earlier discussion distinguished Urban Alien Adventures / IBLoud IVXX, Loptr Lab, and PIXIE. An archived portfolio source identified https://pixie.pckt.blog/ as a reflective archive about systems, incentives, architecture, and creative practice. Other archived material identified The Rift Report as an existing publication.

The assistant also read the saved retrospective I Was Designing a Narrative Game Before I Knew How to Explain It. That AI-assisted retrospective describes Dominique’s earlier IBLoud Wattpad work inspired by The Magicians and Battle the Beast: music as navigation, persistent memory, altered timelines, and ethical choices. It is a secondary account, not a replacement for the original stories.

The specific A to Z of Magic passage and graduate-student incident were not recovered in that search. The assistant could not verify the proposed scene’s placement against complete fictional continuity. Public retrieval of the PIXIE blog also failed; that does not establish that the blog itself is unavailable.

4. Dominique supplied the primary story reference

Dominique pasted “Straight Outta Filory,” from A to Z of Magic by IBLoud. The supplied editor text marked it published and displayed 912 words. Those metadata were supplied by Dominique, not independently verified.

Cover reference: https://img.wattpad.com/cover/139868907-64-k546720.jpg — a cover image, not a full story permalink.

In the supplied passage, Dean Fogg addresses an audience in a workshop framed by lawyers and a software warning. He describes separating Aster from Luna to demonstrate his competence. Luna’s music helps balance Aster’s powers. The examination becomes catastrophic, Aster’s body is left comatose, and Fogg admits manipulating memories while trying to repair the consequences.

The narrative device—an authority figure revealing responsibility through an apparently instructional address—already existed in Dominique’s writing before this session. AI did not invent that device for her project.

Dominique explicitly identified The Police’s “Synchronicity II” and Todrick Hall’s “No Place Like Home” as the important musical references. The assistant proposed connections involving interdependence, return, identity, and who defines recovery. These are creative readings, not confirmed artist intent or proof that either song plays in the uploaded clip.

5. Dominique changed the viewpoint

Dominique then made the decisive connection: the man in the chair is trying to get her out, and his feelings cloud his judgement. She introduced Inpatient’s “Dr. Meyers” and pasted its lyrics.

That supplied text presents a doctor who distances himself from the children in his care, rationalizes harm through scientific and commercial objectives, and later seeks a breakthrough after Jeremiah’s death. The assistant worked from the pasted text; it did not independently verify the recording, credits, linked annotations, or broader Inpatient continuity.

Dominique supplied the association between this doctor and the would-be rescuer. The assistant articulated a possible dramatic parallel: scientific ambition and personal attachment can each become reasons to disregard the person supposedly being helped. This is an ethical analogy within the proposed fiction, not an assertion that the characters have identical motives or culpability.

6. What AI contributed to the scene

The assistant proposed a fictional incident-review transcript titled PIXIE · Incident Review, spoken by the man in the chair before a committee. It generated the scene’s wording, pacing, questions, stage directions, and ending.

New details invented by the assistant include: the student continuing to communicate; her warning that separation might hurt; the rescuer dismissing PIXIE as interference; an instruction to suspend extraction; her asking him to wait; and his attempting another extraction anyway. These were narrative proposals, not facts supplied by Dominique or recovered from her archive. They require her continuity review.

The draft also gives the man knowledge of Meyers’s account. Whether that connection is literal, metaphorical, musical, or part of the fictional world remains unresolved. No particular relationship between the man and the student was established.

The draft’s movement is from “I promised to get her out” towards asking what she needs. Its underlying questions are whether observation amounts to understanding, whether the rescuer can hear an answer he dislikes, and who has authority to define recovery.

7. Contribution record

ContributionSource
Selecting the Ren clip as a creative promptDominique
Graduate student, power surge, entrapment, organic fusion with PIXIEDominique
University president / ethics committee framingDominique
Earlier Fogg workshop, Aster–Luna balance, memory interventionDominique’s supplied Wattpad writing
Synchronicity II and No Place Like Home associationsDominique
Rescuer viewpoint, emotional conflict, Dr. Meyers connectionDominique
Visual interpretation, thematic comparison, suggested publication placementAI analysis, directed and corrected by Dominique
Incident-review dialogue and newly proposed scene eventsAI-generated draft
Final continuity, revisions, acceptance, and publication decisionsDominique; pending

This is a record of creative contributions, not a legal determination of copyright ownership.

8. What this example demonstrates

Dominique uses association across images, music, earlier fiction, and current projects to direct creative work. Here, AI helped put those materials beside one another, articulate relationships, and produce a reviewable scene. The direction developed through her references and corrections; it did not originate from an autonomous AI reading of the clip.

The example also exposes limitations worth retaining in a public account: incomplete retrieval, an overstated audio capability, and plausible scene details that could be mistaken for established canon if their origin were not recorded.

9. Recommended public home

Publication decision: the process case study is hosted in the ibloud.github.io provenance section; the scene is published on PIXIE. Proposed title: *From a Wall of Eyes to an Ethics Hearing: How I Use AI to Develop a Story*. Publish the provenance beside the draft so readers can distinguish source writing, interpretation, and generated additions. This recommendation rests on PIXIE’s archived editorial description; current blog contents and complete story continuity were not verified.

Supporting placement: link the case study from Loptr Lab’s authorship / AI-use documentation or contributor guidance as a concrete example. A later character-led story may also fit Urban Alien Adventures, subject to Dominique’s editorial decision.

Before publishing, add the original Wattpad story permalink, review invented details, resolve “symbolic” versus “symbiotic” in the initial premise, and decide how Dr. Meyers exists within the scene’s frame. Link to musical works rather than reproducing the full lyrics. This document does not reproduce them.

Suggested disclosure: “I selected the visual reference, supplied my earlier fiction and music associations, and directed the character’s viewpoint and ethical conflict. AI helped compare those materials and generated a scene draft. The accompanying process record identifies its invented additions and limitations.”

10. Publication follow-through

Dominique supplied the published scene link and directed implementation of this case study in ibloud/ibloud.github.io. The case study and process record are linked from the provenance index and the homepage Authorship & AI tools section.

Scene: https://pixie.pckt.blog/pixie-incident-review-r417uz7

Case study: https://ibloud.github.io/provenance/ai-assisted-story-development/

11. Ecosystem assessment following use of Manus.im · 18 October 2026

Dominique identified this follow-up as occurring after her use of Manus.im and supplied PIXIE story and ecosystem evidence audit — 18 October 2026.md for review. She then asked ChatGPT to distinguish unnecessary recreation from genuine loss and to include the assessment here. The supplied audit is the handoff evidence; this record does not independently verify the Manus.im session, its full inputs, or which tool performed each reported action.

Finding: the available evidence supports duplicated explanation and retrieval gaps; it does not establish permanent loss of original story text or source code. During this follow-up, ChatGPT retrieved the existing canonical ecosystem architecture, which already documents lineage, distributed discovery, and local project authority. ChatGPT’s initial suggestion that a new public map was needed overlooked that existing authority.

What was recreated or added

Recreated or added work
ItemAssessmentEvidence boundary
Ecosystem map and lineageExisting authority overlookedThe canonical architecture already maps the creative lineage, distributed discovery model, and project authority. Reconstructing those relationships as unknown repeated documented work.
Separate ecosystem guidePotentially redundant explanationThe supplied audit reports a new guide repository. Its contents and current availability were not verified in this follow-up; its independent necessity is not established. Any guide should link to the canonical map.
Provenance cube addendum and typography changesUnnecessary additions reported by the auditThe audit says these local edits were started without being necessary to the assessment. They were not recovery of missing source material; their present state was not verified.
AI incident-review sceneNew generated materialThe scene’s invented events are proposals, not recovered archive text. They cannot establish the contents of earlier writing.
Separate PIXIE software experimentsDuplication not establishedDifferent helpers, discovery tools, workspace prototypes, and server experiments may serve different purposes. Shared branding does not establish redundant implementation.

What was genuinely lost?

No permanent artifact loss was confirmed in this review. The following are retrieval, traceability, or verification gaps rather than established destruction:

Unresolved recovery questions
Material or capabilitySupported status
Earlier conversations and complete Wattpad archiveUnretrieved; deletion or irrecoverability not established.
A to Z of Magic source locationA supplied passage survives in the process record, but a full story permalink remains missing from this record.
Chronology, character identities, and canon decisionsUnresolved in the retrieved evidence; this does not establish that Dominique never made those decisions.
Hosted MCP endpoint or unified PIXIE runtimeWorking functionality was not verified. Loss of a previously working integrated service was not established.
Five documentation repairs and other local editsReported unpublished work whose recovery status requires a checkout, branch, commit, or patch. This follow-up did not locate those artifacts.

Attempts to retrieve the reported guide README and an assumed inventory path returned “Not Found.” That result does not distinguish an incorrect path, access limits, relocation, or deletion, and is not proof of loss.

What this adds to the AI-use record

The demonstrated failure was continuity in the assistance: an existing architecture was overlooked while fresh explanations were proposed. Dominique used a cross-tool handoff and follow-up questioning to expose the difference between missing retrieval, new AI output, and actual recovery. This is an assessment of the available record, not a claim that Manus.im caused every reported problem.

The corrective approach is to reconnect authoritative sources before recreating them, identify surviving unpublished work by concrete artifacts, and keep public guides subordinate to the canonical map. AI may propose clearly labeled possibilities; Dominique decides what enters story canon. This assessment adds no story events or canon decisions.