:: Welcome to Venn Agency ::

This page has all the info you’ll need to begin confidently navigating Venn’s projects and processes so you can dive right into working with the team. 


To start, you’ll learn how we use Asana, Telegram, Google Drive & Google Calendar to organize, communicate and get shit done! We’ve also got all current project summaries here for you, with links to their folders, chats and tasks so the things you need to access are easy to find. 


Have questions!?

Vanessa is happy to support you with your onboarding so feel free to hit her up on Telegram (instructions below).


Move Slow and Fix Things


Venn is a digital development lab driving human-centric innovation in technology. We approach today’s big problems with the thoughtfulness and care they deserve. 


Venn is the parent company of Loci. 

Know Your Way


Loci’s mission is to make people smarter and safer wherever they go. We’re building a new generation of web tools designed to connect people to the places they’re in, bringing meaning, intelligence and awareness back into our lives. Our technology works in harmony with the human brain, empowering people to know what to do and where to go when it counts. 


Loci’s first in-market products, Safety Check and Safety CAPTCHA,  are focused on safety and emergency response. 


Safety Check

Smarter People. Safer Places.


No one knows how to read a map anymore, and no amount of signage is going to save you in a life-or-death situation. Safety Check uses groundbreaking neuroscience and an experiential learning interface to turn safety instructions into instinct.



Smarter People. Safer Places.


You’ve never been here before. Do you know how to escape in an emergency? Safety CAPTCHA teaches life-saving evacuation information to people at one-time gatherings like concerts, sporting events, and festivals. 

Loci Admin Portal

Loci’s Admin Portal gives safety officers and executives the ability to manage and audit safety training in their organization. Admins can easily create and customize safety training courses, distribute training assignments and report on training progress.


*Tap phone to preview*

Safety Check
Safety Captcha
Admin Portal

*Last updated Oct 31st 2019

Working Doc: Venn LOCI Glossary

Credential Terminology

Verifiable Credential

A digital object that lives on a ledger that points to a source of truth in a provable, auditable way and provides queries with information about the current state of the organization and current certificates


COR - Certificate of Recognition, a program sponsored by WorkSafe BC that encourages employers to create an occupational health and safety management system that goes beyond the current legal requirements


Top-level container holding all information about the org, especially list of users and locations



Object containing information about a physical location, holds information about safety zones and fixtures inside the location



A localized area in a location containing fixtures - a location may have multiple zones (note: zones are also fixtures, where placards are present)



A physical object in a zone, i.e. fire pull, fire extinguisher, first aid kit, etc

NOTE: All fixtures have a unique ID, tied to their marker


Incident (subtype of Fixture)

A story in the SafetyCheck app that requires an occupant to move to an appropriate fixture NOTE: For data purposes, incidents have a fixture type and are in the fixture table


Fixture Type

  1. ZonePlacard (sign)

  2. MusterStation (gathering location)

  3. FirstAidKit

  4. FireExtinguisher

  5. PrimaryExit

  6. SecondaryExit

  7. Phone



(Stored in the same table as Fixtures?)

  1. Incident_FirstAidKit (green, minor injury)

  2. Incident_FireExtinguisher(orange, minor fire)

  3. Incident_PrimaryExit(red, major fire)

  4. Incident_SecondaryExit(pink, major fire with primary exit blocked)

  5. Incident_Phone(yellow. Serious injury)



(SafetyCheck and physical location front-end apps only)

A physical sticker on the location that indicates incidents and fixtures. Has an Aruco marker generated from the fixture ID.

  1. Incident Markers

    1. Pin drop shaped colour stickers (green, orange, red, pink and yellow) that represent the different types of Incidents found on a Loci training course.

  2. Resolution Markers 

    1. Square shaped black and white stickers that represent the solution to an Incident. Most often these are fixtures, but also include “soft fixtures” like calling for help (eg, Incident_Phone (yellow. Serious injury)).


Loci Safety Check & CAPTCHA Terminology


Database management and Rest API


Admin Portal

Front-end desktop application for organization stakeholders to manage org, users, courses and occupants


Safety Check Mobile application

