Ari’s Space*   est. 2026
Skip to content
ari*s space[ a. ]
← Libraryari os / 2026-10-03

Vybe-Check: From A Vibe To An Agreed Brief

Why I needed a creative workshop for image prompts, how it develops intention through context and refinement, and how the public release candidate keeps agreed decisions intact.

11 parts / Hover to explore. Click to read.

Why I needed a creative workshop for image prompts, how it develops intention through context and refinement, and how the public release candidate keeps agreed decisions intact.

Partial brief -> resolve choices
                    | agree
Complete brief      |
+ prompt request ---+
                    v
              agreed version
                    |
               draft revision
                    | accept
                new version
A complete brief with an explicit prompt request can take the direct drafting path; unresolved choices need agreement. Accepting a revision appends a version while retaining its provenance.

A prompt can name the subject, lens, film stock and mood while leaving the image undecided.

Where should I look first? What does the reference actually establish? Which part of this proposal are we keeping? If we make another version, will that decision survive?

That is why I needed Vybe-Check. I started by asking for an image-prompt enhancer. As we developed it, I wanted more context, more intention and a conversation that could refine the frame with the judgement of a director of photography and a creative team.

The outcome became an agreed creative brief with reasons behind its choices. A generation prompt expresses that brief. An image can be the whole result; motion is a further choice when the idea needs it.

This account follows the summer shoot developed around me and my black Raptor, then looks at the public 0.1.0rc1 source candidate. The illustrations use approved finished test images and precomputed Higgsfield reconstructions made from those outputs. The raw face references and identity pack stay private. No control on this page submits a generation job.

Decide what the viewer should notice

The starting request was a posed shoot of me with the Raptor, using the original vehicle photo and privately held identity references. We wanted several prompts that could belong to one shoot.

That tells us the subject and vehicle. It does not yet tell us their relationship in the frame. How much space does the truck get? How posed am I? What makes the photograph feel like a summer memory?

Answer those before adding another row of adjectives. The question what should the viewer notice first? gives the later camera and styling choices something to serve.

Then set the anchors. One woman. One recognisable black Raptor. Agreed styling that can hold across the series. A portrait crop must still leave believable proportions for the cab, wheels and bed; the truck cannot stretch just to fill a tall image.

Separate three things:

  • Outcome: what the image should do and where it will be used.
  • Priority: the action, relationship or detail carrying the image.
  • Anchors: supplied facts and agreed constraints a later proposal must preserve.

Give each reference a role too. A photo can establish geometry, lighting, colour or composition. A lighting example does not automatically prescribe the wardrobe or identify the person. Without that distinction, incidental details turn into instructions.

That bounded collection of material and roles is the for the work.

Translate the look into camera decisions

During refinement, I asked for early-2000s hot-girl summer: a nostalgic photograph, Kodak Portra warmth, visible grain and chromatic aberration. We could keep the person and vehicle while changing the photographic language.

The DOP perspective turns that into consequences. A friend's waist-height camera with a slight tilt can make the frame feel casual. Warm sun and modest flash fill can keep skin and black paint readable. Texture, creamy highlights and fine grain support the intended film-memory treatment.

Chromatic aberration belongs to the lens treatment around contrasting edges. It is not caused by Portra film. Keep it restrained enough that the subject and truck still read. Each part of the look should have a reason to be there and an axis you can adjust.

The Raptor workshop
Follow the choice and its reason

The Raptor shoot, step by step.

Start with the brief, refine the look, keep continuity, and carry the selected still into motion.

Ari looks back beside the black Raptor in balanced warm daylight.

Set the briefReconstructed brief

Precomputed / Select a step to inspect its frame and the reason behind it. Add motion shows a still reconstructed from the completed walk test.

Reason
The original goal was posed photos of Ari around her original black Raptor: one woman and a recognisable truck.
Framing
Use a portrait frame without stretching the cab, wheels, and bed to fit.
Camera
Give the subject and the parked four-door truck room to read together.
Light
Leave the look open for refinement; the light serves the posed-photo brief.
Kept in every choice
  • One woman
  • One parked black Raptor
  • Consistent summer styling
