Guide/Assure/Framework packs

Framework packs

A registry of jurisdiction standards, legal effect, activation gates, and the capabilities each pack needs.

/framework/packs
Who this is forHR and compliance staff overseeing which standards apply.
Org adminHR reviewerCompliance officerScreenshot shown as: David Chen
moosh.app/framework/packs
Framework packs screen

MOOSH treats a framework as data: approved content, requirements, and configuration — not a separate product per country. This page lists first go-to-market packs (Australia, Victoria as its own OHS regime, New Zealand, Brazil NR-1) with honest legal-effect and activation labels.

Each pack can declare reusable capabilities it needs — worker risk communication, event-driven review, statutory artifact export. If a required capability is missing, activation fails closed rather than claiming partial compliance.

Packs in the mock are reference-only concept fixtures pending counsel. Nothing here is treated as live legal compliance advice.

For example

Brazil NR-1 GRO/PGR shows as adopted_requirement, pending counsel, and lists all three reusable capabilities. The UK ISO 45003 stack remains the active operating stack for the demo organisation until a local pack is approved.

Worth knowing

Jurisdiction
The country or region whose specific rules apply — each one needs its own local approval before it's treated as active.
Legal effect
How strongly a pack binds practice — for example guidance, model source, or adopted requirement.
Required capability
A generic platform feature a pack must have enabled before it can be activated.

What you can do here

  1. 1See pack name, legal effect, and activation limitation.
  2. 2Read which reusable capabilities each pack declares.
  3. 3Open related review-trigger and coverage views from the assure loop.