SHARD — Shared Rule Definitions for A.I.

Overview

SHARD — Shared Rule Definitions — is a framework for building high-quality software with the help of A.I.

As A.I. coding assistants become a daily part of how software gets built, the question every team faces is: how do we keep the work consistent, professional, and maintainable across many projects, many technologies, and many developers?

SHARD answers that question. It's a single source of truth for the rules, conventions, and design philosophy that govern how code is written — shared by every project that imports it.

The Problem It Solves

Without a shared standard, every project ends up reinventing the same conventions: how to format SQL, how to structure data access, what kinds of mistakes the A.I. should avoid, when to commit, how to back up. The result is inconsistency, duplicated rule-writing, and rules drifting out of sync as different projects evolve.

SHARD fixes this by separating universal rules from project-specific knowledge. Update a rule once in SHARD — every project that depends on it picks up the change automatically.

How It's Structured

SHARD is organised by technology and concern. Each area lives in its own file so it can be reasoned about independently:

• A.I. behaviour — how the A.I. should think, when to ask, how to plan before coding
• Database conventions — SQL formatting, naming, schema patterns
• Application code — data-access patterns, language-specific idioms
• Shell and scripting — common traps, regex gotchas, bulk-edit safety
• Backup discipline — when to back up, naming conventions, recovery practices
• Source control — commit hygiene, branching, what not to do

Each project then has its own configuration file that imports the relevant SHARD rules and adds only what's unique to that project — the domain knowledge, the schema, the business rules.

Designed to Grow

The architecture is deliberately extensible. New technologies, new disciplines, new best practices can be added as their own modules without disturbing what's already in place. As the way we build software with A.I. continues to evolve, SHARD evolves with it.

Why It Matters

Building with A.I. is a force multiplier — but only if the A.I. is given a consistent, well-defined set of rules to work within. SHARD is the discipline layer that keeps A.I.-assisted development from becoming a different kind of chaos. It's how we ensure that the code we ship today still makes sense to the team that maintains it tomorrow.

Status

SHARD is actively used across our project portfolio and is continuously refined as we learn from each new build. We are exploring how to share the framework more widely with the development community.