Authored high-level recap using approved finished Raptor test outputs as references for new Higgsfield images. These precomputed reconstructions illustrate the choices, not the original version archive. Raw face references and the identity pack remain private. Generated frames cannot certify exact identity, markings or vehicle geometry.

The four steps in this illustration are establish the brief, refine the look, keep continuity and add motion. Each connects a reason to framing, camera and light using a saved frame. The clean-daylight and film views reconstruct a comparison from the finished test image. The wider view gives the cab, wheels and bed room. Add motion uses a still re-rendered from the completed walk test.

These are generated explanations, approved for use with my finished test images and generated likeness. They are not the original version archive and cannot certify exact identity, body art or vehicle fidelity. Clicking a step loads its saved image.

Other lenses ask different questions. Art direction considers environment and objects. Styling considers material, silhouette and colour. Continuity tracks what must stay recognisable. Editing considers how adjacent frames develop the idea. They are perspectives within the workshop, not autonomous departments the skill secretly launches.

Use choice, reason, consequence. Keep me in the foreground beside the closed front door: choice. Make it feel like a summer moment with my truck: reason. Retain the four-door cab, front wheel and bed without stretching them: consequence.

Technical language helps when it carries that relationship. Focal length, depth of field, diffusion, exposure and grain should describe a coherent frame, not decorate an unresolved one.

Keep evidence and proposals distinguishable

A short brief leaves gaps. Developing it means adding things. The workshop needs to show where each addition came from.

Vybe-Check uses four labels:

  • Supplied: explicit user information or an accepted reference role.
  • Inferred: a contextual reading that can be corrected.
  • Proposed: a creative addition offered for agreement.
  • Generated: material originating in an exploratory generated output.

In this case, the subject, Raptor and early-2000s summer direction were supplied. The casual friend-shot reading developed from that direction. Pink tank, low-rise denim, accessories and loose dark hair were styling proposals. They were not facts extracted from the private identity references.

A generated image can become a useful composition reference while remaining generated. Agreement changes whether we use the proposal; it does not change its origin.

For an addition, ask what it contributes. Does it clarify the action or establish a useful relationship? Does it fit the environment? What extra continuity problem does it introduce?

Let the conversation follow the unresolved work. With a partial brief, one focused question may change the image. With no useful detail, offer a coherent direction and a meaningful alternative. When creative choices are delegated, develop and explain them.

A complete brief with an explicit request for prompts already gives agreement to draft through the skill's direct path. Do not turn that into an unnecessary interview. The questions should earn their place.

Give a revision a bounded job

"Better" is difficult to review. "Keep the subject and truck, but loosen the pose and make the photograph feel more casual" tells the next version what to change and what to preserve.

That was the value of the summer-film correction. Later revisions could lower the camera, bring the truck forward or reduce edge fringing without discarding everything that already worked.

What came from where
Keep the source of a choice visible

Agreement changes the record.

Illustrative agreed baseline. Try a look proposal, then agree it to retain another example revision.

SUPPLIED

Ari and her original black Raptor, plus Ari's early-2000s summer film direction. The film request came from her.

INFERRED

A casual friend-shot reading followed from that intent. It remained open to correction.

PROPOSED

Camera distance, optional flash fill, and styling were proposals for expressing the supplied direction.

GENERATED

A study or generated frame supports the selected composition. It cannot prove exact identity or vehicle details.

Pending draft / Proposed treatment

Try the look refinement.

Ari looks back beside the black Raptor in balanced warm daylight.

Pending previewReconstructed brief

Warm summer light around Ari and her parked black Raptor. Keep a portrait frame with a recognisable cab, wheels, and bed.

The draft matches the latest agreed example revision.

Selected agreed example revision

Version 1

Ari looks back beside the black Raptor in balanced warm daylight.

Agreed previewReconstructed brief

Warm summer light around Ari and her parked black Raptor. Keep a portrait frame with a recognisable cab, wheels, and bed.

Retained locks

One woman. One parked black Raptor. Consistent summer styling.

Retained example revision history

  1. Warm summer light around Ari and her parked black Raptor. Keep a portrait frame with a recognisable cab, wheels, and bed.

    Locks: One woman. One parked black Raptor. Consistent summer styling.

