User Office / Notifications

Notifications

User notification center scaffold for project updates, governance notices, Transfer Board notices, account notices, and system notices.

User Office Boundary

PRODUCT_WORKFLOW

This User Office is a prelaunch controlled mock environment. Deposit, withdrawal, settlement, revenue, recovery, Transfer Board, and wallet transfer actions shown here are simulation or review-state controls only and do not execute real money movement or token transfer.

Participant Journey Context

Participant reviewer context for the UIH-2 journey. Actions stay in Preview / Simulation / Controlled Mock mode and link to traceability rather than live execution.

ParticipantAX-LOGIPreview / SimulationNo live execution

User notifications

Open the user office notification center for participant-visible updates.

Next route: Notification Workflow.

Open Workflow Console Back to Portfolio

Inspect audit reference

Audit Preview

Open sanitized audit query context for controlled preview traceability.

User notifications

Open the user office notification center for participant-visible updates.

Inspect workflow inbox

Notification Workflow

Open the canonical workflow console for notification preview continuity.

Internal Ledger PreviewLEDGER-UIH2-AX-LOGI-PARTICIPANT-001 Audit PreviewAUD-UIH2-AX-LOGI-PARTICIPANT-001 Notification PreviewNOTIFY-UIH2-AX-LOGI-PARTICIPANT-001

Notification Center

API-backed in-app notifications appear first. Fixture notifications remain below as explicit fallback and route context.

Notification runtime proofAPI / DB visible

endpoint

/notifications/me

data source

loading

persisted records

0

external send

disabled

Data source

loading

Notification route calls /notifications/me for persisted in-app records.

Operation evidence update

Project updates

New

AX-LOGI published a new operation evidence reference.

Open linked route

Operator selection completed

Governance notices

Review

Operator selection result remains available for review.

Open linked route

Challenge threshold preview reached

Challenge notices

Preview

Challenge threshold preview reached 25% support and is ready for escalation review.

Open linked route

Emergency review preview opened

Emergency review notices

Urgent demo

Emergency review preview is open for project protection without fund freeze, settlement halt, or external enforcement.

Open linked route

Transfer eligibility boundary

Transfer Board notices

Notice

Transfer Board actions require eligibility review and approval.

Open linked route

Mock treasury controls available

Mock treasury request notices

Mock

Mock deposit and withdrawal requests are review-state controls only.

Open linked route

Account readiness

Account notices

Ready

Email is verified. MFA remains a future candidate.

Open linked route

Prelaunch mock-control boundary

System notices

System

User Office controlled mock controls are fixture-backed and do not call production services.

Open linked route

Compatibility Workflow Console

The existing deeper workflow notification console remains available as a compatibility route.

Open Notification Workflow

Notification Evidence Spine

Notification and outbox evidence rows are read from the Trace Spine notification endpoint. With query context, this panel narrows to the selected workflow; without query context, it shows recent notification/outbox evidence across workflows.

Abstract trace evidence diagram connecting source workflow, ledger, audit, notification, and controlled record nodes. — Trace evidence diagramTrace evidence diagram for ledger, audit, and notification routes.

Trace evidence diagramIllustrative, not evidence

Trace evidence diagram

This diagram clarifies source workflow, controlled record, ledger, audit, and notification continuity. The records below remain API/PostgreSQL rows with real IDs, timestamps, source routes, and trace links.

Evidence rows

0

Rows returned from the Trace Spine API and backed by PostgreSQL runtime evidence tables.

Workflow families

0

Distinct source workflow families represented in this view.

Context

operator_execution

Query context is preserved through URLSearchParams and survives refresh.

Mode

API / PostgreSQL

Evidence surfaces are read-only and link back to source workflows.

Runtime proof availableRefresh persistent

What happened: the route is reading internal evidence records through the Trace Spine API. Where it came from: operator_execution / OPPLAN-AX-WELL-001.

No runtime evidence rows matched this context.

Create or update a Founder proposal, Transfer Board request, Financial workflow, Provider dry-run, Operator execution, Governance challenge, or Admin Runtime action to create notification and outbox evidence.

DB Trace Spine

DB-backed notification trace resolved from the workflow trace ID or source entity ID. Notification records remain internal in-app records and do not create legally effective external notices.

No DB-backed trace bundle was resolved for this route context.

Notification Anchor Proof Runtime

API/PostgreSQL-backed LedgerProofRecord records with hash-only Fabric-compatible proof metadata. PostgreSQL remains the operational source of truth.

Abstract anchor proof schematic with hash reference, adapter boundary, verification node, and local ledger proof record. — Anchor proof schematicAnchor proof schematic for Fabric-compatible hash reference review.

Anchor proof schematicIllustrative, not evidence

Anchor proof schematic

The anchor schematic clarifies hash-reference-only proof, adapter boundary, verification, and local LedgerProofRecord continuity. Anchor creation, reload, verify, and error states remain API/PostgreSQL-backed controls below.

Records

0

Adapter

pending

Runtime mode

local-compatible

Network

status pending

Verification

not recorded

Trace-to-anchor query context

limit: 20
sourceEntityId: OPPLAN-AX-WELL-001
sourceWorkflow: operator_execution

Failed to parse URL from /api/fabric/anchors?limit=20&sourceEntityId=OPPLAN-AX-WELL-001&sourceWorkflow=operator_execution

No API/PostgreSQL LedgerProofRecord matched this context.

Record an anchor proof from the ledger or audit evidence route to link this notification context to LedgerProofRecord evidence.

Boundary

Hash-reference only local/dev anchor proof. No production credentials, production network finality, legal finality, accounting finality, custody, wallet signing, token transfer, payment execution, settlement execution, regulatory filing, public launch, or live activation.