Front-end application, receives location data from the back-end API and constructs a course for occupants on-site. (Used to be called the game/safety game)



"Completely Automated Public Turing test to tell Computers and Humans Apart" 

Front-end application aimed at ticket sales, receives data from the API to construct a short memory game for users. (Not built by the LOCI core team)


Occupants are ticket holders, event goers or employees receiving training

Occupants are assigned a list of zones, and save event data from front-end application


Occupant Type 

Enumeration of types of occupants, e.g. “Accounting” vs “IT”. Single-valued. Sam will provide values?


Occupant Template

Derived from Occupant Type. Time-saving mechanism to avoid repetitive entry based on Occupant Types.


Occupant Actions

ActivityStarted -- timestamp, ID (hash or unique increment)

FixtureLocated -- timestamp, fixtureId

TrainingModuleStarted -- timestamp, moduleType (enum)

TrainingModuleCompleted -- timestamp, moduleType (enum)

ActivityEnded -- timestamp, ID (same ID as start)


User Role Templates

Users are given individual permissions that can be edited, but these can be added from predefined role templates

Users fall into several general role categories, although new roles can be created with custom permissions for specific needs at any time


 • AdminExternal - Can create new organizations (eg Venn or a service partner)

 • AdminInternal - On-site admin, can create new admins (eg high level safety coordinator)

 • UserInternal - Everyday user, responsible for occupants and managing course (eg safety manager)

 • UserExternal - Outside users who want to access anonymized data (eg fire dept)

 • Occupants - Non-account holders who use the front-end and send data back to database. Occupants do not hold accounts, they recieve link or do the test on page

User Permissions

Users are assigned individual permissions based on their role template at time of creation, but this can be updated by an admin


View list - AdminExternal

Create - AdminExternal

Read - AdminExternal, AdminInternal

Update - AdminExternal, AdminInternal

Delete - AdminExternal


View list - AdminExternal, AdminInternal

Create - AdminExternal, AdminInternal

Read - AdminExternal, AdminInternal, UserInternal (self), UserExternal (self)

Update - AdminExternal, AdminInternal, UserInternal (self), UserExternal (self)

Delete - AdminExternal, AdminInternal, UserInternal (self), UserExternal (self)


View list -  AdminExternal, AdminInternal, UserInternal, UserExternal, Occupant

Create - AdminExternal, AdminInternal, UserInternal?

Read - AdminExternal, AdminInternal, UserInternal, UserExternal, Occupant

Update - AdminExternal, AdminInternal, UserInternal?

Delete - AdminExternal, AdminInternal, UserInternal?


View list - AdminExternal, AdminInternal, UserInternal, UserExternal, Occupant

Create - AdminExternal, AdminInternal, UserInternal

Read - AdminExternal, AdminInternal, UserInternal, UserExternal, Occupant

Update - AdminExternal, AdminInternal, UserInternal

Delete - AdminExternal, AdminInternal, UserInternal


View list - AdminExternal, AdminInternal, UserInternal

View list anonymously - UserExternal

Create - AdminExternal, AdminInternal, UserInternal

Read - AdminExternal, AdminInternal, UserInternla

Read list anonymously - UserExternal

Update - AdminExternal, AdminInternal, UserInternal

Delete - AdminExternal, AdminInternal, UserInternal


View list - AdminExternal, AdminInternal, UserInternal, UserExternal

Create - AdminExternal, AdminInternal, UserInternal

Read - AdminExternal, AdminInternal, UserInternal, UserExternal

Update - AdminExternal, AdminInternal, UserInternal

Delete - AdminExternal, AdminInternal, UserInternal


An assignment for occupants. Filters information needed for each front-end app and provides a permission template when adding new occupants

