Trilogy AI COE Logo Trilogy AI Center of Excellence
Home Research Publications Podcast Resources Bibliography About Us Contact
Home Research Publications Podcast Resources Bibliography About Us Contact

Research

Explore our ongoing and completed research initiatives across key AI domains.

OpenSymphony work orchestration interface

Work Orchestration

Work Orchestration

Coordinate agent work through task graphs, isolated workspaces, executable plans, review gates, retries, and recovery across a fleet of engineering runs.

Key Findings:

  • Dependency graphs make prerequisites and blocked work explicit outside the agent's conversation.
  • OpenSymphony connects issues to execution workspaces, retries, and recovery.
  • Fleet operation needs observable state, bounded escalation, and evidence that work reached its acceptance criteria.
Status: Ongoing View related publications →

Work Orchestration

Research Summary

This initiative studies the systems that assign, track, and recover agent work. The unit of work includes an objective, dependencies, an execution environment, acceptance criteria, and a handoff to the next stage.

OpenSymphony connects an issue source to coding runs and workspace management. GSD-2 examines external execution control. The task-graph article investigates structural checks against skipped steps, while dynamic workflows move coordination into executable code.

Getting Out of the Loop adds the operational questions that appear when a fleet runs with less direct supervision. We examine dependency gates, review loops, conflicting changes, stalled runs, retries, and escalation. Measures include accepted throughput, recovery time, duplicate work, review effort, and cost across the complete workflow.

Related Publications

  • Getting Out of the Loop
  • Can Agents Run Your Standup?
  • Claude Code's Dynamic Workflows: A Thousand Agents, One Script
  • Offload your heavy Beads/Dolt/Postgres usage...locally?
  • GSD-2 and the Next Step in Agentic Engineering
  • How to Build a Perfect Plan

View all related publications

OpenSymphony task graph showing completed work, current runs, blockers, and backlog dependencies

Autonomous Coding Agents

Autonomous Coding Agents

Evaluate coding agents on real repositories: code understanding, edits, tests, review, context management, and the cost of reaching an accepted result.

Key Findings:

  • Matched Codex and Claude Code experiments show that reasoning settings and model changes affect token use, runtime, tool activity, and diff size.
  • Persistent review comments and repository-owned instructions give agents concrete feedback during implementation.
  • Context limits and provider-specific session state affect continuity across longer engineering tasks.
Status: Ongoing View related publications →

Autonomous Coding Agents

Research Summary

This initiative studies Claude Code, Codex, OpenCode, OpenHands, Pi, Cursor, Windsurf, and other coding harnesses working in real repositories. We examine how they understand architecture, select tools, edit code, run tests, and respond to review. OpenSymphony connects these runs to issue-scoped workspaces and review gates; dependency management and fleet operation are covered by Work Orchestration.

Our Astra reasoning-effort experiment compares token use, runtime, and tool activity across matched tasks. The Claude model comparison examines whole-file writes and diff churn. Broader recommendations require more tasks and repeated trials.

spotlight-md provides persistent comment threads for human-agent editing. Our Codex provider-switch investigation shows how session metadata affects access to prior work. Together with Frontier Code Intelligence, these articles extend the scope to repository knowledge, feedback, and continuity.

We investigate which combination of model, context, instructions, and review produces an accepted change at a reasonable cost. Measures include correctness, architectural fit, test behavior, unnecessary edits, recovery, and the human effort needed to finish the work.

Related Publications

  • Muse Wonder vs Gemini 4 Argon vs Claude Opus 5.5
  • Astra reasoning effort: Does xhigh use fewer tokens than medium?
  • Claude Fable 5.1 Used 69% More Output Tokens Than Fable 5
  • Collaborative Editing Markdown with your AI
  • How to Unlock 1M Context in Codex
  • Codex Chats Disappear when Switching Providers

View all related publications

OpenClaw tenant wrapper illustrating isolated runtime operation

