Ryoi
Founder, product owner and creative director. Sets the vision, taste and priorities; makes material product decisions; reviews gates; grants production authority; gives final acceptance.
Human direction
02.01 / Live / evolving
RYOI.ai
Built by AI. Directed by Ryoi.
RYOI.ai is Ryoi’s public home and a working experiment in directing a persistent AI product team.
- Build method
- Built by AI
- Human direction
- Directed by Ryoi
- AI team
- web PdM + web Dev
- Principal model
- GPT-5.6 Sol
- First public version
- 9h 56m work time
- Token spend
- 316.1M processed
Built by AI.
Directed by Ryoi.
Directed by Ryoi.
A public home /
a working experiment
The website is both a place for Ryoi’s products and one visible result of learning how a human product owner can direct persistent AI roles.
RYOI.ai began before the portfolio was mature. It needed to feel credible without inventing products, clients or outcomes—and it needed a way to keep context, direction and accountability intact across many rounds of AI-assisted work.
AI produced the design, writing, code and delivery artifacts. Ryoi supplied the vision, taste, material corrections, approvals and final acceptance. The authorship is collaborative, but the authority is deliberately asymmetric.
Vibe coding evolved into a persistent AI product team.
The experiment moved from isolated conversations toward named roles, durable product context, one development lane, explicit gates and production evidence.
One direction /
persistent roles
Each role owns a distinct part of the work. AI makes the artifacts; Ryoi owns the vision, material decisions, approval and acceptance.
web PdM
Maintains Web context, turns discussion into product scope and content architecture, prepares GitHub contracts, coordinates the approved route and surfaces decisions.
AI product managerweb Dev
Creates journey proofs, implements approved work, reviews affected behavior, records evidence, prepares releases after approval and verifies production.
AI developerOpenAI Codex
The AI environment through which the persistent product and development roles plan, design, write, code and operate.
Working environmentHow the work /
moves
One visible development lane turns direction into an exact reviewable artifact, then carries the approved result through release and production verification.
Ryoi direction
Vision, taste, priorities and material decisions.
AI PdM scope
Context becomes a bounded product contract.
Journey proof
A working experience makes composition concrete.
Ryoi approval
The material direction is selected before build.
AI Dev build / review / test
The approved source is inherited, implemented and checked.
Exact preview / Ryoi approval
Reachable URLs and proportionate evidence support the final pre-release decision.
Release / production verification
The approved candidate is released and verified at the public URL.
The failures /
shaped the system
The operating model grew from observed delivery friction. Each reset removed ambiguity or made the next decision easier to judge.
Specification before experience
Early moodboards and adjective-heavy requirements repeatedly pushed the design away from Ryoi’s intent. The reset was to work through complete, reference-faithful journeys before extracting a system.
Reset / prototype firstImagery without a role
Generated imagery added polish without strengthening the product story. Typography, hierarchy, space and neutral authored fields became the visual lead instead.
Decision / content firstOne ticket carrying too much
An overloaded brief constrained exploration and made approval boundaries harder to read. Scope, journey and implementation became distinct phases with one exact artifact at each gate.
Reset / explicit phasesEvidence becoming ceremony
Excess testing, missing direct URLs and unnecessary monitoring spent attention without improving the decision. Review moved to URL-first gates and evidence proportional to actual risk.
Decision / proportionate proofMotion moving the layout
Page-entry and title effects exposed geometry drift in live review. Motion was contained inside reserved layers so the interface can resolve without moving the page.
Correction / fixed geometryHierarchy by normalization
A uniform title system weakened the editorial character. The accepted direction restored varied magazine-like scales and corrected only the Contact close that needed restraint.
Decision / preserve variationThe visual system /
supports the story
Full-screen, content-first compositions put typography before imagery and use one restrained interaction grammar across Dark and Light.
RYOI
Dark leads / Light equalFull wordmark / every scale
Typography before imagery
The complete RYOI wordmark uses the same Space Grotesk display construction as this proof’s header. Large editorial statements, monospaced supporting copy, layered neutral fields and sparse rules carry the experience without a decorative brand device.
- Canvas
- Full browser
- Theme
- Dark / Light parity
- Motion
- Fixed geometry
- Status
- Always explicit
- Media
- Authored / optional
Full-screen composition
The browser is the website. There is no inner shell, simulated window or decorative dashboard.
Spatial principleOne interaction grammar
Menus, themes, titles, reveals and actions share the same timing, focus and state language.
Behavior principleHonest product frames
Projects and Journal entries state what is live, evolving, unpublished or not yet known without filling gaps with claims.
Content principleThe operational /
product
The outcome is not only a website. It is a repeatable human/AI collaboration model with durable context, explicit authority and verified release.
Persistent roles let product context outlive one conversation. GitHub keeps scope, exact candidates and delivery evidence retrievable. Approval gates reserve the decisions that require Ryoi’s judgment while leaving the AI team room to execute bounded work.
Consent-first analytics, accessible interaction patterns, exact previews and production verification make operational quality part of the product rather than a separate afterthought.
9h 56m work time / 316.1M processed
The first public release took 9h 56m of recorded AI-team work across web PdM and web Dev. Idle time is excluded; overlapping work is counted as team-hours. The build processed 316.1M tokens, mostly cached context.
Method / bounded ledgerSpeed needs memory
AI can create quickly, but speed without persistent context and decision boundaries produces drift.
LearningWorking beats descriptive
A functioning prototype exposes proportion, hierarchy and behavior more clearly than adjective-heavy specifications.
LearningTaste remains decisive
AI can generate and refine many artifacts; human judgment determines which direction deserves to continue.
LearningApproved means inherited
Content-addressed evidence prevents later work from quietly reconstructing or drifting from an accepted state.
LearningLive now /
still evolving
RYOI.ai is live as a durable home for Ryoi’s products. The next chapters remain intentionally open and require their own direction.
Authored media
Purpose-built interface fragments, process diagrams or video can deepen the story when they add meaning.
RoadmapReal Journal entries
Published field notes can explore role design, context preservation, approval gates and observed delivery lessons.
RoadmapExpanded product stories
Each public product can receive a fuller story when its facts, media and release context are ready.
RoadmapObserved refinement
The AI product team will keep evolving from concrete delivery friction rather than speculative process.
RoadmapBuilt by AI /
directed by Ryoi
Design, writing, code and delivery artifacts by the persistent Web AI team in OpenAI Codex. Vision, taste, material product decisions, approval and final acceptance by Ryoi.
View the live websiteLet’s make the idea real
Contact
Have a product idea, an opportunity to collaborate, or something worth bringing back to life?