A full-length walking pose with the black Raptor grille, four-door cab, wheels and bed in view.

Composition studyReconstructed continuity study

GENERATED

Exploratory composition study

Composition only. Cannot verify identity, vehicle geometry, or markings.

Precomputed Higgsfield study from the approved finished test still. Illustrative promotion keeps its generated source and limits.

Illustrative agreed baseline ready to inspect.

Kept in every choice
  • One woman
  • One parked black Raptor
  • Consistent summer styling
Authored provenance illustration with precomputed Higgsfield look comparisons. These condensed example revisions demonstrate a record; they are not the actual workshop version archive. Agreement changes the selected text and image together; it generates nothing on this page.

This replay uses authored look summaries and illustrative version numbers. Changing the look creates a pending proposal with a saved image. Agree revision appends that text and image as another version. You can inspect earlier text, images and anchors without erasing what came after.

The exploratory study is a precomputed Higgsfield composition example derived from the approved finished still. Promoting it keeps the Generated label and the composition-only limit. It does not become a supplied identity fact because you liked it.

That is what I want a live board to hold: current brief, pending change, accepted version and relevant references. The board gives disagreement a location. "This still reads as a campaign portrait" names a look mismatch. "The tall crop distorts the truck" names a geometry failure. Each gives the next pass something specific to resolve.

Add motion when it serves the idea

The agreed image can stand alone. For the Raptor demonstration, we also developed the walking-and-looking-back direction into a 15-second sequence, using the selected still as the motion anchor.

Now decide what changes over time. Subject, camera, environment, light and shot structure can each change. Each change also adds something to inspect for continuity.

The skill offers three ways to organise that development:

  • Preserve: a restrained continuous action within the established scene.
  • Evolve: a continuous scene with a more deliberate progression.
  • Multishot: distinct shots connected by shared anchors.
A still becomes a sequence
Continue the agreed intent through time

Choose what changes.

Same vehicle, outfit, and film look. Compare a continuous walk, a developing frame, and three shots.

Preserve

Total duration: 15 seconds

Keep the selected still as the starting composition for one continuous walk.

The original selected generated still: Ari looks back in a pink tank and denim beside the parked Raptor.

Start / Selected stillOriginal selected test still

Ari looks back with a small smile while walking beside the closed Raptor cab.

Middle / Walk and lookbackRe-rendered from walk test

Ari smiles beside the Raptor grille at the end of the walk.

Ending / Loose grinRe-rendered from walk test

Precomputed stills / The pictures illustrate the proposed sequence. The timeline below describes intended timing.

  1. to

    Camera

    Gentle camera follow beside Ari, holding the relationship to the truck.

    Action

    Ari walks beside the closed front door and looks back with a loose grin. The truck stays parked throughout.

Kept in every choice
  • One woman
  • One parked black Raptor
  • Consistent summer styling
Authored comparison with precomputed stills: the original selected test image, frames re-rendered from the completed walk, and proposed views generated with Higgsfield. These are static storyboards, not generated videos or evidence of provider timing. The comparison does not mean all modes ran.

The illustration compares authored 15-second continuations with three-frame storyboards. Preserve starts from the original selected test still and uses images re-rendered from the completed walk. Evolve and Multishot add proposed views to that continuity.

Preserve uses one continuous interval. Evolve and Multishot use three ordered five-second intervals. These are saved stills explaining proposed structures, not evidence that all three video modes were rendered or that a provider followed the timings.

The action was small: walk beside the parked Raptor's closed front door, then look back with a loose grin. A gentle camera follow lets that gesture develop while the vehicle stays parked and the summer look carries through.

Write the action, camera and time together. Name when the look-back happens and what the ending holds. Then inspect the output. A coherent walk can still drift in subject details or vehicle geometry. A timed prompt is a brief for the renderer, not proof of compliance. Sound belongs in the direction when requested; these examples leave it unspecified.

What the source candidate actually holds

The public candidate separates conversation from saved state. Its skill instructs a host agent in context gathering, choices and refinement. A Python runtime provides the board, validation, state and exports. The host supplies the conversational model and its data handling. The source discussed here is pinned to 85db053d4ce256bcff76564d03cd24077a53c2f6. Skill.

