Validate Your Workspace
Check whether WyrdOS is complete enough to trust for planning and decisions
WyrdOS is trustworthy when the important work has context, ownership, and a visible reason. Use this checklist before relying on a workspace for planning reviews or agent workflows.
Fast Audit
Start with one active piece of work and move upward:
- Open an active Zone.
- Confirm it belongs to the right Container.
- Confirm it links to at least one relevant Goal Outcome or Value Goal.
- Confirm that goal connects to a Pillar.
- Confirm the pillar reflects a real Principle.
If the chain breaks, fix the missing relationship before adding more entities.
Health Checks
| Check | Healthy | Needs repair |
|---|---|---|
| Principles | Short, decision-oriented, still true | Generic values nobody uses |
| Pillars | Few enough to guide tradeoffs | Too many themes or no active owner |
| Goal outcomes | Specific, dated, measurable | Vague goals with no target date |
| Containers | Own broad areas of work | Duplicate or unclear ownership |
| Zones | Actionable and dated | Work item with no date, owner, or container |
| Pages | Capture decisions and reference material | Old notes with no linked context |
| Directory | Tools, contacts, and funding link to work | Static inventory disconnected from active work |
Common Symptoms
| Symptom | Likely cause | Inspect | Repair |
|---|---|---|---|
| Team cannot explain why a zone exists | Missing goal or pillar link | Zone detail sidebar | Link the zone to a goal outcome and container |
| Container list feels noisy | Containers are being used for tasks | Containers index page | Move small work into zones or actions |
| Goals are not reviewed | Missing target dates or terms | Goal Outcomes | Add term and target completion date |
| Strategy feels disconnected from work | Pillars are not linked downward | Pillars and Containers | Link active containers to the relevant pillar |
| Agent or script returns too much context | Filters or relationships are too broad | CLI context, API list filters | Narrow containers, statuses, and relationships |
| Users distrust old evidence | Pages or evidence are stale | Linked pages, evidence APIs | Add fresh source material or mark stale context |
CLI Checks
Use the CLI when you need a structured audit surface:
wyrdos auth check --output json
wyrdos context --output json
wyrdos engines summary --output json
wyrdos plan today --output jsonThe output should show the current workspace, relevant containers, active zones, and strategic context. If a command returns empty or unrelated data, inspect authentication, organisation scope, and entity links.
API Checks
For scripts and agents, start with:
curl -H "Authorization: Bearer <API_KEY>" \
"https://<your-wyrdos-api-host>/api/v1/engines/context?organisationId=<organisationId>"Then compare the response with the workspace UI. The API should not be the only place where a relationship makes sense; it should expose the same operating graph users can inspect.
Done Criteria
A workspace is ready for recurring reviews when:
- Active zones have containers and dates.
- Active containers link to goals or pillars.
- Current goals have target dates.
- Critical decisions have pages or evidence.
- API keys used by agents have only the permissions they need.
- Support or enterprise questions have a named owner.
If any of these fail, keep the workspace in setup mode and repair the graph before using it for team-level decisions.
All rights reserved.