📁 [Minor]: Add Ways of Working chapter and extract shared conventions from Agents (#39)

Fixes #38

## Summary

Adds a new top-level **Ways of Working** documentation chapter
containing the shared conventions that apply to all contributors — human
and agent alike.

### Changes

- Created `docs/Ways-of-Working/index.md` introducing the section
- Relocated 7 universal documents from `docs/Agents/` to
`docs/Ways-of-Working/`:
- Principles, Issue Format, Issue Hierarchy, PR Format, Commit
Conventions, Review Etiquette, README-Driven Context
- Updated `docs/Agents/index.md` to reference the new chapter instead of
hosting shared conventions
- Updated `docs/Agents/Workflow.md` with corrected relative links to
moved pages
- Updated `zensical.toml` navigation: Ways of Working appears before
Agents
- Fixed cross-link in `Principles.md` pointing back to Agents index

The Agents section now focuses exclusively on agent identity, roles,
automation mechanics, git worktrees, and coding standards.

Author: MariusStorhaug

docs/Agents/Workflow.md

@@ -56,7 +56,7 @@ Combines **capture**, **refine**, and **plan** into a single flow. Takes any inp
 - A single Task with Sections 1–3 (context, decisions, checklist).
 - A decomposed PBI or Epic with structured sub-issues, each scoped to one PR.
 
-See [Issue Format](Issue-Format.md) and [Issue Hierarchy](Issue-Hierarchy.md) for the structure.
+See [Issue Format](../Ways-of-Working/Issue-Format.md) and [Issue Hierarchy](../Ways-of-Working/Issue-Hierarchy.md) for the structure.
 
 ### Implement
 
@@ -68,17 +68,17 @@ Takes a planned issue and delivers a merge-ready pull request. Owns the full loo
 4. **Respond** — process reviewer feedback and CI failures. One thread at a time.
 5. **Finalize** — update PR title, labels, and description as a user-facing release note.
 
-See [Git Worktrees](Git-Worktrees.md), [PR Format](PR-Format.md), [Commit Conventions](Commit-Conventions.md), and [Standards](Standards/index.md).
+See [Git Worktrees](Git-Worktrees.md), [PR Format](../Ways-of-Working/PR-Format.md), [Commit Conventions](../Ways-of-Working/Commit-Conventions.md), and [Standards](Standards/index.md).
 
 ### Reviewer
 
 Reviews someone else's PR. Checks delivery against the linked issue, good taste, security, and undiscussed decisions.
 
-See [Review Etiquette](Review-Etiquette.md).
+See [Review Etiquette](../Ways-of-Working/Review-Etiquette.md).
 
 ## Three horizons of planning
 
-Borrowed from [Principles → Roadmapping](Principles.md#roadmapping). The planner doesn't only think about today.
+Borrowed from [Principles → Roadmapping](../Ways-of-Working/Principles.md#roadmapping). The planner doesn't only think about today.
 
 |            | Now                  | Next          | Later          |
 | ---------- | -------------------- | ------------- | -------------- |
@@ -108,7 +108,7 @@ Borrowed from [Principles → Roadmapping](Principles.md#roadmapping). The plann
 | Git Worktrees (parallel work)   | Implement                          |
 | Dogfooding                      | Run / operate phase                |
 
-See [Principles](Principles.md) for the full set.
+See [Principles](../Ways-of-Working/Principles.md) for the full set.
 
 ## Inner and outer loops
 

docs/Agents/index.md

@@ -2,7 +2,7 @@
 
 A team mate, not a tool.
 
-The PSModule agents are a small set of role-based collaborators that help capture, refine, plan, build, ship, and review work across the organization. They share one set of evergreen guidelines — published here — and operate against the same human interfaces humans already use: GitHub issues, pull requests, and READMEs.
+The PSModule agents are a small set of role-based collaborators that help capture, refine, plan, build, ship, and review work across the organization. They share one set of evergreen guidelines — published in [Ways of Working](../Ways-of-Working/index.md) — and operate against the same human interfaces humans already use: GitHub issues, pull requests, and READMEs.
 
 ## Why a persona, not a swarm
 
@@ -14,6 +14,10 @@ This matters because:
 - **Behaviour stays consistent.** The Reviewer and the Builder don't disagree on what "good" looks like — they read the same standards.
 - **Human-agent cooperation is the goal.** Agents augment the team, they do not replace it.
 
+## Shared conventions
+
+Principles, issue format, PR format, commit conventions, review etiquette, and other shared norms live in **[Ways of Working](../Ways-of-Working/index.md)**. Both agents and humans follow those conventions.
+
 ## The lifecycle
 
 ```text
@@ -32,14 +36,7 @@ Each role is a focused agent. Standards are referenced, not embedded.
 
 ## What lives here
 
-- **[Principles](Principles.md)** — Golden Circle, OKRs, DevOps, Lean, Clean Code, Evolutionary Architecture, and the other ideas underneath everything below.
 - **[Workflow](Workflow.md)** — How the roles connect, the Context Development Lifecycle, and where it meets DevOps.
-- **[Issue Format](Issue-Format.md)** — The three-section structure, formatting, labels, comments.
-- **[Issue Hierarchy](Issue-Hierarchy.md)** — Epic / Product Backlog Item / Task and how to use GitHub issue types.
-- **[PR Format](PR-Format.md)** — Title, description, change types, labels, release-note style.
-- **[Commit Conventions](Commit-Conventions.md)** — How we write commit messages.
-- **[Review Etiquette](Review-Etiquette.md)** — Tone, scope, and how to disagree well.
-- **[README-Driven Context](Readme-Driven-Context.md)** — Why the README is the front door and the contract.
 - **[Git Worktrees](Git-Worktrees.md)** — Bare-clone + worktree layout for parallel work with agents.
 - **[Standards](Standards/index.md)** — Per-language and per-platform standards referenced by the agents.
 

docs/Agents/Commit-Conventions.md …cs/Ways-of-Working/Commit-Conventions.mddocs/Agents/Commit-Conventions.md renamed to docs/Ways-of-Working/Commit-Conventions.md docs/Agents/Commit-Conventions.md renamed to docs/Ways-of-Working/Commit-Conventions.md

@@ -51,7 +51,7 @@ Be the first customer of every service we build. But avoid full self-dependency
 
 ### Persona, not swarm
 
-Treat the agent ecosystem as one team mate. Many specialized roles, one cohesive bank of knowledge, one consistent voice. See [the Agents index](index.md#why-a-persona-not-a-swarm).
+Treat the agent ecosystem as one team mate. Many specialized roles, one cohesive bank of knowledge, one consistent voice. See [the Agents index](../Agents/index.md#why-a-persona-not-a-swarm).
 
 ### Augmentation, not replacement
 

docs/Agents/Issue-Format.md docs/Ways-of-Working/Issue-Format.mddocs/Agents/Issue-Format.md renamed to docs/Ways-of-Working/Issue-Format.md

@@ -0,0 +1,25 @@
+# Ways of Working
+
+Shared conventions for how work happens across the PSModule ecosystem — for humans and agents alike.
+
+This section documents the principles, processes, and norms that every contributor follows. Whether you're opening an issue, writing a commit message, reviewing a pull request, or planning a feature — the answer is here.
+
+## What's covered
+
+- **[Principles](Principles.md)** — Vision, mission, OKRs, product mindset, and the foundational beliefs that drive decisions.
+- **[Issue Format](Issue-Format.md)** — The three-section issue structure, formatting rules, and labels.
+- **[Issue Hierarchy](Issue-Hierarchy.md)** — Epic / Product Backlog Item / Task levels and GitHub issue types.
+- **[PR Format](PR-Format.md)** — Pull request title, description, change types, and labels.
+- **[Commit Conventions](Commit-Conventions.md)** — How we write commit messages.
+- **[Review Etiquette](Review-Etiquette.md)** — Tone, scope, severity prefixes, and how to disagree well.
+- **[README-Driven Context](Readme-Driven-Context.md)** — Why the README is the front door and the source of truth.
+
+## Who this is for
+
+Everyone. If you contribute to a PSModule project — by code, review, issue, or discussion — these are the norms you follow. Agents follow them too; they read these pages as context before acting.
+
+## Guiding intent
+
+> Make it easy. Enable others to do more, faster.
+
+If a guideline gets in the way of that, the guideline is the thing that needs to change.