Ezzi Clarity
The institutional repository of Ezzi Clarity Educational Consulting Services Inc. — educational consulting and publishing, founded by Arva Ezzi in Waterloo Region, Ontario. Public website: ezziclarity.ca.
This repository is the corporation’s single source of truth: its governance and constitution, its corporate and legal records, its commercial strategy and content IP, and the operating know-how behind running it. It exists so that the business can be understood, run, and handed off without depending on any one person’s memory. If you’re new here, this page is your map.
Start Here
| If you are… | Start with |
|---|---|
| 🏛️ A director, officer, or advisor wanting the governance picture | governance/constitution.md |
| 💼 Someone who wants to understand the business itself | company/strategy/business-plan.md |
| 📊 Checking where things currently stand, administratively | company/strategy/current-status.md |
| 📁 Looking for a specific legal or corporate record | registers/corporate-records-register.md |
| 🤖 An AI assistant working in this repository | CLAUDE.md |
How the Repository Is Organized
The repository is organized by governance function and business arm, not by document type — each domain answers a different kind of question:
flowchart TD
G["⚖️ governance/<br/>constitution, standards, decisions"] --> R["📋 registers/<br/>what exists, what's pending"]
R --> L["🏢 company/legal/<br/>corporate & immigration records"]
R --> S["💼 company/strategy/ + consulting/ + publishing/<br/>the business itself"]
S --> K["🧠 knowledge/<br/>institutional understanding"]
S -.superseded.-> A["🗄️ archive/<br/>frozen history"]
L -.superseded.-> A
| Domain | Answers | Contents |
|---|---|---|
⚖️ governance/ |
What gives this repository its authority? | Constitution, Governance Principles, Manifesto, Repository Standards, Security Policy, Decision Log, Changelog, and the Enterprise Standards (governance/standards/) |
📋 registers/ |
What currently exists, and what’s still being decided? | Corporate Records Register (permanent record IDs mapped to files), Decision Pipeline, and digital/brand, website, and bookshelf asset registers |
🏢 company/legal/ |
Where’s the evidence? | corporate/ — incorporation, registration, share records. immigration/ — the C11 case docket, stored under a governed security exception |
💼 company/strategy/ |
What is the business, and where is it going? | Business plan, roadmap, growth plan, org structure, current status |
🎨 company/brand/ |
How does the business present itself? | Shared positioning and voice, and the founder’s full biography |
🎓 consulting/ |
What does the consulting arm sell, and how? | Cohort economic model, curriculum, outreach playbook, network activation tracker |
📚 publishing/ |
What does the publishing arm sell, and how? | Strategy, distribution, and a pointer to ezzi-bookshelf — the active production repo where 3 books are already published |
🧠 knowledge/ |
What has been learned that isn’t a business arm or a corporate record? | Architecture decisions and technical reviews — currently, the public website’s |
🗄️ archive/ |
What used to be current? | Superseded documents, kept for their original point-in-time reasoning |
docs/superpowers/ holds the design specs and implementation plans produced while building this
repository’s structure with Claude Code — a record of how the repository came to be organized
this way, kept separate from the business’s own knowledge base above.
Recent Activity
One row per Issue — full detail in governance/changelog.md.
| Date | Issue | What changed |
|---|---|---|
| 2026-08-24 | #16 | Finalized the DP-0001 account-opening document checklist — corporate documents already on file, personal KYC documents confirmed available |
| 2026-08-24 | #14 | Corrected the portal notification to trigger a GitHub Actions build instead of a Cloudflare deploy hook, after finding Cloudflare’s git integration can’t clone a private submodule |
| 2026-08-24 | #12 | Added a workflow that notifies the private portal to rebuild on every push to main |
| 2026-08-24 | #10 | Broke every sentence pointing to 2+ documents into a bulleted list, across 11 files |
| 2026-08-24 | #8 | Added company/brand/about-the-founder.md, curated from the founder’s résumé and records, and corrected a real error in her documented language fluency along the way |
| 2026-08-24 | #6 | Added registers/bookshelf-asset-register.md (REG-3003) — a governed listing of ezzi-bookshelf and its 7 titles, matching the website’s register pattern |
| 2026-08-23 | #5 | Decluttered every document’s presentation (no inline git-provenance narration, proper vertical tables of contents) and corrected publishing/ — the book pipeline is active, not aspirational, with 3 titles already published |
| 2026-08-23 | #3 | Established ESS-002, the documentation formatting standard, and applied it repository-wide |
| 2026-08-23 | #1 | Adopted ezzi-clarity-os’s governance framework — Constitution, standards, records register — making this repository the single primary one |
Working in This Repository
Every document longer than a page opens with a short summary and, where useful, a table of contents. Material changes follow an Issue → Branch → Pull Request → Changelog trail. The three documents behind these conventions:
governance/repository-standards.md— the practical rulebook; start here if you’re contributing for the first timegovernance/standards/ess-002-documentation-formatting.md— the full formatting standardgovernance/standards/ess-008-issue-and-change-audit.md— the Issue/branch/PR/changelog traceability standard