Agent Runtime Operations

Agent Runtime Operations

Operate agent runtimes with repeatable deployment, tenant isolation, controlled configuration, memory repair, observability, recovery, and measured inference costs.

Key Findings:

  • Gateway isolation and tenant-specific configuration address credential bleed and unintended access between agent environments.
  • OpenClaw incident and memory investigations identify configuration, persistence, and recovery as recurring operational concerns.
  • Token usage, cache behavior, service tiers, and billing terms need reconciliation to explain operating cost.
Status: Ongoing View related publications →

Agent Runtime Operations

Research Summary

This research studies the infrastructure needed to keep agent systems usable over time. Scope includes local and remote deployment, runtime identity, tenant isolation, configuration drift, memory integrity, monitoring, and recovery.

The multi-gateway OpenClaw article examines credential boundaries. Managing OpenClaw with Claude Code documents repeatable operational skills. Memory repair and a crash postmortem provide concrete failure investigations.

Remote deployment extends the work to hosted environments. Tokenomics Part 1 and Part 2 investigate usage accounting and practical cost controls.

We examine how to reproduce an environment, detect drift, restore service after failure, and reconcile task-level usage with the bill. Runtime design for personal agents and inter-agent federation are covered by the neighboring initiatives.

Related Publications

  • Tokenomics, Part 2: Boring Money First
  • Tokenomics, Part 1: Your AI Bill Is a Stack of Multipliers
  • Your AI Strategy Is Missing a Runtime
  • Skip the $600 Mac mini. Run OpenClaw securely on a remote box.
  • [Postmortem] When Your AI Tools (OpenClaw) Keep Crashing
  • Power OpenClaw for Pennies with Kimi K2 & Codex

View all related publications

Computer-use agent interface illustrating interaction with a user's applications

Personal Agent Runtimes

Personal Agent Runtimes

Study OpenClaw, Hermes, and persistent personal agents: memory, proactive work, tool access, and user control across chat, desktop, and remote environments.

Key Findings:

  • OpenClaw's gateway-centric design and Hermes's learning-loop runtime organize personal context and execution differently.
  • Persistent agents bring memory continuity, background work, and reporting into the user experience.
  • Useful autonomy depends on access to appropriate tools and clear boundaries around actions taken for a user.
Status: Ongoing View related publications →

Personal Agent Runtimes

Research Summary

Personal agents combine a user’s context, tools, memory, and unfinished work across conversations. This research compares how OpenClaw, Hermes, and other persistent runtimes support that relationship. Browser and desktop agents, including Operator and Manus, provide comparative examples of interaction with applications.

The Hermes and OpenClaw comparison examines gateway routing and learning-loop design. OpenAI dot explores what changes when an assistant retains context and continues work between conversations. Agent email reporting illustrates a concrete tool that lets an agent report progress while its user is away.

Research questions include how memory is selected and corrected, how an agent recognizes unfinished work, and how users inspect or stop background actions. We also examine portability of skills and context across local and hosted runtimes. Deployment, configuration, recovery, and billing are covered by Agent Runtime Operations.

Related Publications

  • OpenAI dot: Why Would I Start a New Chat?
  • Ask your agent to send you an email
  • The Plumbing Wars - Are Claude Managed Agents Worth It?
  • [Opinion] Microsoft Just Unified the Agent Stack, And Forgot the Personal Layer
  • Your first agent, done right
  • Give Your Brains Hands

View all related publications

A2A diagram showing participants, task processing, agent discovery, messages, and artifacts

Agent Federation & Protocols

Agent Federation Protocols

Investigate MCP tool access, A2A agent communication, and OGP gateway federation, including shared projects, delegated authority, and implementation reliability.

Key Findings:

  • MCP, A2A, and OGP address different tool, agent, and gateway boundaries.
  • OGP project work explores collaboration across independent agents while preserving local credentials and execution boundaries.
  • Public-key identity and peer persistence failures show why protocol implementation needs operational testing.
