@equal-experts/kuat-vue 0.13.1 → 0.14.0-beta.0

package/agent-docs/AGENTS.md

@@ -7,4 +7,4 @@ Rules for this install live under `agent-docs/` in `@equal-experts/kuat-core`, `
 3. Load component guides via `agent-docs/components.manifest.json`.
 4. Skills: `kuat-review`, `kuat-create` from [kuat-agent-docs](https://github.com/equalexperts/kuat-agent-docs).
 
-**Version:** 0.13.1 · **Rules snapshot:** 67fc215fe87c
+**Version:** 0.14.0-beta.0 · **Rules snapshot:** 538afc80d437

package/agent-docs/README.md

@@ -14,4 +14,4 @@ Curated agent docs bundled with `@equal-experts/kuat-core`, `@equal-experts/kuat
 node scripts/agent-docs/bundle-for-core.mjs
 ```
 
-Built against upstream ref: `67fc215fe87c`
+Built against upstream ref: `538afc80d437`

package/agent-docs/bundle-manifest.json

@@ -18,36 +18,28 @@
       "target": "components"
     },
     {
-      "source": "external/kuat-agent-rules/kuat-docs/rules/foundations/brand.md",
-      "target": "external/kuat-agent-rules/kuat-docs/rules/foundations/brand.md"
+      "source": "external/kuat-agent-rules/reference/brand",
+      "target": "external/kuat-agent-rules/reference/brand"
     },
     {
-      "source": "external/kuat-agent-rules/kuat-docs/rules/foundations/accessibility.md",
-      "target": "external/kuat-agent-rules/kuat-docs/rules/foundations/accessibility.md"
+      "source": "external/kuat-agent-rules/reference/accessibility",
+      "target": "external/kuat-agent-rules/reference/accessibility"
     },
     {
-      "source": "external/kuat-agent-rules/kuat-docs/rules/LOADING.md",
-      "target": "external/kuat-agent-rules/kuat-docs/rules/LOADING.md"
+      "source": "external/kuat-agent-rules/reference/design-language",
+      "target": "external/kuat-agent-rules/reference/design-language"
     },
     {
-      "source": "external/kuat-agent-rules/kuat-docs/rules/foundations/design",
-      "target": "external/kuat-agent-rules/kuat-docs/rules/foundations/design"
+      "source": "external/kuat-agent-rules/reference/content",
+      "target": "external/kuat-agent-rules/reference/content"
     },
     {
-      "source": "external/kuat-agent-rules/kuat-docs/rules/foundations/content",
-      "target": "external/kuat-agent-rules/kuat-docs/rules/foundations/content"
+      "source": "external/kuat-agent-rules/reference/media-types/web-product",
+      "target": "external/kuat-agent-rules/reference/media-types/web-product"
     },
     {
-      "source": "external/kuat-agent-rules/kuat-docs/rules/foundations/logo.md",
-      "target": "external/kuat-agent-rules/kuat-docs/rules/foundations/logo.md"
-    },
-    {
-      "source": "external/kuat-agent-rules/kuat-docs/rules/types/web/product",
-      "target": "external/kuat-agent-rules/kuat-docs/rules/types/web/product"
-    },
-    {
-      "source": "external/kuat-agent-rules/kuat-docs/rules/types/web/marketing",
-      "target": "external/kuat-agent-rules/kuat-docs/rules/types/web/marketing"
+      "source": "external/kuat-agent-rules/reference/media-types/web-marketing",
+      "target": "external/kuat-agent-rules/reference/media-types/web-marketing"
     }
   ],
   "denyPathSegments": [

package/agent-docs/components/components.manifest.json

@@ -3,16 +3,19 @@
   "components": {
     "shadcn:button": {
       "slug": "button",
+      "displayName": "Button",
       "path": "components/button.md",
       "sources": ["shadcn:button", "@equal-experts/kuat-core"]
     },
     "kuat:button-group": {
       "slug": "button-group",
+      "displayName": "ButtonGroup",
       "path": "components/button-group.md",
       "sources": ["@equal-experts/kuat-react", "@equal-experts/kuat-vue"]
     },
     "kuat:kuat-header": {
       "slug": "kuat-header",
+      "displayName": "KuatHeader",
       "path": "components/kuat-header.md",
       "sources": ["@equal-experts/kuat-react", "@equal-experts/kuat-vue"]
     }

package/agent-docs/external/kuat-agent-rules/reference/accessibility/README.md

@@ -0,0 +1,7 @@
+# Accessibility
+
+Equal Experts accessibility standards, applied across every medium.
+
+| File | Scope |
+|------|-------|
+| [accessibility.md](./accessibility.md) | WCAG 2.2 AA standards: contrast, focus, semantics, alt text |

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/foundations → reference/accessibility}/accessibility.md

@@ -1,7 +1,3 @@
----
-scope: general
----
-
 # Accessibility
 
 Foundational accessibility requirements for Equal Experts content and products. These rules ensure products and services deliver the best experience for all users.
@@ -371,11 +367,17 @@ Always spell out abbreviations on first use:
 
 ## Inclusive Language
 
+Inclusive language is part of how Equal Experts writes — it helps us be accurate and build trust. Around 16% of people worldwide experience some form of disability, so it matters that we don't unintentionally exclude anyone from accessing or understanding our work. This section is the authoritative source for inclusive word choices across all content; the [writing style](../content/writing-style.md) guidance links here.
+
 ### Guidelines
 
 - Use language that is respectful and free of bias
-- Avoid exclusionary terms or outdated phrases
-- Consider diverse audiences and perspectives
+- Avoid terms that contribute to stigmas around disability or mental illness
+- Make content **gender-neutral** wherever possible, and avoid words and phrases that indicate gender bias
+- Avoid words, images, or situations that reinforce racial, ethnic, or religious stereotypes
+- Be considerate with computer and software terminology such as "master", "slave", and "blacklist" — prefer neutral alternatives (for example "main", "primary/replica", "blocklist")
+- Avoid assumptions: when including someone in a piece of content, ask how they'd like to be identified
+- Avoid idioms where possible, or make sure they're clearly explained — they don't always translate across cultures or for non-native readers
 - When in doubt, research current preferred terminology
 
 ### Person-First Language
@@ -438,7 +440,7 @@ Always spell out abbreviations on first use:
 
 ## Related Documentation
 
-- [Colours](./design/colours.md) - Brand colour palette and contrast
-- [Typography](./design/typography.md) - Font families and type scale
-- [Content](./content/README.md) - Writing style and tone
-- [Web Technical Accessibility](../types/web/product/accessibility.md) - Implementation details
+- [Colours](../design-language/colours.md) - Brand colour palette and contrast
+- [Typography](../design-language/typography.md) - Font families and type scale
+- [Writing style](../content/writing-style.md) - Writing style and tone
+- [Web Technical Accessibility](../media-types/web-product/accessibility.md) - Implementation details

package/agent-docs/external/kuat-agent-rules/reference/brand/README.md

@@ -0,0 +1,9 @@
+# Brand
+
+Equal Experts brand identity: who EE is and how the brand expresses itself.
+
+| File | Scope |
+|------|-------|
+| [brand.md](./brand.md) | Brand principles and identity |
+| [logo.md](./logo.md) | Logo variants, sizing, placement, clear space |
+| [voice-and-tone.md](./voice-and-tone.md) | Voice, tone, audience, content quality |

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/foundations → reference/brand}/brand.md

@@ -18,21 +18,31 @@ Equal Experts is a network of experienced software consultants, helping organisa
 
 ## Brand Values
 
-### 1. Expertise Through Experience
+The Equal Experts values act as principles of how we work with our customers. They are intended to give all members of the network autonomy in making decisions that are aligned with the way we want to behave, as well as how we want to be recognised.
 
-We hire only experienced consultants. Our expertise comes from years of hands-on work, not certifications or titles.
+### 1. We deliver as teams of equals
 
-### 2. Equality and Collaboration
+Teams are greater than the sum of their parts. No matter what role people play in a team, they all have something to contribute, and they all have a voice in delivery decisions.
 
-Everyone is equal. We work alongside clients as partners, not vendors. No account managers, no hierarchy - just experts working together.
+### 2. We prioritise outcomes over approach
 
-### 3. Honesty and Transparency
+We work in complex and highly dynamic environments. We’re not interested in a cookie-cutter approach.
 
-We tell clients what they need to hear, not what they want to hear. We're direct about risks, challenges, and realistic outcomes.
+### 3. We narrow our focus but widen our context
 
-### 4. Pragmatism Over Perfection
+We deliver concrete value as early as possible by quickly identifying key opportunities, but framing them within the wider organisational context.
 
-We focus on delivering value, not following processes for their own sake. We choose practical solutions that work in the real world.
+### 4. We bring step-by-step change
+
+It can be tempting to look for a WOW factor, but we know that lasting change is best achieved through small, incremental practices that build towards larger transformation.
+
+### 5. We have a passion for learning over knowing all the answers
+
+We may be experts, but we don’t pretend to know all the answers.
+
+### 6. We seek customer success over our own short-term interests
+
+We thrive by our reputation, so the only way to guarantee our future success is to do what’s right, right now, for our customers.
 
 ---
 
@@ -94,6 +104,6 @@ When representing Equal Experts:
 ## Related Documentation
 
 - [Logo Usage](./logo.md) - Logo variants, sizing, placement
-- [Colours](./design/colours.md) - Brand color palette
-- [Typography](./design/typography.md) - Brand fonts
-- [Content](./content/README.md) - Writing style and tone
+- [Colours](../design-language/colours.md) - Brand color palette
+- [Typography](../design-language/typography.md) - Brand fonts
+- [Reference index](../README.md) - All brand reference guides

package/agent-docs/external/kuat-agent-rules/{kuat-docs/rules/foundations → reference/brand}/logo.md

@@ -121,9 +121,10 @@ The brand mark (without wordmark) should only be used when:
 
 For platform-specific logo placement guidance:
 
-- **Web layouts** - See [types/web/](../types/web/)
-- **Slides** - See [types/slides/](../types/slides/)
-- **Graphics** - See [types/graphics/](../types/graphics/)
+- **Web product** - See [media-types/web-product/](../media-types/web-product/)
+- **Web marketing** - See [media-types/web-marketing/](../media-types/web-marketing/)
+- **Slides** - See [media-types/slides/](../media-types/slides/)
+- **Graphics** - See [media-types/imagery/patterns/graphics/](../media-types/imagery/patterns/graphics/)
 
 ---
 
@@ -148,4 +149,4 @@ All logos are available in the [Equal Experts brand-assets repository](https://g
 ## Related Documentation
 
 - [Brand Guidelines](./brand.md) - Brand principles
-- [Colours](./design/colours.md) - Brand color palette
+- [Colours](../design-language/colours.md) - Brand color palette

package/agent-docs/external/kuat-agent-rules/reference/brand/voice-and-tone.md

@@ -0,0 +1,166 @@
+# Voice and Tone
+
+Universal voice and tone for Equal Experts content. Applies to all platforms and media.
+
+---
+
+## Overview
+
+It's not just *what* we say but *how* we say it that matters. A consistent voice — aligned with our vision, mission, and values — helps us speak to our audience clearly, reflects our culture, and differentiates us from the competition. If the voice isn't reflective of Equal Experts, our work, and our values, we risk key messages being misunderstood or overlooked.
+
+Our **voice** is constant: it's who we are. Our **tone** flexes to suit the audience, channel, and purpose.
+
+---
+
+## Quick Reference
+
+**Always:**
+- Be friendly, clear, and approachable — one human to another
+- Be confident, but never arrogant; back claims with evidence
+- Focus on the audience and their needs
+- Use plain language; be specific, not vague
+- Be consistent across channels and materials
+
+**Never:**
+- Make bold claims without backing them up
+- Hide behind jargon, acronyms, or buzzwords
+- Talk down to, over-simplify for, or patronise the audience
+- Overuse "we" so the content reads as boastful
+- Mix and match tones and styles within a piece
+
+---
+
+## How We Describe Equal Experts
+
+Equal Experts is a global network of technology shapers. We work collaboratively with clients on digital initiatives that deliver long-lasting change and pragmatic innovation. Engaging around 3,000 consultants across five continents, we help solve complex business problems and create leading digital products and services. We decide with data, design for users, deliver at pace, and scale sustainably.
+
+What makes us unique: we engage only senior consultants (averaging around 18 years' experience), we're low-ego and curious, we're vendor-agnostic and don't offer cookie-cutter solutions, and our flexible global delivery model means we're not limited by geography.
+
+---
+
+## Writing in the Equal Experts Voice
+
+**Friendly, clear, and approachable.** We speak from one human to another. Though we work with cutting-edge technology, we're not robots and neither are our customers. Content is clear, concise, and purposeful, but reflects how we'd speak face-to-face. Gentle humour is welcome when it arises naturally, is appropriate, and will be widely understood.
+
+**Confident, but never arrogant.** With a word as powerful as "expert" in our name, we embody it with humility. We show our knowledge through tangible results and a passion for learning. We're confident without being condescending, and knowledgeable without being know-it-alls.
+
+**Focused on the audience.** Our voice adapts to different audiences, channels, and platforms. When we talk about technology, we consider the audience and don't cloud the message with terminology, acronyms, or phrases they're unlikely to understand. We're not dumbing down or patronising — we're meeting the audience where they are.
+
+**Genuine, and a team of equals.** Our voice instils trust in our work and our people. We speak positively about our customers — past and present — emphasising collaboration, transparency, and honesty. We voice our opinions but stay open to compromise for the good of the client or team. We're considerate and intentional with our words, paying close attention to inclusivity and accessibility.
+
+---
+
+## Adapting Tone for the Audience
+
+The Equal Experts voice flexes to the audience and content type. Internal audiences allow a more informal, conversational tone with more room for humour; sales materials dial up confident, persuasive language.
+
+| Audience / channel | Tone |
+|--------------------|------|
+| Case studies (external) | Straightforward and factual, with a focus on storytelling, client collaboration, and results |
+| Blogs (external & internal) | Purposeful and informative, letting the author's personality shine through; answer the audience's questions |
+| Playbooks & informative content | Clear and informative, with evidence-based insights and examples; a strong expert tone |
+| Pitch decks & sales materials | Confident, authoritative, persuasive; definitive statements about our work and impact, always backed by results |
+| Social media | Conversational, friendly, and informal; often addressed to the audience |
+| Internal Blogin & Slack | Friendly, approachable, reflecting the author's personality. Remember NDAs |
+| Knowledge Portal | Deeper, less-polished opinions and insights, useful for the network but not for external view. Remember NDAs |
+
+We don't adapt the tone in a way that compromises our values, and we always read as professional, reliable experts who deliver results.
+
+---
+
+## Content Principles
+
+These principles underpin all our content, from planning to maintenance.
+
+1. **Always be human.** We're humans talking to humans — simple, authentic, and genuine, with personality and humour where it suits.
+2. **Have a clear purpose.** Set the aim, audience, and the goal it serves before you start. What question does this piece answer?
+3. **Know who your audience is.** Understand their situation, behaviours, attitudes, problems, and goals.
+4. **Be clear and concise.** Plain English, the best chance of being read and understood. Don't use ten words when three will do.
+5. **Collaborate with others.** Draw on people with the right skills at the right point in the process.
+6. **Test, iterate, and learn.** Try new content, improve it on feedback and evidence, and share what you learn across the network.
+
+---
+
+## Top Tips
+
+- **Write for all readers.** Some read every word; others skim. Descriptive headers, subheaders, lists, and diagrams help people find what they need
+- **Lead with the key message.** Open with the main or most interesting point, then back it up
+- **Use the active voice.** "We reviewed the code", not "The code was reviewed by Equal Experts"
+- **Be clear, concise, and specific.** Plain English, no slang, no unnecessary jargon or acronyms; don't assume prior knowledge
+- **Write like a human.** Being an expert means removing complexity — be relatable, warm, and friendly
+- **Adapt to the audience.** Suit the situation, the reader, and the subject
+- **Don't "we" all over the content.** Too much "we" reads as boastful; emphasise the client and the collaboration
+- **Be consistent.** Apply the same standards and style throughout; don't mix tones
+
+---
+
+## UK English and Local Markets
+
+We focus on **UK English** for global content, but respect local markets — Australia, the US, Europe, South Africa, and India — where appropriate, adopting local spelling, grammar, and currency in location-specific content.
+
+---
+
+## Audience Considerations
+
+### Technical audiences (developers, engineers)
+
+**Tone:** Pragmatic, evidence-based, respectful of expertise. Use specific technical detail, code examples, and trade-offs. Avoid over-simplification, buzzwords, and marketing language.
+
+### Business stakeholders (product owners, leaders)
+
+**Tone:** Outcome-focused, clear, strategic. Use business metrics, efficiency gains, and impact. Avoid deep technical detail without context and unexplained acronyms.
+
+### General audiences
+
+**Tone:** Helpful, clear, accessible. Use plain language, clear explanations, and practical examples. Avoid corporate speak and jargon.
+
+---
+
+## Common Pitfalls
+
+### Buzzword bingo
+Trendy terminology without substance.
+
+❌ "Leveraging synergistic, AI-enabled solutions"  
+✅ "We automated invoice processing using existing APIs"
+
+### Unbacked claims
+Bold statements without evidence.
+
+❌ "We'll dramatically improve your performance"  
+✅ "The health check saved the client £3 million"
+
+### Over-explanation
+Explaining what needs no explanation.
+
+❌ "Click the button below to continue to the next screen"  
+✅ [Continue]
+
+---
+
+## Content Quality Checklist
+
+- **Clarity:** Can it be understood from a 30-second skim?
+- **Purpose:** Does it answer a specific question or solve a problem?
+- **Consistency:** Does it use consistent terminology and patterns?
+- **Audience:** Is it pitched right for the intended reader?
+- **Accessibility:** Does it work for everyone, including assistive-technology users?
+
+---
+
+## Platform-Specific Content
+
+For platform-specific content guidance:
+
+- **Web Marketing** - See [media-types/web-marketing/](../media-types/web-marketing/)
+- **Web Product** - See [media-types/web-product/](../media-types/web-product/)
+- **Slides** - See [media-types/slides/](../media-types/slides/)
+
+---
+
+## Related Documentation
+
+- [Brand Guidelines](./brand.md) - Brand voice and values
+- [Writing style](../content/writing-style.md) - Active voice, plain language, conventions
+- [Inclusive language](../accessibility/accessibility.md#inclusive-language) - Accessible, bias-free word choices
+- [Design language](../design-language/design-language.md) - Visual design principles

package/agent-docs/external/kuat-agent-rules/reference/content/README.md

@@ -0,0 +1,12 @@
+# Content
+
+How Equal Experts writes — style and usage conventions that apply across every medium. (Voice and tone lives in [brand/](../brand/voice-and-tone.md).)
+
+| File | Scope |
+|------|-------|
+| [writing-style.md](./writing-style.md) | Active voice, plain language, conciseness |
+| [formatting.md](./formatting.md) | Capitalisation, headings, links, lists, acronyms |
+| [numbers.md](./numbers.md) | Dates, times, currency, percentages, units |
+| [punctuation.md](./punctuation.md) | Commas, dashes, apostrophes, quotation marks |
+
+Inclusive, bias-free word choices live in [accessibility/](../accessibility/accessibility.md#inclusive-language) and are cross-linked from [writing-style.md](./writing-style.md).

package/agent-docs/external/kuat-agent-rules/reference/content/formatting.md

@@ -0,0 +1,120 @@
+# Formatting
+
+How to use bold, capitalisation, headings, links, lists, and abbreviations in Equal Experts content.
+
+---
+
+## Quick Reference
+
+- **Capitalisation:** Sentence case for headings, buttons, and body copy; capitals only for proper nouns and product names
+- **Bold:** Use sparingly, only to draw attention to a key point
+- **Italics:** Use only to denote a quote
+- **Underline:** Use only to indicate a link
+- **Links:** Descriptive link text, not "click here" or raw URLs
+- **Lists:** Use sparingly; punctuate by whether items are full sentences
+- **Acronyms:** Spell out on first use, then use the short form
+
+---
+
+## Capitalisation
+
+### Sentence case
+
+Use sentence case for:
+- Headings, subheadings, and content titles (no full stop)
+- Button and link labels
+- List items
+- Body copy
+
+**Examples:**  
+"Helping ease the path to AI adoption in the enterprise"  
+"Save and continue"  
+"Contact the team"
+
+### Capitals in body copy
+
+Within the body of the content, use a capital letter only for a **proper noun** (for example a customer or product name). Don't use title case for general headings or UI labels.
+
+---
+
+## Bold, Italics, and Underline
+
+- **Bold:** Use sparingly, only when you want to draw attention to a key point: "Building a culture of innovation? You need **Experts** by your side."
+- *Italics:* Use **only to denote a quote**. Don't use italics for emphasis, titles of works, or technical terms.
+- <u>Underline:</u> Use **only to indicate the presence of a link**. Don't underline for emphasis.
+
+---
+
+## Headings
+
+- Use headings and subheadings to break up text and help readers scan or jump to what they need
+- Write them in **sentence case with no full stop**, and keep them concise and informative: "Why autonomous agents could be the best thing to happen to AI"
+- One H1 per page or screen; use a logical hierarchy (H1 → H2 → H3) and don't skip levels
+
+---
+
+## Links
+
+- Provide a link whenever you refer to something on another website or page
+- Link text should tell people where they're going and why they'd want to visit — link the relevant keywords, written as a normal sentence
+- Don't use words that wouldn't make sense without the link, and avoid "click here" or "read this" — they're bad for accessibility
+
+| Prefer | Avoid |
+|--------|--------|
+| Find out more on our Design service page | Click here for more |
+| Read the accessibility guidelines | Read this |
+| Contact the team | https://example.com/contact |
+
+---
+
+## Lists
+
+Use bullet points for items in no particular order; use a numbered list when the order matters. Use lists sparingly — too many in one piece dilutes their impact. Introduce a list with text followed by a colon.
+
+**Items that are not full sentences:** start each with a lower-case letter, follow each with a comma, end the penultimate item with "and", and end the last item with a full stop:
+
+> Equal Experts can help your business in many ways. We can:
+> - solve complex business problems,
+> - upskill your staff and
+> - scale your business for the future.
+
+**Items that are full sentences:** punctuate them like sentences, with a capital letter and a full stop:
+
+> Inceptions are based on principles and paradigms that we know make the difference:
+> - We validate that our solution is desirable, viable and feasible.
+> - We deliver the most valuable outcomes when we focus on the problem and the outcome.
+
+---
+
+## Buttons
+
+- Button text should describe the resulting **action** and be clear and concise
+- **Capitalise only the first word** ("Save and continue", "Contact us")
+- For product UI button patterns, see [web-product actions](../media-types/web-product/content/actions.md)
+
+---
+
+## Abbreviations and Acronyms
+
+- Spell out on first use with the short form in parentheses: "The Planning and Resource Allocation Committee (PRAC) decided to continue." Then use the short form: "We meet with the PRAC every two weeks."
+- This **isn't required for well-known acronyms** (for example NHS, BBC)
+- **Latin abbreviations** (e.g., etc., i.e.) may be used, but must be used correctly, in the right context, and with full stops
+
+---
+
+## Emojis and Hashtags
+
+Use emojis and hashtags thoughtfully, mainly in social media posts.
+
+- Don't add too many emojis; they should complement the text, not replace it. Check the post still makes sense if the emoji is removed
+- Make sure an emoji is appropriate and doesn't carry an alternative meaning online
+- Use **camel case** for hashtags so they're readable for assistive technology: #BlackLivesMatter, not #blacklivesmatter
+- Use 3–5 hashtags on LinkedIn and 1–2 on X; look for relevant event, industry, or topic tags
+
+---
+
+## Related Documentation
+
+- [Voice and tone](../brand/voice-and-tone.md)
+- [Writing style](./writing-style.md)
+- [Numbers](./numbers.md) - Dates, currency, units

package/agent-docs/external/kuat-agent-rules/reference/content/numbers.md

@@ -0,0 +1,87 @@
+# Numbers
+
+Guidance for numbers, dates, times, and currency in Equal Experts content.
+
+---
+
+## Quick Reference
+
+- **Words vs figures:** Spell out one to ten; use figures for 11 and above
+- **Always figures:** Percentages, measurements, and currency always use figures and symbols (10%, 1.61m, £4m)
+- **Dates:** Day before month, no "th"/"st", never "the" (13 April, not the 13th of April)
+- **Times:** 12-hour uses a full stop (11.30am); 24-hour uses a colon (13:00). Don't mix the two
+- **Currency:** Default to a generic £ for global content; use local currency for single-country content
+- **Large numbers:** Use commas for thousands (3,000); abbreviate very large round numbers (1k, 2m)
+
+---
+
+## Words or Figures
+
+- Spell out whole numbers from **one to ten**: "We worked with the client for two months."
+- Use **figures for 11 and above**: "Our work involved 35 teams across the organisation."
+- If a number is the **first word of a sentence**, spell it out: "Eleven people worked in the team."
+- If a paragraph has **multiple figures**, use figures throughout so readers can compare easily: "There were 2 people in the team when we started, and 22 when we finished."
+
+**Exception:** percentages, measurements, and currency always use figures and symbols, even below 11 (see below).
+
+---
+
+## Ordinals
+
+- Spell out **first to tenth**: "She was the first person to see the problem."
+- Use figures with **st, nd, rd, th** for larger ordinals: "The 19th president of the United States was Rutherford B Hayes."
+
+---
+
+## Percentages, Measurements, and Currency
+
+Always use figures and symbols, regardless of the one-to-ten rule.
+
+- **Percentages:** Use the % symbol with the figure (10%, 12.5%). For a range, "40–60%" (en dash, no space)
+- **Measurements:** "The average height of a woman in the UK is 1.61m." Leave a space when spelling out units in prose where it reads naturally
+- **Currency:** See [Money and currency](#money-and-currency) below
+
+---
+
+## Large Numbers
+
+- Use commas as thousand separators: "We reviewed 3,000 lines of code."
+- For very large round numbers, combine a figure with a word or letter, or abbreviate to 1k or 2m: "The population of the earth is now more than 7 billion people." / "The budget came in at just under £2m."
+- Keep formatting consistent across tables and lists.
+
+---
+
+## Money and Currency
+
+- The default currency is a **generic £** sign on anything that may be referenced globally
+- If content is intended for a **single country**, adopt the local currency: "Our US-based client has seen efficiencies in the region of $1.3m."
+- Abbreviate large round amounts: "The cost savings for our client were £4m."
+
+---
+
+## Dates
+
+- Always put the **date before the month** — even in US-focused content, for clarity: "Easter this year is on 13 April." / "Armistice Day is on 11 November."
+- Don't use "th", "st", "nd", or "rd" with dates, and never precede the number with "the"
+- **Shorten periods** of time where it isn't ambiguous: "The First World War (1914–18)."
+- For a **financial year**, use the format "2020–21": "The company did better in 2020–21 than in 2019–20."
+- Use the **day of the week with a date** only for emphasis or to avoid confusion: "The Agile on the Beach conference starts on Friday 13 April."
+- In code, data, and other technical fields where an unambiguous machine format is needed, ISO 8601 (YYYY-MM-DD) is acceptable; it is the exception, not the prose style.
+
+---
+
+## Time
+
+- Use either the 12-hour or 24-hour clock — **not both** in the same text
+- **12-hour clock:** Use a full stop between hours and minutes, with am/pm: "The meeting starts at 11.30am and ends at 1pm."
+- **24-hour clock:** Use a colon and omit am/pm: "The meeting starts at 11:30 and ends at 13:00."
+- Use **"noon"** or **"midnight"** instead of "12", "12 noon", or "12 midnight"
+- When you use "from" with a start time or date, pair it with "to" for the end — not a dash: "The third financial quarter runs from October to December."
+- Specify a time zone when the reader needs to act or compare across regions ("2.30pm GMT")
+
+---
+
+## Related Documentation
+
+- [Formatting](./formatting.md) - Capitalisation, lists
+- [Punctuation](./punctuation.md) - En dash for ranges, "from … to"