Atlas of the nine vaults

Knowledge, work and learning

An organization learns when it can recover what it knew, why it acted, what outcome it found and what changed afterwards. Symbiontes is an architecture under development that connects this memory to people, methods, capabilities and tools.

Nine vaults organize different functions of that work. Bridges preserve the relationships through which people collaborate, verify a contribution and incorporate it without losing its origin. Records already exist in systems and files; integration and maturity continue to be developed and demonstrated for each part.

A vault is a domain of continuity: it preserves a kind of knowledge, the problems it addresses and the history of its changes. Context, methods, capabilities, versions and evidence may be distributed across existing containers.

The term does not mean an isolated folder, a security product or a complete copy of the system. A page may identify an object, a file may preserve its deliverable and a relationship may show which vault it participates in. Identity, reference and destination make the organization recoverable.

Direction, proposal, record, observed use and demonstrated outcome are different milestones. A published document establishes the existence of that version; the quality of its use needs its own evidence.

A bridge preserves a working relationship

A bridge organizes collaboration or passage around a problem. It preserves the question, participants, sources, contributions, disagreements and conditions for continuation. It may span multiple missions and conversations without acquiring a new identity whenever a tool changes.

Within a vault, different bridges may investigate problems, develop capabilities or evaluate outcomes. Across vaults, a bridge connects an originating need to a contribution from another function and to feedback showing how that contribution was used.

A bridge situated in one vault can organize passage between functions. Location, relationship and responsibility are distinct dimensions. Ownership of each action remains identifiable even when the problem is shared.

What makes the pattern fractal

The cycle can recur in an object, a capability, a vault or a composition: context → problem → collaboration → verifiable contribution → authorized incorporation → learning and continuity.

The part keeps a relationship with the whole. A change of scale states the object being observed, the participants involved and the boundaries of the scope. A diagram helps explain composition; operation needs its own records and checks.

S, H and SH across scales

S and H identify positions within a stated relationship. In the conceptual vocabulary, symbiont, host and symbiosis describe distinct roles: a participating contribution, the context receiving it and the relationship built between them.

In the current diagram, S and H retain their bridges and are separated by a membrane. SH coordinates the composition at that scale. In a larger frame, the previous whole may occupy H while the previous coordination occupies S. The notation tracks this shift without turning labels into permanent identities.

Executors are peers. A person, an AI or a tool does not gain authority by occupying a position in the diagram. Mandate, assignment, real access and responsibility bound each action. Conceptual SH does not require a third independent executor.

The membrane preserves boundaries

The membrane represents a governed boundary: what may cross, in which direction, for what purpose and with what return. It enables cooperation without assuming that identities, collections or permissions merge.

A contribution may circulate by reference. Sharing a space, knowing an address or viewing a file does not imply access to every related collection.

From diagrams to systems

In the documented arrangement, Notion holds records, contracts, relationships and returns; Drive holds addressable files and artifacts. Executing tools act on bounded inputs and return results to the relevant source.

The mapping is functional. It does not require nine identical folders, nine independent databases or a symmetrical copy of every vault in every platform. One deliverable can serve several relationships by reference, preserving the source and avoiding competing versions.

Tools are current means with their own capabilities and limits. The architecture needs to preserve identity, continuity and history even when a means is revised.

Three kinds of version

A contribution has its own version and authorship. A vault records what it incorporated and under which conditions. A composition records which versions it uses together.

A local change affects the parts that depend on it. History makes it possible to check the delta, understand the impact and recover the previous arrangement.

A fictional workshop

An entirely synthetic scenario: an organization prepares a two-day workshop with one room and two facilitators. It needs materials, registration and a programme. No real person, client or operation is represented.

1 · C1 gathers context

Dates, resources, requirements and dependencies are related. Room availability on the second day remains an explicit gap.

2 · C2 recovers a method

Before finalizing the programme, the resource supporting the in-person activities must be confirmed. The method retains the alternative of making part of the workshop asynchronous.

3 · C3 brings capabilities

One capability compares schedule constraints and another prepares materials. A responsible person confirms the information that depends on them.

4 · C4 composes the work

Materials and registration can progress while the final programme depends on the room. The dependency does not stop all work, and silence is not treated as confirmation.

5 · C5 supports the conversation

A spoken synthesis explains the dependency and two options in plain language. Feedback is recorded so the next session starts from what has already been clarified.

6 · The bridge preserves feedback

The scheduling capability receives confirmed information, updates the proposal and returns the version. Its consumer checks the change and its usefulness.

7 · C2 receives learning

If the early check prevented rework, the record describes what was observed, its scope and the conditions for reuse.

8 · C7 examines a means when needed

An additional tool enters evaluation only if a difficulty remains inadequately addressed by the existing means.

9 · C6 preserves a possibility

Adapting the workshop to another context can become a possibility to develop. Preserving it does not automatically activate a new operation.

10 · C8 and C9 investigate the composition

C8 examines a recurring architectural problem. C9 may formulate a hypothesis if a qualitatively new capability appears. Every task does not need to involve all nine vaults.

What the journey shows

Useful collaboration depends on identity, input, output, ownership, a consumer and feedback. Message or file counts do not, by themselves, measure the outcome.

Two ways to recognize progress

A useful outcome improves a situation and leaves continuity. Learning compares an action with its outcome and helps confirm, contradict or reformulate a method. The same work may produce both, or deliver an outcome without new learning.

In the project vocabulary, Moeda 1 names useful progress and continuity. Moeda 2 requires learning supported by origin and evidence. Repeating a record across destinations does not multiply the learning. When no new learning exists, its absence can be recorded without inventing a conclusion.

Maturity belongs to the object

Bagunça, Bronze, Prata, Ouro and Diamante name ways of examining the development of a bounded scope. Criteria identify which context, method, capability or composition is being evaluated. The state of one part does not automatically promote an entire vault or the whole system.

The site distinguishes what has been described, produced, used and demonstrated. A visually complete proposal remains a proposal until its relevant evaluation. A successful experience remains bounded by the conditions in which it occurred.

Responsibility and continuity

Each action needs an owner and a scope. Preparing a decision helps a person decide; it does not perform the act reserved to that person. Cooperation between people and AI preserves this distinction and the history needed to resume, correct or reverse the work.

Sources remain connected to the claims they support. An integrity record confirms the object checked, while access, operation and outcomes are verified in their own contexts.