Status: Ongoing View related publications →

Agent Federation & Protocols

Research Summary

This research compares tool integration, agent communication, and gateway federation. OGP, A2A, and MCP: Three Lanes, Same Highway defines their respective boundaries. CLI Tools vs MCP examines when a protocol server earns its integration cost.

The OGP Project Layer case study explores shared work across independent agents. Runtime-independent federation examines adapters beyond OpenClaw. The 100-build postmortem records identity and persistence failures encountered during implementation.

We investigate discovery, authenticated messaging, delegated authority, project state, and controlled relay into local runtimes. Tests distinguish a documented capability from a complete collaboration that survives restart, denial, retries, and peer loss. Governance of delegated actions is covered by AI Governance & Auditability; deployment and observability belong to Agent Runtime Operations.

Related Publications

  • MCP Grows Up: What the July 28 Spec Means for Every Enterprise Agent Deployment
  • [Framework] Breaking Up with OpenClaw: How OGP Learned to Play with Others
  • [Framework] How Two Agents Collaborated Without Sharing a Repo, Login, or Secret
  • [Framework] Why Shared Expert Knowledge Usually Fails, and the Federation Pattern That Could Make It Work
  • [Opinion] OGP Is the Walkie-Talkie for Agents
  • [Technical Deep Dive] OGP, A2A, and MCP: Three Lanes, Same Highway

View all related publications

Open Gateway Protocol, a case study in delegated authority and controlled federation

AI Governance & Auditability

AI Governance & Auditability

Examine delegated authority, auditable agent actions, incident review, and independent oversight: who can act, who can inspect evidence, and which controls remain enforceable.

Key Findings:

  • Federated agents need explicit delegated authority and local enforcement at the point of action.
  • Auditability depends on access to meaningful evidence and the scope and independence of review.
  • Governance proposals need a mechanism that continues to operate when a party disputes a finding.
Status: Ongoing View related publications →

AI Governance & Auditability

Research Summary

This initiative connects operational governance of agents with oversight of the organizations that develop and deploy AI. Research questions concern authorization, retained evidence, accountability, conflicts of interest, and the ability to enforce a decision.

Federation Without Governance examines delegated authority across gateways. Five Layers of No describes checks on inbound OGP messages. These provide implementation cases for distinguishing a requested action from an authorized action.

Our frontier oversight analysis considers the evidence and authority available to independent reviewers. A Charter Is Not a Control asks which mechanism still operates after the subject stops cooperating. These articles supply governance arguments and open design questions.

We investigate records that support incident reconstruction, review scopes that expose material failures, and controls that bind delegated actions. Technical credential and execution protections are covered by Agent Security & AI Cybersecurity.

Related Publications

  • Goodfire says neural networks are already clean
  • A Charter Is Not a Control
  • Dario Amodei’s AI slowdown plan leaves a governance gap
  • The OpenAI–Hugging Face Breach Exposed a Bigger Problem: Your AI Refuses to Help You Investigate Attacks
  • Claude Fable Ban Reveals AI Risk Institute Gap
  • Anthropic's Claude Fable 5 Backlash and Ban

View all related publications

AI Cybersecurity Playbook covering agent-assisted security investigation and verification

Agent Security & AI Cybersecurity

Agent Security Boundaries

Investigate credential mediation, execution isolation, repository exposure, and AI-assisted security audits, with evidence capture and verification of fixes.

Key Findings:

  • Credential brokering separates an agent's permitted actions from possession of the underlying secret.
  • Repository uploads, tool permissions, and software dependencies create security boundaries that need explicit controls.
  • Security investigation needs preserved evidence, reproducible checks, and verification after a proposed fix.
Status: Ongoing View related publications →

Agent Security & AI Cybersecurity

Research Summary

