OYU Office AI

Stage: concept. OYU Office AI explores a visual alternative to a list of chatbot conversations. The office metaphor is intended to make roles and task state easier to understand.

A user would assign a bounded task to a role such as researcher, writer, designer, marketer, or assistant, then follow its progress and take over when review is required.

Independent workers can lose track of parallel AI conversations, source material, and unfinished outputs. A shared visual state could make the queue, owner, and next action clearer.

The concept aims to make task assignment, progress, review, and output history legible to non-technical users. It has not demonstrated productivity or adoption outcomes.

The proposed audience is freelancers, creators, consultants, and small teams that manage several kinds of knowledge work without a large operations system.

The brief includes a 2D workspace, role setup, task assignment, status changes, files, notifications, history, collaboration, and possible payments.

Planned functions include specialized roles, visual task state, queues, handoffs, review requests, reusable workspaces, and simple progress reporting.

The source describes possible web-canvas, language-model, realtime, database, authentication, storage, and payment components. No final implementation stack is verified.

The audience, interface idea, and core workflows are documented. No public product, user count, revenue, or validated productivity result is available in the repository.

The main risks are visual novelty overwhelming the work, too many simultaneous roles, unclear AI state, and incorrect output. The concept needs a small default team, explicit statuses, review gates, and a conventional task view alongside the office.

Individual and team subscriptions are proposed in the source material. Packaging and willingness to pay have not been publicly validated.

The intended outcome is better visibility across parallel assisted tasks. Completion time, abandoned tasks, review load, and repeat use would be the relevant measures.

The proposed distinction is the visual operating metaphor tied to real task state. It remains a design hypothesis rather than a released-product advantage.