Records without a category

Abstract

A host-agnostic architecture for a desktop AI companion. State and logic live in a local server while the web page only renders, allowing a browser, a borderless pywebview/WebView2 window, and Lively wallpaper to act as interchangeable skins. Three infrastructure battles follow: speech recognition moved server-side because a wallpaper host could not interact with native permission UI, bringing local whisper transcription and deadline-based echo suppression; audio playback moved to the server because the wallpaper process was frozen by its host; and global shortcuts moved from conflicting system combinations to a macro pad emitting F13–F19, followed by three separate debounce repairs. Two environment traps are also recorded: logging under a Japanese locale crashed a feature path, and missing CUDA libraries appeared only at first inference.

Abstract

A record of building an independent dialogue engine for an AI companion. The central decision was that a relationship should not use a multi-session model: one continuous timeline feeds four memory layers—recent verbatim context, context-separated rolling summaries, editable long-term notes, and a full archive with per-turn retrieval. The main failure was a style infection in which one phrase appeared eleven times in twenty replies and was then preserved by the summariser as long-term personality. The article traces three layers of reinforcement—examples in the window, self-imitation, and summary consolidation—explains why instructions lose against examples already in context, and gives a mechanical repair: summary surgery, summariser constraints, generation guards, and an on-demand context cut. A fast model handles conversation while a stronger reasoning model performs latency-insensitive memory compression in the background.

Abstract

A first-person record of a digital-companion system from first impulse to working whole: why it began, where it met hard limits, how the direction changed, and when the project left its upstream foundation to become independent. Five linked technical records cover lip-sync tests, content isolation, host architecture, memory, and a controlled selfie system. The account follows contemporaneous work notes rather than polishing the process in hindsight.

Abstract

A design record for an AI companion's selfie behavior. The central idea is layered authority: the model reads the conversational atmosphere—at home, late at night, outdoors, and so on—while outfits are sampled from a manually maintained pool filtered by that atmosphere. She reads the room; you stock the shelf. Expressive freedom and the upper content boundary belong to different actors. The outfit engine combines shot types, ten slots, exclusion groups, and whole-outfit replacement rules, then validates them through hundreds of randomized trials. The post examines three failures: an image endpoint silently ignored a reference-image parameter despite returning 200 twice; a caption claimed a composition that contradicted the sampled shot; and praise triggered an endless stream of follow-up photos. The fixes were the correct endpoint, shared composition and expression parameters, and a narrow rule that blocks praise-triggered repetition without removing proactive sharing.

Abstract

A design and validation record for a two-context isolation mechanism. Normal and private modes each hold separate persona additions, rolling summaries, and long-term memories. When normal mode reads history, every private segment becomes one constant bridge placeholder. The article explains the fail-closed valve—boot and every failure land on the normal side, entry requires verification while exit does not—the information argument for constant placeholder text, and crash recovery for an open segment. It also analyses three failures: a silently blocked cross-origin request meant isolation never activated while mocked tests stayed green; double trimming erased context every turn; and prefix deletion removed legitimate history on the same side. Twenty-two regression checks protect the final semantics.

Abstract

This article records a failed generation experiment and the statistical review that could have anticipated it. To build a dependable action-shot pipeline, the author examined five complete, publicly released video workflows, extracting 231 video nodes and 228 prompts to classify input modes, reference-image counts, and action language. Attack verbs appeared in 18% of prompts and two-subject interaction in 6%, yet prompts describing physical contact between characters appeared zero times: the five apparent contact cases were deliberate non-corporeal penetration or collisions between a character and the environment. Ten generations of a two-character combat shot then addressed seven repeatable failure modes—turn-based staging, style collapse, anatomical drift in non-human subjects, reference-locked distance, broken action causality, idle waiting, and unnecessary endings. Only the causal credibility between attack and evasion never held, and the experiment was stopped. The article also records two methodological conclusions: sampled-frame grids are systematically unreliable for judging generated video, and adding more documentation does not solve the failure to retrieve conclusions already on record. Statistics, observations, and inferences remain distinct throughout; the claims are limited to the tested models and the time of writing.

Abstract

This article documents the construction of a keyframe-to-animation pipeline for a painterly animated pilot. It begins with a reversal in production logic: image models are difficult to control while the script is completely editable, so the storyboard should adapt to strong generated images instead of repeatedly spending generation budget on a fixed composition. It records the failure that forced this change and the revised storyboard structure, which specifies beats and red lines rather than composition. It then identifies three repeatable prompt failures: unspecified body parts are filled in, mentioned objects appear even when negated, and some spatial constraints cannot coexist from any camera angle. Finally, it measures texture retention across two image-to-video paths. Using Laplacian response to separate flat-surface texture from contour sharpness, the two paths retain 76% and 39% of the keyframe's surface texture. A post-production correction matches the metric exactly but fails visually. Observations, measurements, and inferences remain distinct; the pipeline is still unfinished.

Abstract

After the previous AI action film was archived as a failure, this article records a Claude Fable 5-driven greenfield restart on the same platform. No prior assets were carried over; the task was reduced to a three-shot atmospheric film within the models' capability boundary, with no physical contact or combat causality. It tests a new division of labor: the creator produces the keyframes in Midjourney, Flova and Seedance handle orchestration and animation, and Claude Fable 5 drives the official CLI and extracts frames for review. The article follows three lines of failure and correction: a helmet hallucinated because the first frame lacked structural information, a text-only silhouette entrance rebuilt as an impact shot, and thick-painted imagery becoming synthetic in motion before MJ Animate offered a better route. It also records the final decision to delete a shot because of character drift. The finished film runs 14.2 seconds, consumed 838 credits, and produced seven reusable rules.