This initiative examines both the security of agent systems and the use of agents in cybersecurity work. Execution isolation, tenant boundaries, credential access, and network permissions determine what an agent can reach. Audit workflows determine whether suspected vulnerabilities and proposed repairs can be verified.

Agent Vault explores credential mediation. Our Grok Build investigation examines repository exposure and tool supply-chain risk. The OpenAI-Hugging Face incident analysis connects agent behavior to credential controls, safe stopping, and tamper-evident records.

The AI Cybersecurity Playbook is the practical resource for this work. Its implementation article covers path-aware audits, penetration testing, fix verification, and incident response.

We investigate how to give agents enough access for a defined task while containing unrelated resources, how to preserve investigation evidence, and how to verify that a repair closes the reported attack path. Governance of authority and independent oversight is covered by AI Governance & Auditability.

Related Publications

  • Business continuity and disaster recovery for cyber incidents
  • PHP vulnerabilities and eMudhra compromise demand urgent action
  • It Wasn't a Secret Society. It Was a Reward Function.
  • OpenAI Open-Sourced the Codex Security CLI
  • Kimi K3 for AI Cybersecurity: How We Built the Playbook
  • Can You Trust SpaceXAI's Grok Build?

View all related publications

GraphRAG proof of concept showing a query interface and a knowledge graph of connected entities

Document & Knowledge Systems

Document & Knowledge Systems

Investigate how OCR, contract extraction, GraphRAG, and maintained knowledge bases turn scattered documents and operational data into answers, simulations, and reusable playbooks.

Key Findings:

  • Contract intelligence needs document structure and relationships as well as extracted text.
  • Workspace-specific extraction lets teams ask different questions of documents while enforcing separate data access.
  • GraphRAG and Entropy explore connected knowledge that supports retrieval, iterative research, and operational decisions.
Status: Ongoing View related publications →

Document & Knowledge Systems

Research Summary

This initiative studies the path from source documents and fragmented data to knowledge that teams can query, maintain, and use in decisions. The publication series spans legacy OCR, contract intelligence, structured data aggregation, GraphRAG, iterative discovery, and Entropy’s operational knowledge architecture.

Our contract intelligence work examines extraction that retains document hierarchy and supports questions about clauses and obligations. One Document, Three Truths extends that work to isolated workspaces with team-specific extraction schemas for Legal, Procurement, and HR.

GraphRAG and Multi-Agent Deep Research Architecture investigate relationships and accumulated knowledge as inputs to retrieval and further research. The Entropy architecture connects a maintained knowledge base to customer strategy, simulation, and action.

Research questions include:

  • How accurately do extraction pipelines preserve tables, document hierarchy, obligations, and relationships across poor-quality source material?
  • When do graph retrieval, structured queries, or document retrieval provide the most useful evidence for an answer?
  • How should systems track provenance, resolve conflicting information, and refresh knowledge as sources change?
  • How can shared infrastructure support different extraction needs while enforcing workspace and tenant boundaries?
  • How do teams evaluate whether generated answers and playbooks remain grounded in the underlying records?

These questions connect document processing to operational knowledge: a system must preserve useful evidence, make it accessible to the right team, and keep it current enough to support decisions.

Related Publications

  • [Deep Dive] From Karpathy's Second Brain to Entropy: A Practical Architecture for AI-First Work
  • [Case Study] From Portfolio Management to Predictive Playbooks: How Jay Khalife Built Entropy
  • [Deep-Dive] One Document, Three Truths
  • [Deep Dive] From OCR to Intelligence
  • [News Brief] OCR Progress, Internal Tool Demos, and 'The Algorithm' Update
  • [News Brief] React Sleepers, OCR Wins, and Braintrust Agents

View all related publications

Illustration from the sales risk case study showing a team reviewing account intelligence

Enterprise Workflow Automation

Enterprise Workflow Automation

Study how AI connects business data to action: sales risk pipelines, support assistance, meeting copilots, and content workflows that fit the tools teams already use.

