A regulatory source set for one workflow
The frozen example is used to review selected claims in a Singapore financial assurance report.
Capability 02 / Regulatory Source Pack
Keep current, supporting, and proposed sources distinct
Auxtho records each approved public source's exact version and review role. If the recorded source set becomes stale, incomplete, unclear, or changes, it cannot support the report until another review is completed.
A document can remain visible for inspection without being allowed to support a current release claim.
The job in plain language
A financial report uses more than one kind of regulatory material
A current Notice, a supporting FAQ, and a closed consultation may all be relevant to review, but they do not carry the same role.
Keeps each source's version and role clear
Auxtho records whether each source is current, supporting, or proposed, whether it may support the report, and which reviewed claims could be affected by a change.
Whether a new pack version becomes active
An accountable reviewer activates the exact version after a separately authorized preparation and review step.
Lifecycle status and each source role
The App shows ACTIVE or re-review state and the role of every exact source in the pack.
An exact pack identity and lifecycle history
The prior pack, decisions, source identities, transition events, and impact inventory remain available for reconstruction.
Actual product screens
Read the lifecycle and source roles without opening internal mechanics
The first panel shows the workspace lifecycle readback. The second shows the exact public source inventory and distinct eligibility roles.
Lifecycle path
Change the source set without carrying the old approval forward
01Bind exact sources
Issuer, URL, bytes, SHA-256, page count, status, role, and eligibility form the source identity.
02Record the active version
The workspace activates one exact version under separate preparation and review roles.
03Detect a recorded change
A deterministic diff lists changed fields and the claims and prior releases affected.
04Require re-review
Stale, incomplete, ambiguous, or update-pending state stops the pack from supporting release.
05Activate a new exact version
The new decision does not rewrite the old pack or the decisions that used it.
Source note
Within the frozen MAS pack dated 29 August 2026, the Notice is classified as the current-primary source, the FAQ as supporting-only, and the consultation as proposed-only. M120 public proof and M121 PACK_ENGINE_V1_GO in terminal tree 1cca2c79d92ffba686883dd0ef3a8c4eb08f7c1b record the source-set and lifecycle behavior. Current revalidation included the 115 M121-M125 focused backend tests, TypeScript, focused M121 lint, and the authenticated local App/API lifecycle browser path. Proof boundary: one local synthetic MAS pack and a bounded generic lifecycle fixture; no second jurisdiction, automatic regulation update, legal determination, hosted activation, or production lifecycle is claimed.