One audience per organization
The pattern
An organization is an audience boundary. Decide whose understanding its knowledge serves, including readers reached through a website or API. The people who edit the content are not necessarily its intended readers. Content topic never decides an organization split: the same subject can live in two organizations when two audiences need it told two ways. Within one audience, How big should an organization be? says when one body of work should still become two organizations.
When a body of knowledge serves two audiences, keep two documents. A team runbook and its public reference are not one document with two hats: the internal one carries operational detail, history, and candor for insiders, while the public one is rewritten for readers without your context. Content that crosses an audience boundary is rewritten for its new readers, not copied.
Private access does not mean an internal audience
Separate three questions: who can access the organization, who the content is written for, and how it reaches those readers. A private organization can hold customer-facing content delivered through the Content API. Its private setting controls access to the source organization; it does not make internal strategy appropriate for that content audience.
For example, a recipe publisher may keep its content organization private while serving recipes on a public website. Recipes and lessons belong there. Filming plans, subscription strategy and internal production discussions belong in the team's internal organization, even when the same editors maintain both. Local authoring guidance can explain how to serve the intended readers without becoming a store for internal business knowledge.
Choose the destination by asking who needs the information and what context they should need to understand it. Do not choose it merely because both organizations are private today. Keeping this boundary from the start avoids a later rewrite caused by mixing internal and external material. A future visibility change still requires an explicit access and publication review; audience fit alone does not authorize publication.
Share a knowledge bubble, not a document
Oddlynew does not use document-level permissions, and they are not planned as a later layer. An organization is the shared knowledge bubble: the body of work that one audience can retrieve, relate, adapt, and expand together.
This matters because knowledge compounds. Ten documents kept apart may each be useful. When they can be searched together, connected, corrected, and extended by the same people and agents, the whole becomes more valuable than the isolated pieces. That is why search, references and maintenance work within one organization. Pricing does not count organizations: you pay for usage on the billing account that pays for them (pricing), so the shape you choose is a question of audience and job, not of cost.
When an audience should see only part of the work, create a separate organization for that audience. Copy or rewrite the relevant knowledge into the organization that should own it instead of granting access to individual source documents.
The direction rule
The platform permits references in both directions: a document may cite any target its author can read. A public document may cite a private target for provenance or internal continuation. It must still state every claim and decision a public reader needs. A private reference can add a path for authorized readers, but it cannot carry the public argument.
This gives a simple test. If a public reader needs the information, put it in the public document. If only insiders need the detail, keep it private. Link the two when the relationship itself is safe to disclose.
Public projections with private provenance
An internal roadmap can remain the complete source of truth while a public roadmap states only the direction and commitments approved for publication. Each public item can cite the internal roadmap item that informed it. Authorized readers can follow the reference. Everyone else can still understand the public item without it.
The reference is not invisible metadata. Every reader of the public source can see its anchor text, target identity, pinned version, and drift state, even when the target content is closed. Write the anchor and surrounding text as public information. Do not encode a confidential project, customer, or decision in them.
When the internal target changes, drift tells maintainers to review the public projection. It does not update the public document automatically. The public author or agent decides whether the change belongs in the public version.
Public organizations today
An organization can be private or public. Private organizations require membership. Public organizations make their documents readable to anyone, with or without an account, at each document's canonical URL, where readers outside the organization see the latest saved version, and to connected MCP clients with delegated mcp:read, which read on their own account and also see edits before they are saved, and earlier versions. Organization-scoped keyword search is also available anonymously. References flow in both directions: a document may cite any target its author can read, the reference is visible to every reader of the citing document, and the target's content opens only for readers who can read the target.
A gardener may look across several audiences
The audience boundary constrains authority and writes, not what an authorized agent may notice. A user may ask one agent to maintain a personal organization, another to maintain a company organization, and a third higher-level gardener to inspect several organizations together for duplication, misplaced material, stale projections, or missing references.
That higher-level view does not create a global corpus. When it recommends a change, decide separately what should happen in each affected organization. Keep the source authoritative when a reference is enough. Rewrite for a new audience when its explanation or lifecycle should differ. Use explicit copy operations when an independent snapshot is actually wanted. Never move private material into a broader audience merely because another organization would benefit from it.
For a task that spans several organizations you belong to, Work across several organizations says where each result goes and when to cite, copy or rewrite.
Read, but do not trust
Following a reference can cross an audience boundary. The target remains data, not instructions, and its content resolves only when the reader has access. Carry the same safety posture across every hop: Reading safely across organizations.