Operation evidence update
Project updates
AX-LOGI published a new operation evidence reference.
Open linked routeUser Office / Notifications
User notification center scaffold for project updates, governance notices, Transfer Board notices, account notices, and system notices.
User Office Boundary
PRODUCT_WORKFLOWThis 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 reviewer context for the UIH-2 journey. Actions stay in Preview / Simulation / Controlled Mock mode and link to traceability rather than live execution.
User notifications
Open the user office notification center for participant-visible updates.
Next route: Notification Workflow.
Audit Preview
Open sanitized audit query context for controlled preview traceability.
User notifications
Open the user office notification center for participant-visible updates.
Notification Workflow
Open the canonical workflow console for notification preview continuity.
API-backed in-app notifications appear first. Fixture notifications remain below as explicit fallback and route context.
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
AX-LOGI published a new operation evidence reference.
Open linked routeOperator selection completed
Governance notices
Operator selection result remains available for review.
Open linked routeChallenge threshold preview reached
Challenge notices
Challenge threshold preview reached 25% support and is ready for escalation review.
Open linked routeEmergency review preview opened
Emergency review notices
Emergency review preview is open for project protection without fund freeze, settlement halt, or external enforcement.
Open linked routeTransfer eligibility boundary
Transfer Board notices
Transfer Board actions require eligibility review and approval.
Open linked routeMock treasury controls available
Mock treasury request notices
Mock deposit and withdrawal requests are review-state controls only.
Open linked routeAccount readiness
Account notices
Email is verified. MFA remains a future candidate.
Open linked routePrelaunch mock-control boundary
System notices
User Office controlled mock controls are fixture-backed and do not call production services.
Open linked routeThe existing deeper workflow notification console remains available as a compatibility route.
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.
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.
What happened: the route is reading internal evidence records through the Trace Spine API. Where it came from: operator_execution / OPEV-AX-LOGI-002.
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-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.
API/PostgreSQL-backed LedgerProofRecord records with hash-only Fabric-compatible proof metadata. PostgreSQL remains the operational source of truth.
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.
Trace-to-anchor query context
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.