A session holds brief, choices, provenance, locks, image/video versions, pending drafts, studies and assets. Named actions have validated payloads. Callers request a particular change instead of submitting an arbitrary replacement session.

Propose, resolve choices and agree are separate actions. Ordinary agreement needs a proposed brief with no unresolved choices. The direct-image route accepts a complete explicit brief while gathering, establishes agreement and appends the image version. These are two supported routes, not a reason to impose the longer one on every user.

A mutation states the revision it expects. Under a write lock, the runtime rereads saved state and checks that revision. A mismatch raises a conflict, so two requests based on the same old state cannot silently overwrite each other through this interface.

Each file is written through a temporary file in the same directory, flushed and synced, then replaced atomically. Session and media-registry updates still span separate files. That is per-file atomic replacement, not a multi-file transaction. Workshop implementation.

Keep a draft attached to its parent

A browser draft records target, text, base revision and base version. The parent version matters because a user can select another image while a draft remains pending.

Accepting the draft appends a version from that named parent, retaining its settings, locks and provenance while applying the agreed text. Earlier versions remain inspectable and selection moves to the new one. Video drafts also keep their parent relationship.

Creating video starts from the selected agreed image version and records that source relationship. Its locks and provenance carry into motion alongside explicit mode, duration, action, camera and accepted settings. The runtime builds the prompt structure; the eventual renderer still needs checking. Runtime reference.

Those controls preserve structure and history. They do not decide whether the accepted words make a better image. That remains editorial judgement.

Export less than the whole workshop

The export includes an agreed image or video prompt with an allowed set of fields: prompt text, shots, settings, locks, version data and the relevant source-image relationship. You can name a version explicitly; the default is the latest, which need not be the image currently selected on the board.

The full session, private media-registry paths and reference bytes stay outside that export. Recognised credential and local-path patterns are cleaned from strings. That filter cannot recognise every identifying detail expressed as ordinary prose. Inspect what you share. Export implementation.

The board binds to loopback and serves registered media through opaque identifiers. Its URL gives access to the local session; loopback does not protect against a compromised account or other software acting as the same user. Saved sessions are ordinary local files, not automatically encrypted storage.

Give optional tools a narrow job

The core workshop needs no API key. Optional local image studies use a configured loopback ComfyUI service after inspecting its checkpoints and installed nodes. The supported graph is restricted to an allowed core workflow; unknown nodes refuse.

That graph uses text conditioning. Registered identity or object references are not silently fed in as conditioning images, so a study cannot certify their exact reproduction. It can explore framing, light and colour while keeping its generated provenance visible. Loopback alone does not establish what third-party software does with the input.

Optional Jev advice is a different operation: assess a bounded question and its options. The intended advice writes no prose, accepts no draft, changes no agreed prompt bytes or locks, and submits no generation.

Both Jev advice routes are unavailable in this pinned candidate. The primary-billing-bounds function returns no verified bound, so direct TypeSafe and OpenRouter paths refuse with billing_unbounded before reading credentials or calling transport. Current provider prices do not unlock that implementation. Judge source.

The route's prerequisites still matter: inspect outbound strings for anonymity, obtain explicit bounded approval, establish current billing bounds and a user-selected ceiling. Credentials use an explicit native-store adapter that can be denied or unavailable; plaintext fallback is refused. Windows credential roaming depends on the account and organisation policy, so it needs host-specific checks. Privacy and optional services.

Source inspection does not establish successful installation or native-store behaviour on a particular machine. The pinned candidate's 75 active independent/native acceptance criteria remain open. It provides no paid image/video submission command; prompts can be copied to the user's chosen tool. Verification contract.

Carry an explainable decision forward

Start with the outcome and visual priority. Give references roles. Establish the anchors. Develop relevant proposals, then retain what was agreed as you refine.

The practical test is whether a later version can explain what changed, why it changed and what it kept. Continue into motion only when that serves the idea.

The Creative Direction Worksheet gives one image a starting brief and one revision a clear target. The agent context pack carries the method, and the public source candidate contains the implementation described here.

[ comments ]

guests welcome. members show first in the list

no comments yet. start the thread_

1 / 13