Purpose: Implementation pack for the Adaptive Universal Resource Activation architecture: a single extensible model for SKRs (safekeeping receipts and strategic resource records), server funds, tokenized and non-tokenized assets, and Proxmox/infrastructure capacity.

Status: Documentation implementation (schema, lanes, evidence, pilots). On-chain and service wiring follow the links in each document.

Document map

Document	Role
UNIVERSAL_RESOURCE_ONTOLOGY.md	Canonical resource schema, families, lifecycle states, deployability states
UNIVERSAL_RESOURCE_POLICY_PROFILES.md	Legal, jurisdiction, compliance, accounting, valuation, transferability profiles
UNIVERSAL_RESOURCE_SKR_CUSTODY_LANE.md	SKR / custody lane: intake, evidence, encumbrance, deployability
UNIVERSAL_RESOURCE_SERVER_FUNDS_LANE.md	Server-funds lane: SoR, good-funds, holds, caps, reconciliation
UNIVERSAL_RESOURCE_INFRA_CAPACITY_LANE.md	Infrastructure capacity lane: inventory, bundles, broker, metering
UNIVERSAL_RESOURCE_EVIDENCE_PACKAGE.md	Shared evidence and reconciliation package
UNIVERSAL_RESOURCE_PILOT_PLAN.md	First three pilots (SKR, server funds, infra)
URA_PILOT_CLOSURE_RUNBOOK.md	Replace manifest placeholders; close pilots and evidence
URA_OPERATIONAL_READINESS_CHECKLIST.md	Phased checklist from preconditions to production acceptance; run `pnpm ura:ops-readiness` (fast) or `pnpm ura:ops-readiness:full` (adds forge + full config gate) in-repo for validation
technical-specs/README.md	TS-* normative specs for remaining automation (OMNL/sidecar, settlement indexer, SKR ETL, GRU program, compliance sign-off)
policy-profiles.json (registry)	Machine-readable profiles + GRU governance level
POLICY_PROFILES_REGISTRY.md	Doc control / sign-off table per profile version
MANIFEST_AUTOMATION_DESIGN.md	Future manifest merge/CI design (not implemented)
Compliance matrices / onboarding	Per-jurisdiction matrices, charter, playbook
Jurisdiction catalog	Catalog index + `config/jurisdictions/catalog.v1.json`
JSON Schema v1	Machine-readable resource body (`UniversalResource` subset)
URAWiring / ops	Manifest, CI validation, Phoenix `GET` route, env overrides
manifest.json (live store)	In-repo `resources[]` and `evidencePackages[]`

Validate: pnpm ura:ops-readiness / pnpm ura:ops-readiness:full (aggregate repo gate) · pnpm ura:production-ready / pnpm ura:production-ready:connectivity (target host: strict vs staging) · pnpm ura:validate · pnpm ura:validate-profiles · merge fragments: pnpm ura:merge-manifest · ledger mapping: pnpm ura:validate-ledger-mapping · writers: pnpm ura:writer:ledger / pnpm ura:writer:settlement · profile hash (on-chain anchor): pnpm ura:profile-hash · closure gate: pnpm ura:validate-closure / pnpm ura:validate-closure:strict · smoke: pnpm ura:smoke (add --http for Phoenix: manifest + policy-profiles + sidecar-probe) · on-chain id hashes: pnpm ura:keccak — wiring §2.1 · full automation tracker: URA_MANIFEST_AUTOMATION_IMPLEMENTATION_TRACKER.md

Upstream anchors

GRU M00: GRU_M00_DIAMOND_INSTITUTIONAL_SPEC.md
DBIS Rail: DBIS_RAIL_TECHNICAL_SPEC_V1.md
Custody / depository: DBIS_RTGS_DEPOSITORY_AND_CUSTODY_OPERATING_MODEL.md
RTGS checklist: DBIS_RTGS_E2E_REQUIREMENTS_MATRIX.md
VMIDs / sidecars: ALL_VMIDS_ENDPOINTS.md
Storage utilization: STORAGE_REVIEW_SUMMARY.md