Sector content packs

What a sector pack is

The platform's seven sector presets (the same seven covered in the design strategy's component section) carry two parallel dimensions:

1. Visual identity — palette, density, motion, type. Wired through the platform's sector overlay tokens and theme resolver.
2. Content + policy — tone register, default Acknowledgement of Country wording, sector-tuned distress / bias thresholds, recommended consent layer set, audit / reporting posture, sector-specific UI copy, references library. This dimension is the sector content pack.

A sector content pack is the platform-managed bundle of content + policy defaults for one sector. The platform's pack registry maps each sector ID to its pack module, and the resolver reads the organisation's chosen sector and returns the active pack.

Pack content is platform-managed. Organisations choose a sector preset from the Govern → Sector surface; the pack carries the defaults. Pack values evolve through platform updates reviewed by sector practitioners.

Sector IDs and current pack status

Sector ID	Pack status	Review requirement
default	Real	Platform-wide voice doctrine review
government-au	Real	APS deployment partner review
government-international	Real	Per-jurisdiction public-administration expert sign-off
corporate-formal	Real	Corporate HR leadership expert sign-off
community-warm	Real	Community-sector / trauma-informed practitioner review
education-bright	Real	Safeguarding lead + education academic sign-off
healthcare-trust	Real	Clinical lead (nursing or medical) sign-off
finance-considered	Real	Financial-services regulated-conduct expert sign-off

Current state: 7 of 7 real packs. The final wave (May 2026) promoted corporate-formal and finance-considered from placeholder to real content. Prior waves shipped government-au and community-warm (first), then government-international, healthcare-trust, and education-bright (second). The seven-sector matrix is now complete.

Co-design status (all real packs): each pack names the references it was authored against and the named sector practitioners who must sign off before any participant-facing deployment. All seven packs require named sector-practitioner sign-off before launch with a specific deployment — the pack is the platform-managed default; the practitioner review is the deployment gate. The named practitioner role for each pack is published with the pack (e.g., corporate-HR-leadership-expert for corporate-formal, financial-services-regulated-conduct-expert for finance-considered).

With all seven packs now promoted to real content, there are no remaining placeholder packs in the registry — the operational defaults in the default pack continue to apply only when an organisation has no sector configured. The distress-detection and bias-monitoring tunings each carry their research basis in the platform's research library.

Surfaces a pack shapes

When an organisation is on a sector preset, the active pack reaches into the following surfaces:

• Distress detection — the pack's distress block projects onto the detector's threshold shape, sector by sector.
• Bias monitoring — the pack carries sector-aware bias thresholds (e.g. tightened bands for finance and healthcare, balanced for corporate, broader for community).
• Acknowledgement of Country — the pack provides a sector-default AoC block that the welcome surface uses when the organisation has not configured its own. Organisation-level configuration always takes precedence.
• Welcome page — sector-tuned welcome header and consent prefix.
• Completion page — sector-tuned completion message.
• Govern → Sector admin — a read-only "Sector content pack" panel that shows the active pack's identity, how it differs from the default, and offers a JSON export for diligence.

Authoring a new pack

Adding a new sector is a controlled change that touches the platform's sector type registry, the theme resolver, the branding overlays, and a new pack module. Each new pack ships with a header note naming the review status (real / placeholder) and the open items. The type system will not compile until every sector ID has a pack entry; the build is the safety net.

In practice, a new sector arrives via a partnership: a sector practitioner co-designs the pack with the platform team, the pack ships behind a feature flag, and the deployment gate is the named sector-practitioner sign-off.

Co-design protocol per pack

Sector practitioner co-design is a launch gate, not a nice-to-have. Specific sector packs additionally require:

• Indigenous-led overlay (community-warm + Indigenous-led, or any government pack overlaid with Indigenous-led configuration): Indigenous cultural advisor sign-off on the Acknowledgement of Country wording, lexical pattern lists, and crisis-services referral order (13YARN surfaces first). Quarterly methodology review with an Indigenous co-design panel.
• Healthcare: Clinical lead (nursing or medical) sign-off on the clinical narration whitelist scope, clinical crisis-services routing (Doctors4Doctors, Nurse & Midwife Support, EAP surfaced first), mandatory-notification handler (Health Practitioner Regulation National Law), and clinical-precision copy register. AMSes and other Indigenous-led services additionally require cultural-advisor sign-off on the AoC wording.
• Education: Safeguarding lead (with working-with-children clearance) sign-off on the mandatory-reporting pathway and the participant-side mandatory-reporting acknowledgement disclosure. Working-with-children verification for any assessor reviewer. Age-cohort language tuning reviewed by an education academic with the relevant age-cohort experience. Student self-assessment deployments additionally require parent / guardian consent flow review.
• Government (APS): APS deployment partner review of APP / Privacy Act framing copy. IRAP-equivalent posture asserted only after the deployment-level control set has been validated against an actual IRAP assessment.
• Government (International): Per-jurisdiction public-administration expert review of the jurisdiction-appropriate Acknowledgement / Land-Acknowledgement / Whakatauki form, the crisis-services locale and surfacing order, the data-residency choice (EU / AU / US), the local IRAP-equivalent posture (UK GovAssure / Canada PBMM / NZ NZISM / EU ENISA-aligned), and the local privacy-regime framing (UK GDPR / EU GDPR / PIPEDA / etc.).
• Finance / Regulated: APRA / ASIC alignment review.

Pack file header comments name the required review for that specific pack. Do not relax these gates without consulting the trust + safety owner.

How an organisation switches packs

Organisations change their sector preset from the Govern → Sector surface. The change is resolved server-side on the next request, and the pack-consuming surfaces (welcome, completion, govern, distress detector) pick up the new defaults on the next page load.

Organisation-level configuration (for example, an explicit Acknowledgement-of-Country block) continues to take precedence over pack defaults — organisations that have already configured specific overrides will not see their configuration replaced when the pack changes.

Backward compatibility

Existing organisations with no sector configured fall back to the platform default pack. The default pack mirrors the platform's pre-pack behaviour: AoC disabled, thresholds at research defaults, audit-ready logging off, no IRAP posture, generic copy. No deployment sees a behaviour change without an explicit sector choice.