Abstract

This article records the complete production of a 15-second dark-fantasy film driven by Codex 5.6 Sol, from greenfield planning to final export. Codex 5.6 Sol supplied Flova with Niji concept art for the knight and Sylas; the platform planned a five-shot storyboard, generated character and environment Key Elements, and completed two rounds of shot generation, while external frame review, sound design, and timeline assembly closed the process. The workflow respected staged gates and avoided complex combat, but only two restrained single-subject shots earned strong evaluations. Sylas appeared without credible spatial logic, platform-generated weapons and characters looked synthetic, reruns failed to correct travel direction and identity markers, and the final shot had to be replaced by a still. Treating the creator's per-shot scores as the final record, the article explains why a new project, a complete workflow, and a successful export do not make a film successful, and compares the result with a Claude Fable 5 route built around human-authored Midjourney keyframes.

Abstract

This test did not treat a successful export as success. A four-shot action film had to preserve story, space, physical contact, character identity, visual style, and sound continuity at the same time. Flova correctly diagnosed the earlier phantom-distance problem, built a directing plan and timeline, and used Seedance 2.0 to deliver a 38.24-second film with native sound. Gate B, however, repeatedly introduced a knight's helmet on the Boss, premature chest contact, duplicated weapons, and wholesale style drift. In the final sequence, Shot 2 still failed to prove a knee strike, while Vera's identity and lantern hand remained unreliable in Shot 4. More importantly, Flova repeatedly marked these defects as passes. This article records the complete failed workflow from director audit to export, and explains why project-level orchestration still cannot replace independent frame-by-frame review.

Abstract

The goal sounded modest: a 16:9 battle in which a knight evades and counters a stone giant, defeating it before Vera arrives. The visual language stabilized quickly; time and space did not. Early versions dodged too soon, paused before attacking, collapsed floors without a cause, teleported characters, and left the Boss floating. Reducing the task to one five-second action gave Dreamina a clear advantage over Kling, but the continuation introduced a deeper three-dimensional error: the knight was visibly far from the Boss, stood up in place, and somehow struck it. A static contact sheet even made the shot look usable. Rather than force the material into a finished edit, this test preserves the failures, assigns clean single-subject generation to Niji and controlled assembly to Image2, and pauses manual shot-by-shot production while Flova is evaluated as a project-level system for storyboards, shot coordination, and model selection.

Abstract

This was not an attempt to move an entire Godot project into a website. It extracted one minimal, complete, verifiable combat loop from Watchman: a fixed character and fixed values, with movement, jumping, attacks, evasion, poise, stance breaks, and executions. The record covers an explicit asset allowlist, behavioural contracts, collision and hit detection, input buffering, audio and damage numbers, followed by Web packaging, real loading progress, keyboard focus, mobile fullscreen, and contextual-input revisions. Several failed iterations established two rules: combat feel cannot be approximated in a rewrite, and web controls cannot simply copy the main game. Both have to be calibrated against their real operating environment.

Abstract

A company website rebuild is more than a page-design exercise. This article divides the work into seven stages—requirements, stack, content, localization, deployment, domain and filing, and asset handoff—and explains how to choose between static and dynamic architecture, handle forms without a conventional backend, decide where to host, and keep the domain, DNS, hosting account, and source code under company control.

Abstract

Customer orders rarely arrive in one format: a short message, a spreadsheet, a photograph of a quotation, or a scanned document. This note describes an intake tool that uses a multimodal model to turn those inputs into structured order records in a shared online table. The important part is not the code but the reliability contract: every extracted field is marked certain or uncertain; uncertain values remain empty for a person to resolve; a confidence gate chooses between automatic writing and an explicit review card; and the model handles repetitive interpretation while a person retains final judgment. Technical terms are introduced in plain language for readers new to automation.

Abstract

Alias Archive grew from a thin personal-site skeleton into a trilingual archive spanning research, games, music, and work that resists those categories. This article explains the move from Next and vinext to Astro, the repository contracts used to coordinate multiple agents, the role Impeccable played in refining hierarchy and responsive behaviour, and the way articles, images, audio, video, and a Godot Web demo coexist inside a static site. The durable subject is not a tool list, but a system that remains portable, testable, and controlled by its owner as it grows.

Abstract

This is not a one-click-generation demo. Codex served as the only operational interface and coordinated the script, scene plan, API work, visual package, and review. HeyGen supplied Vera's English voice, lip sync, and base performance; HyperFrames supplied Chinese subtitles, information hierarchy, and the 9:16 master. The process exposed failures in avatar reference selection, vertical typography, face-safe layout, preview reliability, background continuity, and speech cadence. The first sample was accepted with two disclosed imperfections so the next production can correct them at the source.

Abstract

This entry divides an AI music video into eight stages: song, directing plan, stills, selection, animation, review, color, and release. Image prompts own appearance while video prompts describe motion only; animation tiers, filmstrip quality control, and anchor-based color matching then contain cost and inconsistency. Models perform production labor, while style, shot selection, and final acceptance remain human decisions.