An object that filters location data down to what is necessary for the occupant. The assignment object can be used to create groups for different front-end applications, (i.e. there could be a “Fire Safety Captcha” assignment) as well as for different needs in a location (i.e. there could be a “Welder Safety QR” and “Office Worker QR”

Assignments filter based on FixtureType, as well as a template for occupant

How We Work

Venn's Principles At Work

  • We iterate and show our work’s progress along the way

  • We are proactive

  • We are accountable

  • We prioritize communication

  • We strive for clarity

  • We set realistic timelines


You’re the expert in your domain. Your perspective is unique. This is why you’re on the team. We value your knowledge and experience, and trust you to think critically about your work from a place of integrity—if you’re asked to do something that doesn’t makes sense to you, get curious, ask questions, offer alternatives and speak up! 


Venn is working on creating new and necessary things from a new perspective. In order to succeed we need to trust each other and be accountable to one another. The internet is our virtual workplace, and we strive to make it feel like a shared space as much as possible. We want all of the great things about being a team (the collaboration, the camaraderie, the creative problem solving, the support, the memes!) without the restrictive 9-5 lifestyle. This means that we all put effort into communicating on group chats and being clear with our teammates about when we’re available and working.

Formal conversations

In group and on-on-one discussion we use “we” statements to express certainties and directives. “We” statements communicate cohesion of thought, and that an agreement

has been established amongst the team.

  • “We’re ready to move this into design phase.”

  • Direction is given from this more formal place.

Informal conversations

In group and on-on-one discussion we use “I” statements to express thoughts, ideas and possible actions. “I” statements communicate emergent ideas and give us room to brainstorm and explore ideas without being taken as a firm directive.

  • “I think we should try calculating risk using data from this study.”

  • Informal “I” statements are not necessarily concrete directions for how work is to be done.

Where We Work

When you are making something to share (internally or externally), ensure you select the appropriate app or platform.

→ Is it highly visual? Lots of digital media? Use Wix

→ Is it a plan with lots of to-do’s? Use Asana

→ Is it mostly written content? Use Google Docs

Asana - Our project management hub. All your project-related assignments will be managed through Asana, and you can maintain your own To-Do lists in the My Tasks tab as well. For the sake of transparency, we encourage contractors to track all work-related tasks on Asana to help you with timesheets and invoicing.

Telegram - This is our main communication channel. PLEASE DO NOT SEND ANYTHING BY EMAIL THAT YOU CAN SHARE IN A CHAT. This includes documents, images, questions, links, and any work-related updates. There is almost no reason to use email internally. Eff emails.


Google Drive - All company documents are kept and shared in Google Drive (at least for now, until we get our own Nextcloud server and can work unseen by the Eye of Sauron).



  • Docs - Collaborative word docs for papers, outlines, research, letters, proposals, glossaries, etc.

  • Sheets - Budgets, forecasts, contacts & CRM-related stuff, numbers.

  • Slides - Draft versions of presentations before they go to design.

  • Forms - Used by the research team to create surveys for data collection.

Zoom - All our meetings take place in Zoom so we can see each others’ smiling faces :) 

Github - Our developer portal. Commit ur code or else.

Canva - Do-it-yourself design platform for quick and dirty mock-ups.


Keynote - Superior presentation app to Slides, we use the iPad version quite a bit. 

Emails - Really, avoid emails as much as possible, except when communicating with outside organizations and individuals.

Evernote - Our research repository. The Evernote web clipper is an internet researcher’s best friend.

Wix - Our website is built on Wix. We also often use Wix instead of Slides to create presentation pages so that our content can be easily kept up-to-date.

Google Calendar - Rounding out the G-Suite, we use google calendar for meeting invites and general scheduling on the Venn team.

Matterport - We use Matterport to make 3D scans of buildings and spaces, and from there we can create fly-throughs and all kinds of cool stuff.


Current Projects


What - Ongoing tasks related to finding the important information we need to build our company and our products.
Why - We often know what we don’t know and put a lot of effort into filling knowledge gaps and finding supporting information that helps us think and perform at our best.

Design SCRUM

What - Design team task management project.
Why - So we’re all on the same page about priorities and deadlines



What - Ongoing tasks related to how our companies look and feel visually. 
Why - Good design makes a world of difference and we are working on creating a holistic and effective design process that yields beautiful, effective work.

UI/IX Safety Check

What - Managing the design and build of Safety Check’s visual and experiential interface.
Why - This is a critical component of the product with many moving pieces that we need to stay aligned on and move forward in parallel with development.


What - Managing the creation of all assets and documentation needed to fundraise for Loci. 