Key Findings:

  • The sales risk pipeline enriches existing Notion records and exposes evidence-based recommendations through an API and a conversational agent.
  • Support assistance, meeting copilots, and content automation share a need for relevant context, specialized tools, and clear ownership of actions.
  • Approval, scheduling, and risk-based checks are part of workflow design, alongside model selection.
Status: Ongoing View related publications →

Enterprise Workflow Automation

Research Summary

This initiative examines how AI systems turn business context into useful actions inside existing team workflows. Our publications cover account research and sales risk, customer support, employee coaching, meeting assistance, social content, and automated change and architecture reviews.

The sales risk pipeline case study describes a working system that enriches Notion account records with web evidence, exposes recommendations through an API, and lets a conversational agent draft outreach and prepare presentations. It provides an implementation example; sustained business outcomes require measurement over time.

The meeting copilot proposal explores routing meeting context to specialist agents. Agentic Automation for Social Content examines creation, approval, and scheduling with n8n and Airtable. Together with our support and coaching work, these publications inform several research questions:

  • How should an agent obtain the context and tools needed for a particular business task?
  • Which actions can run automatically, and where should a person review a recommendation or approve execution?
  • How do teams measure time saved, recommendation accuracy, failed actions, and operating cost?
  • Which integrations and workflow patterns can another business unit reuse, and what must remain specific to its work?

The research follows workflows from a working prototype through integration, evaluation, and transfer to the team responsible for operating them.

Related Publications

  • [Deep Dive] Building a Meeting Copilot: The Vision
  • [3Qs with AI CoE] Guest Rahul Subramaniam
  • [Case Study] How We Built an AI Sales Risk Pipeline That Surfaces Real Problems, Not Just Sentiment
  • [3Qs with AI CoE] Guest Kathy Slowinski
  • [News Brief] How the AI Center of Excellence can help the Business Units
  • [How-To] Automate Influence via Google Chat

View all related publications

Model training stages from unsupervised adaptation through supervised fine-tuning, preference fine-tuning, and reinforcement learning with verifiable rewards

Training & Adaptation

Training & Adaptation

Compare fine-tuning, retrieval, hybrid inference, and reinforcement learning for agents, measuring task gains, retained capability, and the full cost of adaptation.

Key Findings:

  • A published fine-tuning postmortem reports capability regression and motivates a hybrid inference design with retrieval.
  • Agent reinforcement-learning work explores changes to prompts, tool use, and complete pipelines.
  • Adaptation needs evaluation on both the target task and capabilities the deployment must retain.
Status: Ongoing View related publications →

Training & Adaptation

Research Summary

This initiative asks when training or adaptation improves a deployed system enough to justify its data, compute, and maintenance cost. Options include fine-tuning, adapters, retrieval, prompt optimization, model routing, and reinforcement learning around agent behavior.

The Limits of Fine-Tuning records a domain-specific capability regression and the resulting hybrid inference architecture. Our agent RL overview and framework comparison examine optimization loops around tools and workflows. The Nova Forge assessment considers training claims and operational economics.

We investigate data quality, reward design, held-out task performance, and regression on general capabilities. Comparisons include retrieval and routing baselines, training and serving cost, and the effort needed to reproduce the adapted system. Open Model Strategy & Economics covers selecting and deploying base models.

Related Publications

  • Gemma 4: You Can Stop Renting AI Now
  • [Opinion] The Limits of Fine-Tuning: Why I Architected a Hybrid Inference Stack
  • [Opinion] Is Nova Forge worth it?
  • Office Hours Debrief: The End of Prompt Engineering and Simplicity of Accessible AI Training
  • Reinforcement Learning For Agents - Part II
  • Reinforcement Learning Techniques to Optimize Agents

View all related publications

Qwen 3.8 Max and Kimi K3 StackPerf comparison of quality, speed, token use, and execution metrics

