Vision
Software should start with what you want to accomplish.
From app-first to intent-first
Begin with the desired outcome.
App-first software
Asks people to know which tool to open, where to click, what information to enter, and how to follow up.
Intent-led software
Begins with the desired outcome. It understands the request, identifies available capabilities, shows the relevant choices, and helps complete the task when the required connections exist.
The transition will not happen all at once. Most tasks still depend on external providers, permissions, reliable data, and operating processes. The opportunity is to make those dependencies easier to work with, not pretend they no longer exist.
Three parts of the vision
Get tasks done, work with information, run a business.
DBMansion Labs is developing products around three connected needs.
Everyday action
Get everyday tasks done.
Mansion, the personal assistant, is designed to connect everyday intent to compatible businesses and services, making it easier to compare options and execute tasks with user control.
Knowledge work
Work with information.
Satori is intended to help people conduct research, write, code, analyze information, and continue complex work with context across projects.
Business operations
Run a business.
Dibiflow helps businesses organize core workflows. Reliable business records are useful in their own right and may also become building blocks for authorized digital integrations in the future.
Execution
Why structured systems matter.
A generic AI model may reason about what should happen, but real execution also requires dependable information and capability access. To order a product, a system needs correct product details, price, stock, delivery terms, payment authorization, and confirmation. To book travel, it needs live availability and a valid booking flow.
Direct, structured interfaces can reduce the need to parse inconsistent websites for every action. They do not eliminate all integration work, but they can make supported tasks more reliable and less wasteful.
Principles
Constraints that keep the ambition honest.
- Build what works today
- Product status must be clear.
- Connect only where permitted
- Integrations should be authorized, stable, and respectful of provider terms.
- Make action observable
- Show what the system is about to do and what actually happened.
- Keep people in control
- Permissions and material decisions must be clear.
- Earn trust through accuracy
- A failed task should be reported honestly, not disguised as a success.