Knowledge becomes valuable when it is connected.
In AIOS, objects and relationships provide context for your work.
From document to context
A file rarely tells the whole story. Connect it to a customer, page or project. This makes it clear what the information relates to and who works with it.
Start with a question your team regularly needs to answer, such as “What is the current situation with this customer?” That determines which contacts, files and pages belong together. A relationship is most useful when it explains why a document matters. Avoid recreating the same content for every team when one shared, maintained source is enough.
Structure that fits
AIOS organizes objects through shared structures, forms and views. Custom fields and models help reflect how you work. Begin with a few clear fields and extend them when a concrete need emerges.
Give fields a clear meaning before extending the model. “Status” is of little use if sales and the project team interpret it differently. Record what a field means, which values are useful and who maintains it. Use custom fields when they support a recurring decision; longer explanations and background knowledge can remain on a related page.
AIOSDesign access deliberately
Shared context does not mean everyone sees everything. Permissions determine access. When adding content and connections, consider which people and processes need them.
Maintain context after creating it. Before an important task, check whether related documents still apply and whether the people involved can open them. A link creates a connection but does not grant permission. If a document must remain confidential, clarify the collaboration and access required instead of copying its content into more objects without a clear purpose.
Try it yourself
Adapt the placeholders to your task. This example is a template for your work with AIOS.
Task or decision: [What is this context needed for?]
Central object: [Contact, customer, project or another object]
Authoritative source: [File/page and version or date]
Supporting sources: [Source → why it matters]
Terms and fields: [Name → unambiguous meaning]
Maintained by: [Person or team]
Open conflicts: [What still needs clarification?]
Required access: [People/processes and purpose]
Next review: [Event that should trigger another context check]Where should each piece of information go?
| Information | Practical starting point |
|---|---|
| A recurring, short value | A clearly defined field on the appropriate object. |
| Background and reasoning | A page or document connected to the object. |
| Original material | A maintained source file with a clear name and identifiable version or date. |
| Relationship to a customer or project | A meaningful relationship instead of another copy. |