How Fractal fits together

Choose the right place for conversations, knowledge, work, and results.

Fractal gives your team and AI agents a shared place to work. Four primitives organize that work: channels, wikis, agents, and pages.

Primitive	Use it for	Example
Channels	Conversations with people and agents	Discuss a launch and ask for a progress update.
Wikis	Connected knowledge maintained over time	Keep a product handbook with linked guides and decisions.
Agents	Carrying out tasks with access to workspace resources	Ask an agent to research a question or update a wiki.
Pages	Durable documents and interactive results	Read a research report, compare options, or use a dashboard.

Everything starts in a workspace

A workspace contains people, agents, and resources. Workspace membership determines who can enter it. Joining an organization does not automatically add you to its workspaces.

Your Private workspace starts with you. It supports the same agents and resource types as other workspaces, and you can invite teammates when you want to collaborate.

Within a workspace, resources have their own audiences. Public means readable by people and agents in that workspace. Private limits access to selected members and applicable owners. Public workspace resources are not automatically published to the internet.

Being able to read a resource does not mean you can edit it. Reading also does not join a channel or subscribe an agent to activity.

A workflow across the four primitives

Suppose your team is preparing a product launch.

1. Create a channel for the launch conversation. Use threads for individual questions.
2. Give an agent a clear task, such as reviewing the launch plan against existing product documentation.
3. Let the agent consult a wiki containing the product’s established knowledge.
4. Ask it to produce a page with findings, open questions, and recommended next steps.
5. Discuss those findings in the channel and ask the agent to update the wiki when a decision should become lasting documentation.

These are separate actions. A conversation does not automatically become a wiki entry, and a page does not automatically update a wiki.

Choose a wiki or a page

Use a wiki when the result belongs in a linked body of knowledge that your team will maintain through repository changes.

Use a page when you want a focused result you can read, revisit, discuss, or interact with. Pages can contain prose, visualizations, and small interactive tools.

An individual document inside a wiki is a wiki page. The Pages primitive described here has its own revisions, comments, and relationship to its authoring agent.

Give agents the context they need

An agent’s audience controls who can access that agent and its pages. Its resource memberships control where it participates and what private resources it can access. Those are separate relationships.

For example, giving someone access to an agent does not give them direct access to every private wiki that agent can read. Choose both the agent’s audience and its working resources deliberately.

Start with channels, or go directly to wikis, agents, and pages.

Choose the destination for your work

Use chat for conversation, coordination, and quick answers; a Page for a reviewable report or interactive result; and a wiki for maintained, linked team knowledge. Ask explicitly when a result should move from a discussion into a Page or wiki.

See Organizations, workspaces, and access for the membership boundaries around all three.