> For the complete documentation index, see [llms.txt](https://docs.borderless.company/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.borderless.company/english/borderless/who-we-are.md).
# Who we are
### **Mission**
> **"Bring millions of companies onto the web3 and**
>
> **transform the entire corporate lifecycle onchain!"**
We are challengers, breaking corporations' “common sense” that has remained unchanged for over 300 years.
Corporations' structure, considered standard worldwide, was first created more than 300 years ago.
It was designed in an era of sailing ships crossing oceans and letters carrying information.
But is this system truly suitable for how companies and collaboration should function in the modern world?
With today’s technology, global economy, and new values, the speed and transparency required cannot be answered by rules from 300 years ago.
We are here to demonstrate a new answer.
### Our Driving Core
At the heart of this movement is our innovative model: Parallel Entity—a new corporational paradigm designed not just for the 21st century but for the future beyond.
Leveraging the power of blockchain, smart contracts, and decentralized technologies, we create organizations with:
\- Transparency
\- Efficiency
\- Limitless adaptability
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.borderless.company/english/borderless/who-we-are.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.