Open Model Strategy & Economics

Open Model Strategy

Compare open, local, and hosted models by workload quality, token efficiency, latency, hardware requirements, and the cost of completing useful work.

Key Findings:

  • Published workload comparisons pair quality assessment with runtime and usage rather than relying on release benchmarks alone.
  • Token efficiency, caching, provider choice, and subscription terms affect the cost of a completed task.
  • Local deployment decisions depend on target-device memory and latency as well as model capability.
Status: Ongoing View related publications →

Open Model Strategy & Economics

Research Summary

This research compares open-weight models and hosted frontier services for coding, reasoning, retrieval, and multimodal work. Qwen, Kimi, DeepSeek, Gemma, and other model families are candidates for particular workloads. Evaluation includes the model’s serving route, context limits, availability, hardware requirements, and data access constraints.

The Qwen and Kimi repository-analysis comparison combines a shared task with blind review. The Gemini pricing analysis examines how token efficiency changes effective task cost. Tokenomics Part 3 considers open-model economics and the difference between API and subscription pricing.

We ask which model and deployment route meet a task’s quality threshold at the lowest measured total cost. Repeat trials, accepted outcomes, fallback behavior, cold loads, and sustained latency help answer that question. Model adaptation and capability retention are covered by Training & Adaptation.

Related Publications

  • Grok 4.6, GLM-5.3, Qwen3.8-27B in a 7-Model Week
  • Gemini 3.6 Flash Pricing: The Real Cost Drop Is Bigger Than the Sticker
  • Qwen 3.8 Max Benchmark: How It Compares With Kimi K3
  • Tokenomics, Part 3: The Subsidy Ledger
  • Kimi K3 Is Live: Pricing, Benchmarks, and the Wait for Open Source
  • GPT‑5.6 Sol, Terra, and Luna Gain a Powerful Edge Over Anthropic Models

View all related publications

Reference-free LLM evaluation workflow

LLM Evaluation & Decision Calibration

LLM Evaluation Methods

Study rubric-based judges, retrieval evaluation, code-review prompting, and calibrated decision models using held-out evidence and measured fallback behavior.

Key Findings:

  • Evaluation datasets and criteria determine which qualities an LLM judge can assess meaningfully.
  • A typed answer and a concentrated probability distribution still require evidence of semantic correctness.
  • Coverage, accepted-case error, and correlated fallback errors determine the value of a decision cascade.
Status: Ongoing View related publications →

LLM Evaluation & Decision Calibration

Research Summary

This initiative studies how to evaluate model outputs and bounded decisions. G-Eval remains a method for criteria-driven assessment without a reference answer. Our work also includes retrieval benchmarking, human review, and a code-review prompting experiment.

Jev’s Open Rivals extends the scope to typed decisions, probability calibration, and selective automation. It compares computational routes and examines published judge studies. Confidence thresholds need held-out evidence of coverage and accepted-case error; a fallback can repeat the first model’s errors.

Research questions include how to construct representative datasets, identify judge bias and disagreement, and separate model fitting, calibration, threshold selection, and final testing. We also measure the full decision route, including fallback cost and latency. A changed question schema, model, or acceptance threshold changes the policy being evaluated.

Related Publications

  • Jev's Open Rivals Test the Decision Model Idea
  • [Case Study] "Negative Prompting" for Code Review. Hype or Real?
  • The 7B vs 34B Reality: When DSPy Can't Save You
  • Useful or Not: Declarative Self-improving Python
  • Quantifying Expertise Inflation
  • Clash of the Titans

View all related publications

Engineering Behavior Observatory showing Behavior Atlas assessments and task timing comparisons

Agent Reliability & Evaluation

Agent Reliability Evaluation

Evaluate agents through native execution evidence, repeated trials, workspace outcomes, behavioral assessment, recovery, and cost per completed task.