Why - To get a trillion dollars.


What - Master project for building and shipping Loci’s products.

Why - Keeping the big picture clear and accessible to everyone on the team.

Verifiable Credentials

What - Where we manage tasks related to building the architecture of Loci’s VC back end.

Why -  VCs are a key component of the data management strategy at the foundation of Loci’s system.


What - Dev team task management project.
Why - So we’re all on the same page about priorities and deadlines

Policies and Best Practices

What - Dev team project managing how we write and document code, setting development standards and setting our technical path (licenses, terms & agreements, policies).

Why - It’s vital that we build a clean and functional product from the very beginning to support future growth and product development.

Safety Check

What - Master project for building and shipping Safety Check.
Why - Keeping the big picture clear and accessible to everyone on the team.


What - Building the Safety CAPTCHA product with outside contractors at Mind & Mill.
Why - Keeping the internal team and external contractors on track and aware of the projects progress so we can ship the best version of this product possible.

Loci Admin Portal

What - Managing the design and build of the administrator’s dashboard that runs Safety Check and Safety CAPTCHA

Why - The Loci platform is self-managed, allowing admins to build and distribute their own safety training programs.

System Architecture

What - Upkeep on the System Architecture document.

Why - To create clarity and transparency around managing our IP.


What - Steps to develop the process from start to launch when installing Safety Check.

Why - Creating the efficient methods for setting up and running Safety Check in different environments.


All team communications are funneled through the relevant chat streams on Telegram.


  • Anything project-related should be shared in the correct group chat (eg, Design, Dev, Sales & Marketing) even if the message is to one person on the project. 

  • This keeps everyone aware of project progress & supports transparency and accountability in our work.

  • Administrative questions & shares can be sent directly to Vanessa or Sam as needed. 

  • Telegram messages are prioritized around & during work hours (~7am-7pm).

  • Sharing on Telegram can happen any time. Be sure to manage your alerts settings so that this doesn't feel disruptive to your workflow or downtime.

  • For urgent communications outside of work hours use Telegram, if you don’t get an answer call the person you are trying to reach directly.

  • Messages marked as read (√√) are no guarantee that someone has fully read and digested your message. If a timely reply doesn’t come don't be shy, follow up to ensure you get a response, especially if it’s time sensitive.

  • If you’re working late/outside of regular work hours, make sure that the team members you’re interdependent with are aware of your schedule and prepared to coordinate with you during off times if necessary.

  • There’s no expectation that you respond to Telegram after you’ve signed off for the day. Simply send a sign off message saying goodbye to your team chat and everyone will know you'll respond when you sign back on.

Telegram Admin

Vanessa (Lead) → Makes sure everyone gets responded to + reminds team to use it!

Sam → Shares team accomplishments, business priorities and feedback

Joni → Pulls highlights from telegram chat for communications & research

Download Telegram

Download Telegram to your phone, computer and tablets!

Apple - https://itunes.apple.com/us/app/telegram-messenger/id686449807

MAC - https://macos.telegram.org

Android - https://play.google.com/store/apps/details?id=org.telegram.messenger&hl=en_US

PC - https://desktop.telegram.org (in more options)

Getting in the chats

  • Click the name of the chat below to join.

  • Each chat has a description of what its for you can see if you click the title 

  • Trouble joining? Ping Vanessa with your phone number.

  • Note: Quad and Ops are closed - no link and Estate/Retail + Blondtron are currently shelved projects

Project Chats


Venn Agency


Please join our full team Venn Agency chat on telegram!

Everyone is encouraged to share major highlights and milestones.

For example:​

  1. Public facing & internal accomplishments.

  2. Highlights in adjacent industries / our industry, about partners and prospective partners.

  3. Developments, announcements and highlights about relevant tech.

  4. “I ran into X person, sparked convo on X, meeting next week!”

  5. If you don’t know who to ask, you can ask questions here (If there is no related project chat or Asana task).


How to Search Media Shared on Telegram

Google Documents

Shared Docs Best Practices

