Pages & Documents

Pages and documents are where WyrdOS stores the context that does not fit cleanly into a status, date, or relationship field. They preserve decisions, assumptions, plans, handoff notes, research, and source material. Operators use them to keep work explainable. Buyers should read them as the part of WyrdOS that prevents operating knowledge from living only in chat or memory.

The practical rule is simple: structured fields tell WyrdOS how to organise work; pages and documents explain the judgement behind that work.

Pages

Pages are general-purpose documents. They can hold notes, decisions, reference material, meeting outcomes, research summaries, or source excerpts. They use a rich editor and can be organised with folders, types, categories, and container relationships.

Use a page when the content is flexible and may support more than one workflow:

• Launch decision notes
• Onboarding research
• Customer interview summary
• Product assumptions
• Internal operating checklist
• Evidence review notes

Pages can be linked to containers. A linked page becomes part of the operating context for that container. This is useful when a work area needs background material without turning every note into a task.

Container-Linked Pages

Container-linked pages are the bridge between general knowledge and active work. A page such as Beta onboarding review can live in Pages, but linking it to the Product container tells WyrdOS that this material belongs in that operating context.

Use container-linked pages when:

• A decision affects a specific work area.
• Research should travel with the container.
• An operator needs quick access from a container detail page.
• API or CLI workflows need to list pages related to a container.

Avoid linking every page to every container. A page should be linked because it helps explain or operate that container.

Master Documents

Master documents are more structured container documents. They are useful when a container needs a repeatable document type, such as a design document, go-to-market document, or another workspace-specific template.

Compared with pages, master documents are more formal. They belong to a container and document type. They can be created from templates, updated over time, and shared or restricted by document type in container sharing flows.

Use master documents when:

• The team needs a standard document shape.
• The document should always belong to a container.
• A buyer or reviewer expects a repeatable handoff artifact.
• A workflow benefits from default sections.

For example, a Product container might have a Design Document for onboarding changes and a Go To Market document for launch readiness. Both can sit beside zones and actions while preserving deeper context.

Templates

Templates reduce inconsistency. WyrdOS supports default content templates for entity bodies and master document templates for repeatable document types. A template can pre-fill an editor with headings, prompts, and expected sections.

Use templates when:

• New entries need a consistent structure.
• You want operators to capture the same fields each time.
• Reviewers need predictable documents.
• A team is onboarding new users into a workspace.

Templates should guide writing, not create noise. A good template helps someone write a better entry. A bad template adds empty headings that nobody fills in.

Decision Capture

Pages and documents are most valuable when they capture decisions close to the work. A decision entry should include:

This structure is useful for operators and buyers. Operators can recover context quickly. Buyers can see whether the organisation's claims are backed by written reasoning.

What You Can Do In WyrdOS

In Pages, you can:

• Create pages and folders.
• Search and filter pages.
• Set type, category, folder, and container relationships.
• Move pages between folders.
• Link and unlink pages from containers.
• Open page detail views for editing.

In containers, you can:

• Review linked pages.
• Open master document areas.
• Create documents from template types.
• Keep container context beside zones, actions, and ontology.

In Settings, you can:

• Manage templates for entity types.
• Manage master document types and templates.
• Configure categories and types used for organisation.

Example Workflow

For beta onboarding:

1. Create a Product container.
2. Create a page called Beta onboarding review.
3. Capture the top onboarding problems, source notes, and product decisions.
4. Link the page to the Product container.
5. Create an Onboarding cleanup zone from the container.
6. Create a design document from the Product container if the work needs a formal spec.
7. Link evidence to the relevant goal outcome or container when source material should be reviewable.

The result is a work area with executable actions and durable context.

What Good Usage Looks Like

Strong pages and documents:

• Decisions live near the containers they affect.
• Templates make writing easier and more consistent.
• Important pages have clear names, summaries, and relationships.
• Formal documents are used for repeatable artifacts, not every note.
• Source material is linked as evidence when it supports a claim.

Weak pages and documents:

• Pages become an unorganised archive with no container links.
• Templates are too long, so users leave them blank.
• Master documents duplicate pages without adding structure.
• Important decisions stay in chat and never reach the operating record.
• Buyers cannot tell which document is current.

Trust Notes For Buyers

Pages and documents build trust by preserving context. They help answer: What did the team decide? Why did it decide that? Which source supported the decision? Where does the work live now?

WyrdOS should not claim that pages alone create governance. The trustworthy behaviour is the combination of linked pages, structured relationships, evidence, templates, and reviewable container context.

Automate This

Use API and CLI references when pages or documents need to be imported, linked, or exported:

• Pages API
• Containers API
• CLI pages commands