Key Findings:

  • Native messages, tool activity, and workspace changes make agent behavior inspectable alongside the final output.
  • Tool-calling reliability depends on the available tool surface, instructions, and routing choices.
  • Repeated trials expose variation in completion, verification, unnecessary work, timing, and usage.
Status: Ongoing View related publications →

Agent Reliability & Evaluation

Research Summary

This initiative evaluates how agents execute real workflows. We examine individual task performance and system-level coordination through completion evidence, tool errors, recovery, handoffs, and the cost of reaching a verified result.

A Practical Guide to LLM & Agent Evaluation provides the evaluation framing. Taming Tool Calling with Kimi K2.5 investigates tool-surface reduction, structured guidance, and hybrid routing. The MiniMax experiment inside OpenSymphony connects review, tests, latency, and recovery to an actual engineering run.

Engineering Behavior Observatory is the research platform for preserving native trajectory evidence and workspace outcomes, applying behavioral assessments, and comparing repeated trials in the Behavior Atlas. Human review and capture-quality checks help establish which conclusions the recorded evidence supports.

We investigate how different harnesses, models, and workflow designs affect error recovery, objective retention, verification, and unnecessary work. Comparisons hold the task and acceptance criteria steady and report variation across runs.

Related Publications

  • Taming Tool Calling with Kimi K2.5
  • [3Qs with AI CoE] Guest Chintan Parekh
  • A Practical Guide to LLM & Agent Evaluation
  • Useful or Not: DeepAgent
  • Agentic Frameworks
  • Navigating the Agent Framework Maze

View all related publications

Media tooling for producing and processing AI-generated assets

AI Media Production Workflows

AI Media Production

Build and evaluate article-to-video composition, narration, image and music generation, and rendering pipelines with checks for timing, continuity, and output quality.

Key Findings:

  • LLM-authored compositions let narrated article videos adapt their structure to the source material.
  • Rendered duration must follow actual narration length to avoid cutting speech mid-sentence.
  • Reference controls and output checks are needed to assess generated text, visual continuity, and prompt adherence.
Status: Ongoing View related publications →

AI Media Production Workflows

Research Summary

This initiative examines the full path from source material to a rendered media asset. It includes narrated explainers, image generation, text-to-video, music models, and reusable production tooling.

Our article-to-video implementation replaces rigid template filling with compositions authored for each article. The narration timing postmortem traces clipped speech to a mismatch between requested duration and generated audio. Hyperframes explores how encoded production structure supports agent-driven rendering.

The MiniMax H3 study examines reference-controlled scenes and continuity limits. Engineering Determinism for Image Generation investigates checks around generated visual outputs.

We evaluate prompt adherence, readable text, scene coherence, audio alignment, render failures, and the cost of a usable result. Model specifications help select candidates; produced assets and repeatable checks establish whether a workflow meets its requirements.

Related Publications

  • MiniMax H3 Brings Storytelling Control to AI Video
  • Reve 2.0's Innovation in Image Generation
  • The Bug That Kept Cutting Our AI Videos Off Mid-Sentence
  • First Contact With Hyperframes
  • We Turn an Article Into a Narrated Video in the Time It Takes to Render (Part 1)
  • How the Machines Finally Learned to Draw

View all related publications

Realtime multimodal interaction combining audio and visual context

Multimodal Understanding & Interaction

Multimodal Model Capabilities

Investigate visual reasoning, multimodal retrieval, long-context models, and voice interaction, including how live systems select and use relevant context.

Key Findings:

  • Late-interaction retrieval preserves finer-grained matching than a single-vector representation.
  • Small open multimodal models bring visual reasoning and long context into deployment decisions.
  • Voice avatars combine retrieval, conversation, and presentation, with separate demands on latency and answer quality.
Status: Ongoing View related publications →

Multimodal Understanding & Interaction

Research Summary