Never presume anything about what a person knows or will do with what you create (this goes for all things). When documenting or writing anything in a shared doc, we like to create a quick reference summary at the top which includes the following:

  • The goals or purpose of the document (what is it for, why does it exist, who is it for)

  • How to use the document (is this FYI only or do you want feedback? How can ppl share their feedback with you?)

  • Quick links in the header (collect all links from the body of the document and add them to the header for easy access)

  • Separate this section from the body of the document by inserting a horizontal line (> Insert > — Horizontal line)

    • Like this:



Video & audio is automatically recorded and stored on Zoom.com. Some past meetings are stored in the Video Recordings folder on our Team Drive. https://drive.google.com/drive/u/0/folders/1l6drdPHF5awD2IB4FT3enQGNziN8thqj



If you booked the meeting, ensure the responsibility for taking meeting notes is delegated before the meeting starts if you're not doing so yourself. It’s hard to run a meeting and take notes at the same time, so someone from the team can help!

All notes are taken in the appropriate ongoing meetings doc, as detailed below.



When you make a google calendar meeting invite be sure to:

  1. Add the correct Zoom room link (can be copied to the location field in the invite)

  2. Link to relevant docs in the meeting details field.

  3. If you not in the meeting, make it in info@venn.agency calendar so anyone can update the event. 



Anyone meeting with Venn Agency



Meetings External internal 




Team meetings 



MEETINGS Agenda internal 




