Terminology in Anytwo
Vault
The highest level where everything begins, it is your account that manages your identity secured by a key held only by you.
- One vault can belong in multiple hubs.
- One vault can belong in multiple spaces.
- The same vault can query and act across multiple spaces at once.
- Activity centre for notifications exists at this level.
- Connectors for integrations exists at this level.
Hub
A container that holds multiple spaces together that can share assets between them. This enables group coordination and management.
- Sharing collections, properties, templates.
- Public spaces, private spaces.
- Member mangement, permissions.
- Shared integrations.
- Version history, backups, restoration.
Space
A container where all of the work happens. It stores everything as an object that is categorised, linked, and manipulated to form useful interfaces to the underlying data.
- Contains objects with collections, properties, and templates.
- Has its own dedicated set of members and permissions.
Mini-apps
Mini-apps help to customise your experience to suit the task at hand. A space for documentation can have a traditional File Explorer Mini-app. A space for handling many people records can have a CRM Mini-app. A space for collaboration between researchers can have a Chat and Library Mini-app.
- Every Mini app is designed for a specific use case.
- Mini apps all operate using the same underlying object database that have collections, properties, templates, and the like.
- All Mini apps can be enabled and disabled per space.
- Mini apps primarily impacts the space sidebar interaction, but also can influence how objects are rendered.
Format
It defines the how the user interacts with an Object, it's structure, and its layout. Key points:
- Every Object may only have one Format.
- All Formats have a unique object layout that defines how it is interacted with.
- Conversion from one Format to another is atypical and seldomly possible.
- Formats should be as agnostic as possible, the fewer the better.
- By default, the names should be expressed in plural as they’re applied in multiples.
Pages: For reading and writing text heavy objects, powered by a block editor experience.
Views: For manipulating many objects at once, powered by a flexible dataview experience.
Chats: For fast communication between people & agents, powered by a messaging experience.
Bookmarks: For managing an archive of external records, powered by a web clipper experience.
Actions: For task management, powered by a to do list and kanban experience.
Whiteboards: For handling objects in visual space, powered by a whiteboard experience.
Profile: For managing people and organisations, powered by a CRM experience.
Mail: For managing emails, powered by an inbox experience.
Meetings: For reviewing and managing outputs from meetings, powered by…
Events: For managing moments in time, powered by a calendar experience.
Objects
The primary unit that contains content.
- Every Object can only be one Format.
- Every Object can belong in multiple Collections.
- Links between objects can exist on multiple levels, primarily context and body.
- An Objects with different Formats may appear very differently.
Object Header: Title, Description, Icon, Cover Image
Object Context: Collections, Properties, Enrichments
Object Body: Content
Object Appendix: Discussions, Comments, Attachments
Collections
The primary way to add context to each object.
- Every Object can belong in multiple Collections.
- Collections can have multiple Properties.
- Collections can contain Objects with multiple different Formats.
- Membership in a Collection can be based on manual or rule-based selection.
- Org-level Collection?
Properties
Give structured data to each object and provide a means to manipulate them together.
- System Property is set for all objects by the application and cannot be modified.
- Collection Property is specific only to Collections and is user-defined.
Links
Links are how objects build relationships across a knowledge graph.
- Links are connections to an Object
- Backlinks are connections from other Objects
- Two-way Links are connections tied together.
Templates
Templates are reusable structures and content that are specific to the Object Format. A Template for a Meeting will not apply to a Chat.
- Templates are specific to Format.
- Templates can be assigned to Collections, however this would only apply to objects matching the same Format.
Connectors
Integrations are ways to connect the application to external sources.
- Integrations should be mapped to the ideal Object Format.
- If there is an existing Template, integrations should follow it.
Agents
Everything related to the harness
- Personality
- Skills
- Connectors
- Credentials
- Schedules
6 Comments
Sign in to comment
·13 days agoMarking this as done for now.
I am starting to get my head around the new terminology. I have a question that seems to be a limitation in comparison to Anytype, will you support what was called "inline collections" in Anytype in Anytwo? I see Views above and Bao tells me they cannot be inline. For example, I have an Author and want a list of all the books the Author has written. Right now, Bao wrote a scheduled task to update the list.
·14 days agoYes, this is something that we will need to implement. What you're asking for is 'inline views' as a block in the editor—correct?. They're not available at the moment but you're welcome to write out a feature request if there's something special that you expect from it.
·18 days agoA high level product architecture document that outlines all the components to Anytwo. We are open to renaming terms if they are unclear. We are particularly open to other options for Mini-apps, Types, and Agents (currently called Bao).
This overview is very helpful, thanks. => Maybe good for any newbies as well, as a quick primer to core features and terminology.
We're in another iteration of the architecture. Once that's released, and if it settles on being the right choices, I'll likely create a getting started video for Anytypers.