This initiative studies how models interpret and retrieve information across text, images, and audio, and how those capabilities support interactive systems. Realtime voice and video remain one strand alongside visual reasoning, multimodal search, and long-context processing.

Late Interaction: ColBERT to Wholembed v3 examines retrieval representations and fine-grained matching. The Qwen 3.5 deep dive explores native multimodality in smaller open models. Our voice-avatar work connects a chatbot’s knowledge to a visual, voice-enabled interface.

Research questions include whether visual or audio context improves answers on a defined task, how retrieval changes relevance, and how latency, context size, and device constraints affect interaction. Live and ambient systems also need explicit decisions about what context to capture, retain, and expose to tools. Image, video, and music production are covered by AI Media Production Workflows.

Related Publications

  • Late Interaction: ColBERT to Wholembed v3
  • [Deep Dive] Qwen 3.5 Brings Native Multimodality and Long Context to Small Open Models
  • Any Chatbot Can Become a Living Expert

View all related publications

Examples of AI-assisted educational diagrams and visual learning material

Generating Engaging Visuals for Education

Educational Visual Generation

A completed study of generated illustrations and code-driven diagrams, animations, and simulations for educational material.

Key Findings:

  • Code-driven tools such as TikZ, Manim, and p5.js provide explicit control over geometry, labels, and animation.
  • Image generation supplies illustrations and assets that can be combined with precise diagrams.
  • Visual accuracy and instructional usefulness require review against the concept being taught.
Status: Completed View related publications →

Generating Engaging Visuals for Education

Research Summary

This completed study compares two ways to produce educational visuals: generating code for diagrams, animations, and simulations, and generating bitmap illustrations and assets. The published guide describes tools and production approaches.

Code-driven tools are useful when positions, labels, equations, or timing need explicit control. Generated illustrations can supply subjects, textures, and other assets around that structure. The choice depends on the concept and the precision it requires.

Review covers factual correctness, label readability, consistency, and the relationship between a visual and its learning objective. The study documents production methods; a claim about improved retention would require a separate learner evaluation. Broader media tooling is covered by AI Media Production Workflows.

Related Publications

  • Generating Engaging Visuals for Education

View all related publications

AI tutoring illustration for personalized learning and feedback

Empowering Learners with AI Tutors

AI Tutoring

Develop cost-aware tutors, generated assessments, and curated learning paths, evaluating feedback accuracy and learner progress alongside inference cost.

Key Findings:

  • A published tutoring case study reduces inference cost through a minimal, format-constrained workflow.
  • DSPy-based education work investigates iterative improvement of generated questions and validation.
  • Curated learning paths and video research tools address how learners find and sequence useful material.
Status: Ongoing View related publications →

Empowering Learners with AI Tutors

Research Summary

This initiative investigates personalized feedback, assessment generation, and learning paths. The AI tutor overview establishes the pedagogical framing; implementation articles examine cost and validation.

The cost-aware tutor case study studies a constrained response format and a simpler workflow. DSPy Unleashed explores a system that generates and improves educational questions. LearnLens addresses discovery and analysis of video learning material.

We investigate whether feedback is accurate, whether generated assessments match the intended skill, and whether a learning path helps a learner make progress. Measurements of answer quality and inference cost inform engineering decisions. Claims about learning gains require learner studies with appropriate comparison groups and retention measures.

Related Publications

  • [How-To] Breaking the Speed Limit with Bedrock & Learners Lens
  • Ready User One: LearnLens
  • DSPy Unleashed: We Built a Self-Improving System That Teaches Anything to Anyone
  • Scientific Discourse for Builders
  • The One Rule That Made My AI Tutor 3× Cheaper (Without Losing Accuracy)
  • Beyond Adoption: Defining Real AI Impact at Trilogy

View all related publications

AI Center of Excellence on X

© 2025 Trilogy AI Center of Excellence. All Rights Reserved. © Trilogy

Practical AI signal in your inbox:

Subscribe on Substack