All references and articles used during a project are saved to the Venn Content folder in Evernote.

  • Install the Evernote Web Clipper browser extension for easy archiving (works with most browsers, including Brave, even though it’s not listed ;) [https://evernote.com/features/webclipper]

  • Venn Content folder will be shared with you by the admin once you have an Evernote account set up.


Venn Content: All articles, papers and websites we collect during our research. The point is to create a robust library of searchable references so we can minimize the amount of time we spend looking for “that article that had that stat about…” etc.

Project VRM: Repository for relevant threads from the Project VRM [https://cyber.harvard.edu/projectvrm/Main_Page] (Vendor Relationship Management) listserve that some of us follow. Sign up to the list yourself, or browse this folder for interesting conversations, updates and debates about personal data, privacy, SSI and more.


Use all relevant tags—more is better! Add any terms you think will be useful/likely to be used by someone querying the list.

Browse existing tags to see what’s currently in use.

Dev Team Tags in Evernote:

GPS, Gamified learning, machine learning, learning, mixed reality, maps, mapping, node, open source, persistence, personal data, piracy, regulation, researcher, safety, search engine, sleep, social media, spatial learning, SSI, stats, surveillance, capitalism, trust, VR, wallets, wayfinding, webVR, webXR, working group


Sales Team Tags in Evernote: - COMING SOON -


Your First Research Assignment:

Familiarize yourself with some of our past work, as well as the science, philosophy and research that are the foundation of what we do and how we do it.


Wix makes it very easy to create visual presentations. Use this platform for decks, overviews, briefs, product demos and anything else with mixed digital media.

Please note that only one user can be editing in Wix at a time. Check in with the team before going in to editing mode to ensure your changes aren't lost.

Quick Video Tutorial 

Assets & Imagery in Wix

Visual Wix Page Creation Tutorial


Our design process is still evolving and we want to work with our designer(s) to establish a system for briefing and developing design that feels good for everyone involved and yields the best results.

What our current process looks like:

  1. Project kick-off conversation to discuss what the design requests will be and what it will take to get there.

  2. Project Manager (PM) creates Asana project and fills in tasks, priorities and references.

  3. If needed, a comprehensive design brief is created in Wix.

  4. Designer and project leads sign off on brief and agree on desired outcomes.

  5. During design development, designer reviews early options with project lead/PM to get clarity on direction.

  6. Rounds of feedback are communicated through a design project journal (in Slides - this is an easy way for us to comment and compile feedback visually).

  7. Feedback process is repeated until everyone feels we’ve achieved desired outcomes determined at the outset of the project.

  8. Initial sign off on iterations given by Vanessa.

  9. Final sign off is given by Sam.

As the designer you will:

  • Help us set realistic timelines for how long work will take.

  • Be the leader and owner of your process. Please share with us and show us how your work is coming along.

  • Show options/versions for feedback as part of an iterative design process.

  • Break bigger design requests down into the steps it takes to get there and get buy-in/approval for the steps along the way. 

Presentation Deck Design Process

  • Basic deck outlines are created in slides (no design, just content).

  • Kick-off meeting is a review of the outline and discussion of design direction to be taken.

  • Process is then the same as steps 4-9 above.

  • Decks can be designed in Illustrator but final delivery in Keynote is preferred, especially for slides that we will be using elsewhere or in other presentations. 

  • Final version of presentation should also go on Wix for easy sharing via URL. 

Decks working docs, old deck and inspiration decks are in Venn Share --> Presentation [DECKS] https://drive.google.com/drive/u/1/folders/1IG9bO5sqdPYEHwXLj-Wx-cjuAkslbCAD

Visual Brand Identity

Venn.Agency and Loci are separate entities with different visual identities. There are small instances of crossover, where colour or design from Venn may influence choices made for components in Loci––we think of these like samples or an homage. 


Loci’s visual brand is in its early stages and defining it is one of our first design priorities. Which is where you come in!

Development Process

Last updated Nov 4th

Working doc: Dev process




  • feature branches (branch off of staging)

  • staging (merge from feature branches)

  • master (merge from staging only)


Committing Code

Check in your code regularly, at least once a day to repos you’ve changed. This helps avoid lost changes and it permits your peers to review your upcoming changes. 


Because the master and staging branches are automatically deployed during Ci/CD, you can push any changes that aren’t yet ready to a branch off of staging (you can think of this as a feature branch, personal branch, etc. 


Document your code

As we’re getting started, do not worry about having this perfect. We want to improve this over time


Use the repo’s README.md as a running, up-to-date, document of the repo’s design and functionality. Keep it up to date as you add new features. Include e.g. API docs


We have a template you can use as a starting point.


If any of your changes are architecturally significant (change to security model, new component, etc -- ask if you ‘re in doubt), update the Architecture Doc.


Add unit tests

Similarly, we have no strict coverage requirements, but we want to improve this over time.


Add unit tests as you go to reduce manual testing burden. This also helps ensure you’re writing testable code. 


Ensure unit tests are run on checkin via circleci config.




  • Version control: We use github (Venn Agency organization) for version control.

  • Checking in: Check in code to a branch off of staging at least once a day

  • Document your code: Ensure your repo’s README.md is up-to-date and includes (or links to) a high level description of key design concerns

  • Write testable code and unit tests: Add unit tests as you go to reduce the E2E testing burden

  • Promoting to staging: When you’re ready to promote to the staging environment, merge your pending branch(es) into the staging branch

Promoting to production: When you’re ready to promote to the production environment, and any relevant quality bars have been met, merge the staging branch to the master branch



Our CI/CI process is configured as follows:

  • Pushes to any branch automatically run unit tests.

  • Pushes to the staging github branch are automatically deployed to the staging environment

  • Pushes to the master github branch are automatically deployed to the production environment


Quality Bars

Promoting to staging

You may promote your work to staging after you’ve ensured unit test pass, and finished any local testing.


Test your changes in the staging environment

Promoting to production


Before deploying to production (which happens by merging staging to master), the following quality bars apply:

  1. E2E tests

  2. Ensure you’ve updated documentation

    1. Update repo documentation

    2. Update Architecture Doc, if any changes are architecturally significant

  3. Create a PR (a PR is required, long term)

    1. create a PR from staging to master 

    2. include a brief description of your changes

    3. link to relevant documentation (e.g. relevant section in the README.md or other docs). 

    4. Do not merge yet, and ping the dev channel for review

  4. Design review

    1. for anything other than trivial changes, we’ll have design reviews. Your peers are notified by step 3e.

    2. We’ll generally have these meetings after 11am tap ins

    3. Ensure you’ve prepared any relevant design documentation (preferably in the repo’s readme)

    4. You’ll present the changes and we’ll discuss 

  5. Code review: your peers will complete code review

  6. Coordinate on deployment timing (to avoid downtime if any critical demos are underway)


~*~ Welcome to the Venn.Agency Library ~*~

We’re inspired by so many intelligent people doing incredible, groundbreaking work in a vast array of fields. Our library of readings, videos and audio recordings will be updated on an ongoing basis, highlighting the ideas that have been foundational to Venn’s purpose and evolution.

Check out the Complete Read/Watch/Listen list to understand what we value, where we’ve been, where we’re going and how we’ll get there.


*Last updated: Oct 31st - Read/Watch/Listen



Get to Know Us

(Stuff Venn’s made over the years)


Hacker’s Guide to the Metaverse Teaser Video

Metaverse Lab (2015-2018)

Persistence Art Show

Digital Identity, Privacy & VR (Presented at Stanford, October 2018)

Loci Deck (Ongoing)


The Foundations of Our Work

(Stuff that informs what we do and how we do it)


The Immersive Internet—Dr. Karan Singh, Janus VR

Verifiable Credentials Data Model (Plz read from abstract through section 1.2)

Project AVALON

Lifescope Manifesto

Systems Thinking—Scott Spann

Indie Computing—Johannes Ernst

The GPS of the Brain—John O’Keefe


:: Go Deeper into Some of Our Fave Topics ::


The Brain

The Complexity of Memory—TED Playlist

Accounts and 


Stop Saying Privacy is Dead 

The Lost Language of Privacy


Self-Sovereign Identity

The Path to Self-Sovereign Identity

The Seven Myths of SSI Part 1 and Part 2



10 Design Principles for Governing the Commons

Open Data Handbook

Tragedy of the Commons 


Read a Book Whydontcha! 





Screen Shot 2019-10-31 at 12.00.23 PM.pn

We keep sensitive passwords on codedpad.com

If necessary, you'll receive the password for codedpad from Vanessa, or you can can request it from her over Telegram. 


Focusing, motivating and inspiring music!

Please feel free to add to it. PLAYLISTS

Org Chart
Contact info



Add your timezone

If you have not signed an NDA yet email Vanessa - ASAP

*Last updated Oct 29th

Working doc: Contacts


Please update your contact info as it changes! Check the working doc for latest updates



Samantha Mathews Chase 

  • Founder / CEO

  • Tech & Project Strategy - Speaking - Technology - Network 

  • 1-323-740-9425

  • Samantha@venn.agency

  • LA + Vancouver 

Kim Hamilton


Armando Ceron


Cristian Gartner 


Shaw Walters


Alex Mckelly


Crissy Chung  



Joni McKervey 

  • Director of Communication, Writing, Research,  

  • Tactical communication, creative content, content strategy specialist

  • 1-778-996-9264

  • joni@venn.agency

  • jmckervey@gmail.com

  • Venn Status: Employee & NDA

  • Vancouver



Vanessa Dayton

  • Venn Status: Contractor & NDA

  • Vancouver 


Myfanwy Williams


Vishana Lodhia

  • Designer, deck and 2D graphic design

  • +1(416)385-2426

  • vishana@venn.agnecy

  • Venn Status:

  • Toronto / Worldwide!

Full team email list! 















Along with your invoice, please provide a timesheet that breaks down your hours and notes which projects those times were dedicated to.

Time sheets template. 


Paid within 15 or 30 days of invoice received (Depends on your contract, we try and pay right away)



If you have not received payment message Benji or Vanessa on Telegram




Venn Agency

344 - 1530 N Poinsettia Ln

Los Angeles, CA 90046

Send to: samantha@venn.agency CCing accounting@venn.agency vanessa@venn.agency

Include: Hours + breakdown of work (or asana done list screenshot)




Circle Work Corp

2944 Shakespeare St.

Victoria, BC V8R 4H4

Send to: samantha@venn.agency CCing accounting@venn.agency & vanessa@venn.agency 

Include: Timesheet + breakdown of work (or asana done list screenshot)



If you haven't signed a NDA yet ping Vanessa - ASAP

We are keeping our technology under wraps while we file for patents. It’s totally cool to talk about what our product does, just not what’s in the tech stack. That’s the secret sauce!



If you don’t have a contract in place yet, please ping Vanessa on Telegram to set a time to finalize a contract. Feel free to add notes on what you understand the scope of your contract to be so far and the team will get it sorted as quickly as possible.