How can vessel interaction, mechanism motion and project content work together while keeping evidence easy to reach?
Current output
Free exploration and a boarding tour exist. Shared project records, twelve chapter texts and direct reading paths are being refined.
My role
Product goals, content mapping and interaction decisions proposed independently; front-end engineering completed with AI assistance.
01
Context and constraints
Some visitors want to explore the vessel; others want one project. Loading, opening shots and long mechanism sequences must not block responsibilities and results.
02
Decisions
Compartments navigate themes; shared project records hold the content. Both modes reference the same cases, with a standalone reading index and static fallback.
03
My contribution
I define the site purpose, map compartments to personal content and decide how motion explains each theme. Implementation, asset processing and automated checks are AI-assisted.
04
AI collaboration: correcting C04 multi-track playback
The task was to integrate the approved C04 loading version. Inspection found that the new asset contained multiple synchronised clips while the old playback code played only the first.
Loading a file and playing the full mechanism became separate acceptance questions. The solution advanced the clips on a shared clock while preserving pause and return state.
I own the goal and presentation judgement; AI assists asset inspection, playback changes and checks. Complete playback requires examining tracks and key phases, not just opening the page.
05
Evidence: checked scope and open questions
The 19 September record reports 26 journey tests, eight server-rendering and permission tests, type checking and a build, plus model decoding, motion samples and resource checks. These are dated integration results, not automatic claims for later changes.
The same record leaves the new browser visual review and inherited geometry issues open. Visual review, interaction and engineering performance need separate evidence.
06
Limits and next steps
Continue checking article return, direct navigation, mobile layout and reading without 3D. Validation of new copy and routes belongs to the current delivery record; earlier test counts must not be reused as new results.
METHOD NOTES
Methods to take away
Give AI a task with observable acceptance
State the goal, current problem, permitted scope and acceptance scenarios. Review the output and separate passes from unchecked areas.
When to use it
Scoped modelling, code fixes and asset integration in an existing project.