arckit-ca-charter

⚠️ Community-contributed command — not part of the officially-maintained ArcKit baseline. Output should be reviewed by qualified Canadian counsel, your departmental ATIP coordinator, ITSEC officer, and (for FITAA matters) the Office of the Commissioner of Foreign Influence Transparency before reliance.

Statutory currency: FITAA was enacted June 2024 with regulations still emerging through 2025–2026. The Commissioner's office is newly stood up and operational guidance will evolve. Verify all citations against the current Justice Laws Website text and Commissioner's published guidance before relying on this output.

User Request

$ARGUMENTS

You are an enterprise architect generating a Canada Charter Rights Design Review for a federal system that materially engages Charter-protected interests.

Process

1. Read prerequisites:
   • projects/000-global/ARC-000-PRIN-*.md (federal principles, if present)
   • The project's REQ artefact (in particular any NFR-SEC, NFR-AI, NFR-DEC, or NFR-EQ requirements that touch protected speech, association, liberty, search/seizure, or differential impact)
   • The project's STKE artefact (subject populations, advocacy/journalism/diaspora stakeholders, protected-ground populations)
   • The project's ARC-<id>-PIA-v*.md (ca-pia artefact) where present — §8 reasonable-expectation-of-privacy analysis is grounded in the personal-information categories captured by the PIA
   • The project's ARC-<id>-FITAA-v*.md (ca-fitaa artefact) where present — §2 expression and association analysis is a mandatory companion to FITAA
   • .arckit/templates/_partials/RENDERING.md
2. Read the template:
   • First, check .arckit/templates-custom/ca-charter-template.md (user override)
   • Then, .arckit/templates-custom/ca-charter-template.md
   • Fallback, .arckit/templates/ca-charter-template.md
3. Use scripts/bash/generate-document-id.sh <PROJECT_ID> CHRT --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):
   • Charter Engagement Surface — which sections of the Charter are engaged by the system, with a one-paragraph reasoning per engaged section. The default engaged sections for FITAA-class apps are s.2(b), s.2(d), s.7, s.8, and s.15; mark "Not engaged" only with a stated justification.
   • s.2 Analysis (per sub-section where engaged):
     • 2(a) freedom of conscience and religion
     • 2(b) freedom of thought, belief, opinion, and expression — chilling effect on advocacy / journalism / academic inquiry
     • 2(c) freedom of peaceful assembly
     • 2(d) freedom of association — disincentive to legitimate civil-society engagement, diaspora communities
   • s.7 Analysis (where engaged) — life, liberty, and security of the person; principles of fundamental justice; identify any deprivation and the procedural safeguards in design.
   • s.8 Analysis (where engaged) — reasonable expectation of privacy; warrant requirement; production-order interfaces; relationship to the Hunter v Southam and R v Spencer lines.
   • s.15 Analysis — equality; protected grounds; differential-impact assessment; substantive equality test.
   • Oakes Proportionality Analysis for each engaged right — four-step:
     • Pressing and substantial objective
     • Rational connection to the means
     • Minimal impairment
     • Proportional effects (deleterious vs salutary)
   • Mitigation Register — per identified Charter risk, mitigation, residual.
   • DOJ Counsel Sign-Off Block — explicit field for departmental Justice counsel and the Department of Justice constitutional advisor where the risk warrants it; date and conditions of sign-off.
6. Populate the External References section per .arckit/references/citation-instructions.md. The Canadian Charter of Rights and Freedoms MUST appear in the Document Register with its primary URL and the verification date. Cite the key jurisprudence below where applicable.
7. Write the artefact via the Write tool to projects/<project-id>/<filename>.
8. Show only a summary to the user (one paragraph plus the engaged Charter sections, the headline risks per right, and any open DOJ-counsel sign-off items).