Our company knowledge is scattered.
Important context lives across documents, systems, procedures, and people. Find a clearer way to organise and use it.
Catalogue
What are you trying to understand or improve?
Start with the challenge you recognise, or search the published knowledge across the three layers. No ranking is faked: results are ordered by relevance when you search, and alphabetically when you do not.
We need clearer engineering context.
Explore how connected project information can help teams investigate revisions, dependencies, decisions, and delivery risks.
We want AI tools with controlled access.
Understand how approved tools and workflows can be connected to information they are permitted to use.
AI systems do not explain our business clearly.
Make public business information clearer, more structured, and easier for people and AI systems to interpret.
Browse by layer: EchOS · OIL · ORBIT
21 results
Status is the entry’s stage in the content registry, not whether a product exists. Application availability is stated on Applications.
- Aisend: one connected architecture
Aisend brings private company knowledge, controlled orchestration and public knowledge into one connected architecture.
systemoverviewIn review
- Being understandable to AI systems
Structured public knowledge is intended to reduce ambiguity when systems retrieve or summarise a business.
orbitexplainerIn review
- Controlled access is a boundary
A tool should receive the information and permissions needed for its task, not unrestricted access to the company.
oilexplainerIn review
- EchOS: the company brain
EchOS is the intended private knowledge and context layer of the Aisend architecture.
echosoverviewIn review
- Evidence has a lifespan
A verified statement needs review when its source, implementation or operating conditions change.
orbitexplainerIn review
- Evidence people can inspect
Citation-grade content connects a specific statement to an accessible source and explains what that source does and does not establish.
orbitexplainerIn review
- From intent to a controlled workflow
Orchestration turns a request into explicit steps with inputs, permissions, checks and a visible outcome.
oilexplainerIn review
- From private knowledge to public knowledge
Publication is a deliberate boundary between company intelligence and information approved for the outside world.
systemexplainerIn review
- Human approval checkpoints
Sensitive actions need a specific approval tied to the actual action, target and content.
oilexplainerIn review
- Interchangeable tools, stable responsibilities
OIL is intended to let tools change without forcing the whole company knowledge model to change with them.
oilexplainerIn review
- Measure discovery without inventing certainty
Track what people and external systems actually find, understand and cite.
orbitexplainerIn review
- OIL: controlled orchestration
OIL is the intended controlled access and orchestration layer between company knowledge and the tools that use it.
oiloverviewIn review
- One entry, one clear subject
Atomic knowledge entries keep important answers focused, addressable and easier to update.
orbitexplainerIn review
- ORBIT: public knowledge with structure
ORBIT is the public knowledge and visibility layer of the Aisend architecture.
orbitoverviewIn review
- Organising company knowledge
Company knowledge becomes useful when information is identified, structured and connected to its source.
echosexplainerIn review
- Ownership, permissions and review
Useful company intelligence needs clear responsibility for what is stored, who can use it and when it should be reviewed.
echosexplainerIn review
- The Proof Registry
The Proof Registry is the intended place to connect specific public claims to scoped, dated evidence.
orbitexplainerIn review
- What belongs in a tool contract?
A tool contract defines the task boundary, expected data, permissions and failure behaviour.
oilexplainerIn review
- What is a company knowledge catalogue?
A company knowledge catalogue organises public information as linked entries rather than relying only on a sequence of marketing pages.
orbitexplainerIn review
- What makes a company brain “living”?
A living knowledge layer connects reference information to changing business context, within explicitly implemented limits.
echosexplainerIn review
- Zara: a guide through the intelligence centre
Zara helps visitors ask questions and open relevant published knowledge across the Aisend architecture.
systemoverviewIn review