Ezzi Clarity Portal

Decision Log

This file records approved material decisions. Proposed options and unresolved discussions belong in company/strategy/current-status.md, company/strategy/growth-plan.md, registers/decision-pipeline.md, or working notes.

The first two entries below predate this repository and remain in force; all later entries were made here.

Contents

Decision Record Template

## YYYY-MM-DD — Decision title

**Status:** Approved | Superseded | Reversed
**Decision owner:** Name/role

### Decision

State exactly what was approved.

### Reason

Explain why this option was selected.

### Alternatives considered

- Alternative A
- Alternative B

### Implications

- Legal:
- Tax/accounting:
- Cost:
- Operations:
- Documents/systems affected:

### Follow-up

- Action, owner, due date

### Revisit trigger

State when or why the decision should be reviewed again.

2026-08-04 — Establish ECOS as the corporate knowledge repository

Status: Superseded (see 2026-08-23 — Adopt ezzi-clarity as the single primary repository) Decision owner: Vijay Panangipally and Arva Yusuf Ezzi

Decision

Use the private GitHub repository vijaybpanangi/ezzi-clarity-os as the central corporate documentation and knowledge-management repository for Ezzi Clarity Educational Consulting Services Inc.

Reason

Centralize documents and working knowledge; preserve version history and an audit trail; reduce dependence on any single outside consultant; support AI-assisted repository management; make future onboarding of CPAs, lawyers, and collaborators faster.

Follow-up

Superseded by the 2026-08-23 decision below — ezzi-clarity-os’s governance framework was adopted into ezzi-clarity, which became the single primary repository.

2026-08-04 — Defer corporate restructuring until the baseline is confirmed

Status: Approved — still in force Decision owner: Vijay Panangipally and Arva Yusuf Ezzi

Decision

Do not immediately rename, dissolve, continue into Ontario, change share ownership, or otherwise restructure the corporation. First complete the document inventory, compliance review, cost assessment, and professional tax/legal consultation needed for an informed decision.

Reason

The corporation has little or no operating activity, but its filing status, GST/HST obligations, registered-office arrangement, address accuracy, and future use have not yet been fully validated.

Follow-up

Confirm all filing deadlines and account statuses; obtain registered-office service details; engage an Ontario CPA for a scoped review. See company/strategy/current-status.md.

Revisit trigger

Revisit after the compliance baseline and annual carrying cost are confirmed, or before the corporation begins material operations.

2026-08-23 — Keep the C11 immigration case docket in this repository, permanently private

Status: Approved Decision owner: Arva Yusuf Ezzi

Decision

Store the full C11 VisaAffix case docket (passport scans, marriage certificate, bank statements, employment and education records) in company/legal/immigration/, departing from the default governance policy against storing personal identity documents, on the condition that every GitHub remote hosting this repository remains private permanently.

Reason

The founder made an informed choice after the tradeoff was explicitly flagged: the documents are already central to understanding the corporation’s origin, and keeping them in one governed place outweighs the residual risk, given the private-forever condition.

Alternatives considered

Implications

Revisit trigger

Any proposal to make a hosting remote public, add a broader set of collaborators, or transfer the repository must re-confirm this condition still holds.

2026-08-23 — Adopt the arm-based repository architecture

Status: Approved Decision owner: Arva Yusuf Ezzi

Decision

Restructure the repository into company/, consulting/, publishing/, and archive/, split by business arm rather than by document type, with living documents (not dated snapshots) for the core strategy publications.

Reason

The consulting and publishing arms are expected to grow and be tracked largely independently; the founder confirmed this split directly during the repository’s design.

Implications

2026-08-23 — Adopt ezzi-clarity as the single primary repository; retire ezzi-clarity-os

Status: Approved Decision owner: Arva Yusuf Ezzi and Vijay Panangipally

Decision

ezzi-clarity (this repository) becomes the single primary institutional repository for Ezzi Clarity Educational Consulting Services Inc. ezzi-clarity-os’s governance framework — Constitution, Governance Principles, Manifesto, Enterprise Standards, Corporate Records Register, Decision Pipeline, and asset registers — is adopted into this repository under governance/, registers/, and knowledge/, adapted to this repository’s arm-based structure rather than copied verbatim. ezzi-clarity-os itself will be retired (deleted) once this adoption is complete, as a separate, explicitly confirmed step.

Reason

Two parallel repositories had developed independently — ezzi-clarity-os with strong governance and compliance discipline, ezzi-clarity with the actual commercial strategy and content IP — without cross-awareness. Maintaining both indefinitely would fragment the single-source-of-truth principle both repositories otherwise share. The founder chose ezzi-clarity (and specifically the ezziarva-ux/ezzi-clarity-repo GitHub remote) as the canonical repository going forward.

Alternatives considered

Implications

Follow-up

Confirm ezzi-clarity-os deletion with the founder as a separate, explicit step once this adoption is verified complete.

Revisit trigger

None expected; this is intended to be a durable consolidation.

2026-08-23 — Correct organizational facts using ECOS’s more accurate records

Status: Approved Decision owner: Arva Yusuf Ezzi

Decision

Correct company/strategy/org-structure.md to record Srinivasa Vijay Bhushan Panangipally as Sales Manager per the signed organizational resolutions (CR-1005), and to record the registered and records office (Gordon J. Fretwell Law Corporation, Vancouver) — both of which were missing or incorrectly stated as “no other officers” in the document as originally drafted, based on the public Ontario registry profile rather than the internal organizational resolutions.

Reason

ezzi-clarity-os’s CorporateSnapshot.md (2026-08-04) was built from a more complete source — the actual signed organizational resolutions — while org-structure.md’s original draft relied only on the public Ontario Corporations Information Act profile, which does not list internal officer resolutions.

Implications

Revisit trigger

Any future change in director, officer, ownership, or management status must be supported by the appropriate corporate approvals, registers, filings, and source records, per registers/corporate-records-register.md.

2026-08-20 — Publish the picture-book imprint under Arva personally, pending corporate banking

Status: Approved — provisional Decision owner: Arva Yusuf Ezzi and Vijay Panangipally

Decision

The Ezzi Clarity picture-book imprint publishes through Amazon KDP under Arva Ezzi personally (copyright, W-8BEN tax reporting, and payments), not through Ezzi Clarity Educational Consulting Services Inc., for as long as the corporation has no bank account of its own.

Reason

The corporation’s business-banking arrangement is still under evaluation (registers/decision-pipeline.md DP-0001). Rather than wait on that to launch the already-ready first titles, publishing proceeds under Arva’s personal account now.

Implications

Revisit trigger

Once the corporation’s business banking (DP-0001) is resolved, decide explicitly whether to move the imprint’s publishing account to the corporation — this decision does not do that automatically.

2026-08-24 — Correct the founder’s documented language fluency

Status: Approved Decision owner: Arva Yusuf Ezzi

Decision

Correct company/brand/positioning.md and company/strategy/business-plan.md to state the founder’s fluent languages as English, Arabic, Hindi, Gujarati, Marathi, and Urdu, with French as a current work in progress rather than a working language of delivery.

Reason

Drafting company/brand/about-the-founder.md from the founder’s résumé surfaced a conflict: the résumé lists no French and includes Marathi and Urdu, neither previously documented. Confirmed directly with the founder rather than resolved by assumption, per the source-labeling convention in governance/repository-standards.md §6.

Implications

Revisit trigger

Update company/brand/positioning.md’s language-fix recommendation and the site itself once French reaches a working level, and whenever the founder’s language fluency otherwise changes.