Start Guide

Get started with WyrdOS in 10 minutes by creating one traceable strategy-to-execution path

WyrdOS is most useful once work can be traced back to a reason. This guide creates one complete path:

Principle -> Pillar -> Goal Outcome -> Container -> Zone

Before You Start

You need:

Access to a WyrdOS workspace at app.wyrdos.app.
Permission to create engines, containers, and zones in that workspace.
A small example project. This guide uses Beta onboarding.

When you finish, you should be able to open a zone and answer:

What work is happening?
Which container owns it?
Which goal does it support?
Which pillar and principle explain why it matters?

1. Create Or Open A Workspace

Sign in at app.wyrdos.app. Create a workspace if you do not already have one, or open the workspace where your team plans work.

Checkpoint: the sidebar should show the main WyrdOS areas, including Engines and Pipelines.

2. Add One Principle

Open Engines -> Principles and create:

Field	Value
Name	Decisions should leave a trail
Description	Important work should make its reasoning visible later.

Checkpoint: the principle appears in the Principles list and can be opened again from its detail page.

3. Add One Pillar

Open Engines -> Pillars and create:

Field	Value
Name	Product clarity
Status	Active
Linked principle	Decisions should leave a trail

Checkpoint: the pillar detail page shows the linked principle.

4. Add One Goal Outcome

Open Engines -> Goal Outcomes and create:

Field	Value
Name	Beta users understand onboarding
Term	Short
Target date	Pick a real review date
Linked pillar	Product clarity

Checkpoint: the goal outcome is measurable and linked back to the pillar.

5. Add One Container

Open Pipelines -> Containers and create:

Field	Value
Name	Product
Status	Active
Priority	Medium
Linked pillar	Product clarity
Linked goal outcome	Beta users understand onboarding

Use the editor area for short context:

Owns product experience work for the beta launch.

Checkpoint: the container detail page shows its linked pillar and goal outcome.

6. Add One Zone

Open Pipelines -> Zones and create:

Field	Value
Name	Onboarding cleanup
Container	Product
Status	Active
Do date	Today or the next working date
Due date	The next review date
Linked goal outcome	Beta users understand onboarding

Use the editor area for the immediate work:

Review the first-run flow and record the top three confusing steps.

Checkpoint: the zone belongs to the Product container and points to the beta onboarding goal.

7. Check Traceability

Open the Onboarding cleanup zone and inspect its linked entities. Then move upward:

Zone: Onboarding cleanup
Container: Product
Goal outcome: Beta users understand onboarding
Pillar: Product clarity
Principle: Decisions should leave a trail

If any layer is missing, add the relationship before creating more work. A small complete graph is more useful than a large disconnected workspace.

Visual Checkpoints

The quickstart should be easy to verify visually. Capture or refresh these screenshots whenever the app UI changes:

Step	Capture target	Expected state
Workspace	`screenshots/quickstart/workspace-home.png`	Sidebar visible after sign-in.
Principle	`screenshots/quickstart/principle-detail.png`	Principle detail page open.
Pillar	`screenshots/quickstart/pillar-linked-principle.png`	Pillar shows linked principle.
Container	`screenshots/quickstart/container-linked-goal.png`	Container shows linked goal and pillar.
Zone	`screenshots/quickstart/zone-traceability.png`	Zone shows container and goal links.

Do not publish blurred or cropped screenshots that hide the relationship fields. If screenshots are not current, keep the table and update the assets before the next docs release.

Next Steps

Concepts explains the full entity model.
Engines explains principles, pillars, value goals, and goal outcomes in depth.
Pipelines explains containers, zones, actions, dates, and execution flow.
Ontology & Evidence explains graph review, evidence, and proposals.
Conventions explains index pages, filters, views, and detail pages.
Validate your workspace gives a checklist for spotting missing or stale links.
Support explains how to get help.