guide to agentprivacy
Browse collections
โœจVisualise
Connect with Star
Your VTA, your chosen perspective

The planned connection uses your VTA and the Trust Spanning Protocol to carry a scoped exchange for you or your agent. You choose what is presented; the receiving service checks the request before a view is shared.

This guide has no VTA connection adapter yet. Opening Star does not connect an identity or send a key.

Open Star โ†— ยท Inspect your City Key โ†—
guide / Vision / Max Timeline Feedback

HTML5 mp4 http://david.local/assets/workshop-videos/max-timeline-feedback.mov
Feedback on Max's timeline โ€” two open risks: the Nov 5th DevCon vs Don't Panic Festival collision, and the 2027 IP transfer's effect on tokens and Marvin.

Summary

A short feedback exchange interrogating two open risks in Max's timeline for the Hitchhiker / Game of 42 project. The first concerns a scheduling collision on November 5th between Mumbai DevCon and the Don't Panic (Not Panicking) Festival โ€” whether the team can credibly be on stage at DevCon while simultaneously running a global event across 42 locations, when DevCon is treated as the capital city connected to the other 41. The conversation surfaces a staffing and headspace problem: the team can only be in one place, so whoever runs DevCon must be backed by enough team to manage the connected global event. The second open question is a legal/tokenomics one โ€” if the IP is not transferred into the new company until 2027, what becomes of the tokens, of Marvin, and of any IP-dependent activity attempted before the transfer. Both items are parked onto the timeline as milestones, with the IP question tied explicitly to the November token sale.

Key points

  • DevCon vs Festival collision (Nov 5th): open question whether Mumbai DevCon and the Don't Panic Festival can both run on the 5th of November; flagged as a milestone on that date.
  • Two headspaces risk: being on stage at DevCon and managing a global event at the same time are two very different things; the team can only physically be in one place.
  • Capital-city topology: DevCon framed as the capital city, connected to all 42 locations (DevCon being one of them), requiring enough team to hold the centre and the other 41.
  • IP transfer timing: IP is not slated to move into the new company until 2027, raising questions about what happens to the tokens and to Marvin in the interim.
  • IP-before-transfer activity: uncertainty over what can be done with the IP at all before the 2027 transfer.
  • Token-sale linkage: the IP question is bound to the token sale, dated November; logged as an ad (agenda/milestone) on the timeline.
  • Triage discipline: questions raised early and parked onto the timeline now, to be worked through in detail only if these items become ones the team actually pursues.

Action items

  • Put the DevCon / Don't Panic Festival collision on the timeline as a milestone on November 5th.
  • Work through the DevCon-vs-festival 'what could go wrong' questions in detail if that milestone is selected.
  • Ensure enough team to staff DevCon (capital city) while managing the 42-location global event connectedly.
  • Log the IP-transfer (2027) question as an item tied to the November token sale.
  • Resolve what happens to the tokens, to Marvin, and to pre-2027 IP activity before the token sale closes.

See

Transcript

๐Ÿ“Ž max-timeline-feedback