# INJAZ | إنجاز — Brand Foundation

**Status:** Controlled working records and a V1 visual preview. The preview does not itself constitute approval.

## Product identity

- **Name:** INJAZ | إنجاز
- **Arabic tagline:** من التنظيم إلى الإنجاز.
- **English tagline:** From Organization to Achievement.
- **Description:** منصة إدارة وتنظيم المؤسسات

INJAZ is an independent software product. Ibrahim Abu Hassanien & Partners is a customer organisation using the platform; its identity and organisational data remain customer identity, not INJAZ corporate identity.

## Preview website

A static, dependency-light brand preview is available from the repository root:

- `index.html` — visual brand preview
- `brand-preview.css` — responsive styles and theme tokens
- `brand-preview.js` — light/dark theme and RTL/LTR preview controls
- `assets/logos/incoming/` — original supplied artwork, displayed without modification

The preview includes the identity foundation, supplied logo concepts, colour palette, typography specimens, interface examples, and usage/governance notes. It is a working V1 preview, not a production application or a claim of accessibility certification.

### Local preview

Open `index.html` in a modern browser. No build step or package installation is required.

### Cloudflare Pages (not yet connected)

For the authorised Pages publication, use Git integration with this private GitHub repository:
- **Production branch:** `main`
- **Framework preset:** None / static HTML
- **Build command:** leave blank (or use `exit 0`)
- **Build output directory:** `/` (repository root)
- **Root directory:** leave blank (Cloudflare defaults to the repository root)

The Cloudflare account owner must connect and authorise the private repository in the Cloudflare dashboard. Once connected, Cloudflare automatically deploys pushes to `main` and can create preview deployments for branches and pull requests. Git integration is deliberately preferred over Direct Upload; Cloudflare documents that the two project modes cannot be switched later.

The site references `./assets/logos/incoming/...`; therefore publishing only a `site/` subdirectory would break image paths. Keep the repository root as the output directory unless the site is deliberately restructured.

## Approval status

| Group | Status |
|---|---|
| A | Approved |
| B | Approved |
| C — visual identity and final artwork | Pending final artwork review and explicit PO approval |
| D1 | Confirmed (exact ownership-boundary statement recorded in product identity) |
| D2–D12 | Approved |
| E–J | Approved |

The preview uses a working V1 implementation baseline for layout and demonstration. It does not convert proposed colours, typefaces, or logo concepts into final permanent approvals. Selected contrast pairs and static structure checks pass; full browser, zoom, keyboard, and screen-reader verification remain outstanding.

## Documentation

The controlled records remain the source of truth. The website is their visual companion, not a replacement. See [Product Identity](docs/PRODUCT-IDENTITY.md), [Brand Guide](docs/BRAND-GUIDE.md), [Design Tokens](docs/DESIGN-TOKENS.md), [Logo Assets](docs/LOGO-ASSETS.md), [Accessibility Review](docs/ACCESSIBILITY.md), and [Decision Log](docs/DECISION-LOG.md).

## Governance

- Never merge to `main`, connect Cloudflare Pages, change deployment settings, or publish publicly without explicit PO authorisation.
- Do not modify the original logo files.
- No new package, icon, or external font dependency is introduced by this preview.
- Customer identity must never be conflated with INJAZ identity.