Pectrium is the approved public-facing master technology brand founded by Evans Jep. EJEP Systems retains its underlying legal/corporate role, with legal wording subject to verified records. Jeclazon is retired and must not be presented as the active company or master brand.
Brand statement: Intelligent Systems. Global Possibilities.
- Pectrium Master Brand Directive — current brand authority
- Phase 02 audit and controlled migration plan — inventory, risk, verification and release gates
The previous Jeclazon authority documents in docs/ are preserved as historical, superseded records. They are not current identity authority. Their engineering, accessibility and truthfulness principles may be reused where consistent with the Pectrium directive.
This repository includes a pnpm workspace and an existing Next.js corporate web application. The reviewed web source, workspace package names, root scripts, and shared design tokens have been staged under Pectrium on this feature branch. Historical Jeclazon documentation remains unchanged. Complete recursive inventory, build verification, and deployment review remain outstanding.
The proposed wider architecture (shared UI, configuration, project starters, restricted admin, optional APIs and infrastructure) must be verified against actual source before being described as implemented.
Quincestone, Emperor Armani, and Clesla retain their identities. No legal ownership or operational status is asserted merely by listing them in planning documents. Additional projects should not be publicly presented as EJEP/Pectrium builds before their work begins and relationships are verified.
- Preserve project independence, secrets isolation, least privilege, verified release provenance and separate preview/production boundaries.
- Publish only substantiated capabilities and accurate lifecycle status.
- Do not introduce customer accounts, sign-in, checkout, or billing into the corporate website.
- No production deployment, domain migration, repository rename, legal identity change, or merge without explicit approval.
- Follow: AUDIT → BASELINE → PLAN → IMPLEMENT → VERIFY → REVIEW → APPROVE.
Phase 02 source migration is staged on a feature branch, not merged or publicly deployed. Runtime build/lint/typecheck verification remains pending. See the migration plan for confirmed references, audit limitations and remaining work.