Regulatory admin (ops)

UI: locus-ops → /regulatory.

Bank workspace never writes the platform legal vault. Analysts only resolve / open statutes and see findings overlaid from SoR.

Tabs / surfaces

Surface	Actions
Source Registry	Watchtower sources (URLs, fingerprints) from config + SoR
Legal Vault	Upload official PDF → artifact on edition
Review	HASH_CHANGE / new edition / extractor issues → Approve & publish (VaultPublisher) or reject
Applicability	Map provisions → instruments / deal types (LegalProvisionApplicability)
Logs	Operator audit of vault actions

Attach & publish (happy path)

1. Create or select edition / instrument context.
2. Upload PDF (R2 when configured; else LEGAL_VAULT_LOCAL_DIR).
3. POST /api/admin/regulatory/editions/{id}/artifact (via ops BFF/client).
4. Open Review → human APPROVE.
5. VaultPublisher marks legal_reviewed / in_force as designed.
6. Bank: analyzeDealWithVault / resolve / open-statute can use vault IDs + hash-verified bytes.

Discovery vs validity

Watchtower / fetcher may enqueue candidates automatically when the scheduler is on (LEGAL_VAULT_WATCHTOWER_INTERVAL_MINUTES > 0). Scraped ≠ in force until APPROVE.

Fixtures

CI uses synthetic PDFs under data/regulatory/ — fixtures guide. Production corpus = official gazettes uploaded here.

Related

• Legal vault & Watchtower
• Regulatory engine
• locus-ops env