arckit-ca-ola

name	arckit-ca-ola
title	User Request
description	[COMMUNITY] Generate an Official Languages Act review — Parts IV (services), V (language of work), VI (federal language obligations); service-equivalence matrix EN/FR; bilingual public-facing surface; active offer; Translation Bureau pipeline; OQLF acknowledgement where federal-Quebec overlap applies.
author	tractorjuice
author_url	https://github.com/tractorjuice/arc-kit/tree/main/arckit-codex/skills/arckit-ca-ola
license	MIT
version	0.1.0
execution_mode	open
jurisdiction	ca
practice	regulatory
language	en

⚠️ Community-contributed command — not part of the officially-maintained ArcKit baseline. Output should be reviewed by qualified Canadian counsel and the relevant departmental authority (ATIP coordinator, ITSEC officer, OCHRO language lead, CIO branch) before reliance. Citations may lag current text — verify against the Justice Laws Website and the issuing TBS / CSE / OPC source.

User Request

$ARGUMENTS

You are an enterprise architect generating an Official Languages Act review for a federal digital service.

Process

1. Read prerequisites:
   • projects/000-global/ARC-000-PRIN-*.md (federal principles, if present)
   • The project's REQ artefact (if present)
   • The project's service-assessment artefact (if present)
   • The project's ca-fitaa artefact if present (any public register triggers Part IV bilingual obligations)
   • .arckit/templates/_partials/RENDERING.md
2. Read the template:
   • First, check .arckit/templates-custom/ca-ola-template.md (user override)
   • Then, .arckit/templates-custom/ca-ola-template.md
   • Fallback, .arckit/templates/ca-ola-template.md
3. Use scripts/bash/generate-document-id.sh <PROJECT_ID> OLA --filename for the artefact filename.
4. Resolve the <!-- DOC-CONTROL-HEADER --> marker per RENDERING.md. Use the Canadian classification scheme (UNCLASSIFIED / Protected A / Protected B / Protected C / CONFIDENTIAL / SECRET / TOP SECRET) — replace the standard UK line in the header.
5. Generate the following sections (the template provides skeletons for each):
   • Service Surface Inventory — every user-facing surface that must be language-equivalent: screens, forms, notifications, error messages, public registers, accessibility statements, printed correspondence, IVR scripts, and social media. Per surface: language posture (bilingual / unilingual + justification), audience, and channel.
   • Part IV — Communications with and Services to the Public — per surface, state the bilingual obligation rationale (significant demand, public-travel, head-office, designated bilingual office). Active offer at first contact (greeting, signage, written initiation). Bilingual capacity at time of service.
   • Part V — Language of Work — internal tooling EN/FR availability for designated bilingual regions; National Capital Region; New Brunswick; bilingual-designated parts of other regions. Tooling supervision and language of supervision.