Vamos: Audit + Prototype

An outside read of Vamos, the collaborative trip planner, and a working prototype of its core loop. Week one runs the audit and direction; week two builds the desktop / PWA prototype of the drag-to-schedule gesture. Each deliverable resolves at a single review.

Sprint · Two weeks Adjust kickoff to recalculate

Kickoff

Duration2 weeks

Handoff·

FeePer Fictive Kin SOW

01 · Roadmap 2 WEEKS

A · Audit + Direction B · Prototype Milestone

Phase	Window	Duration	Dependency

02 · Calendar DAY-RESOLUTION

Milestones KEY DATES

03 · Phases WORK BY PHASE

A A · Audit + Direction Week 1 · handoff Jun 30

#	Item	Owner	Target
A.1	Fresh-eyes audit: cut / keep / add across every feature	Studio	Jun 30
A.2	Core-loop diagnosis: Ideas as pile, Plan as commitment	Studio	Jun 30
A.3	Strategic outline: top 3 ranked moves, delivered to Cameron	Studio	Jun 30

B B · Prototype Week 2 · handoff Jul 3

#	Item	Owner	Target
B.1	Wireframe: drag-to-schedule, pile to time rail	Studio	Jul 1
B.2	Collapsed item modal + seeded onboarding flow	Studio	Jul 2
B.3	Clickable prototype: core loop end to end (url-fk-vamos)	Studio	Jul 3
B.4	Loom walkthrough + handoff brief	Studio	Jul 3

Insights WHAT WE SEE

Audit before build. B inherits A. The core-loop diagnosis sets the direction the prototype is built against, which is why week one runs first.
The spine was missing, not features. Vamos could not tell a wish from a plan. The fix is one gesture: a maybe becoming a committed, timed block.
Deliverables are format-flexible. Per Cameron: sketches, prototype, or doc, whatever lands the thinking fastest. No code merge this sprint.
Scope is two tracks. The membership app and second orchestra brief are separate engagements, not silent scope creep.

Out of Scope SOURCED SEPARATELY

Production code or merges; this sprint is audit + prototype, not a build into the live app.
The in-destination / day-of mobile view; a separate product surface.
Remixable public trip templates and the social Explore layer; a v2 bet.
The membership app and second orchestra brief; separate Fictive Kin engagements.

Terms BILLING · IP

Engagement. Fee and terms run per the Fictive Kin SOW. This worldsite maps the work, not the contract.
Reviews. Each track resolves at one consolidated sign-off with Cameron; additional rounds scoped separately.
Ownership. Fictive Kin owns the Vamos product and all delivered work. The Vamos identity (Lab Grotesque licensing) sits with Fictive Kin.
Showcase. Client work stays gated: a private case study for pitching, not published.
Entity. Billed through Studio Artifice LLC, fully separate from Artifice NYC.