Admin Management
Preparing Admin Management operations console
Admin Management controlled records are being prepared for the operations console.
Admin Management
Operations console with data-source-aware module linkage
Runtime DB/API Binding
This panel reads PostgreSQL-backed runtime queues and records safe admin actions through the API. API failure is shown directly.
Review the live internal operations queue, record admin acknowledgements through the API, and move into compliance, treasury, provider, or notification evidence routes.
Current state
loading
Evidence
Runtime evidence appears after /admin/runtime/overview responds.
Internal development/test execution record. Real investment solicitation, payment, settlement, wallet signing, rights transfer, regulatory filing, and commercial/legal effect occur only after required business licenses, contracts, legal review, and separate Production Activation approval.
Next reviewer
Admin reviewer / compliance operator
The admin console now presents queue state, runtime failure, trace references, and next action groups before the older module inventory. This follows the benchmark principle of putting the user task and trust evidence first.
The screen is waiting for runtime data. Loading state is shown before any fallback content.
pending
The API contract reports true only when the overview is read from runtime persistence.
not used before API response
Fixture fallback must remain false for this runtime command surface.
loading
Queue count is visible so empty state and API failure are not confused.
pending
Latest admin action trace links this console to audit, ledger, and notification records.
Actions in this group are internal API-backed operations for the current admin role.
Navigation actions move across route families without creating external execution.
These product capabilities may be implemented, but live operation stays disabled here.
endpoint
/admin/runtime/overview
status
loading
api failure visible
pending
live activation
required before production
Controlled Pilot Runtime
This panel reads the pilot scenario through the API and prepares persisted PostgreSQL records for founder, provider, participant, financial, operator, governance, admin, trace, ledger, audit, and notification surfaces.
Gate 416-ADM / ADMIN-COMPLIANCE-ERP
Internal command center for queues, alerts, reports, records, ERP tasks, and agent recommendations.
Admin / Compliance / ERP operating mode
CONTROLLED_RECORDLaunch-fast-build admin path through operations overview, users, projects, compliance, incidents, operator reports, treasury, ERP, provider readiness, audit, and notifications.
You are here
This route is the active open internal entry step in the controlled launch journey. Continue through the route cards below for the nearby preview, ledger, audit, and notification context.
Admin / Compliance launch boundary
PRODUCT_WORKFLOWPriority operating queue that binds review work, provider readiness, controlled records, ledger previews, audit previews, and notification previews into one internal command-center view.
Settlement / revenue preview exception · Review queue item linked to controlled record, internal ledger preview, audit preview, and notification preview.
Next controlled action: Request reconciliation note preview
CR-ADM-SETTLEMENT-REVIEW-001 · Compliance
Provider readiness latest dry-run state · Provider latest dry-run state linked to controlled record, ledger preview, audit preview, notification preview, and evidence route.
Next controlled action: Review Sumsub dry-run evidence and keep production activation blocked.
CR-PA-SUMSUB-IDENTITY-SUCCESS · Sumsub
Challenge escalation operations review · Incident queue item linked to controlled record, audit preview, notification preview, and project-protection review state.
Next controlled action: Assign independent review preview
CR-GC-ESCALATION-001 · Compliance
Manual admin control-plane view for production activation readiness. Controlled workflows stay active for development and testing; real external activation remains blocked until future approval.
Local/dev product workflows, controlled records, previews, simulations, and dry-runs stay active.
Internal or stakeholder pilot can proceed only with synthetic data, access list, runbook, and evidence capture.
Approved sandbox credentials and endpoints require owner, provider, security, and privacy review.
Restricted production use requires legal, compliance, security, provider, operations, and owner approval.
Public launch remains blocked until full go/no-go approval and production controls are complete.
No blocker for controlled internal workflow development and testing.
Next safe admin action: Continue controlled productization and browser QA.
Credential vault, owner approval, rotation, revoke, and audit process are not approved.
Next safe admin action: Prepare credential approval package; do not create production secrets.
Production contract, DPA, endpoint allowlist, signature verification, and incident process are pending.
Next safe admin action: Review provider dry-run evidence and contract checklist.
Consent, retention, export/delete, redaction, access control, and incident approval are pending.
Next safe admin action: Prepare privacy approval package with synthetic-data evidence.
Licensed provider, AML/compliance, reconciliation, custody, signing, transfer, and finality policies are pending.
Next safe admin action: Review simulation evidence; keep real asset movement blocked.
UAE activation, legal opinion, partner/license, board approval, and filing approval are not recorded.
Next safe admin action: Prepare legal and regulatory owner-review package.
Production deployment, migration, backup, monitoring, rollback, support, and on-call approval are pending.
Next safe admin action: Prepare operations readiness and incident package.
Canonical admin-management route family for internal Admin, Compliance, Reviewer, ERP Operator, and System Agent preview workflows.
Admin visuals explain route family coordination only. Review queues, provider dry-runs, treasury actions, ledger/audit links, notifications, and API errors remain real UI records and controls.
Operations Overview
Internal command center for queues, alerts, reports, records, ERP tasks, and agent recommendations.
User / Role / Permission Administration
User account, role, permission, workspace access, and role-change controlled record previews.
Project Registry Admin Operations
Project registry status, visibility, proposal, governance, operator, participant, audit, and controlled-record linkage.
Review / Compliance Queue
Risk flags, emergency review, provider readiness, settlement exceptions, and compliance decision previews.
ERP Operations Workflow
Internal ERP task, document checklist, approval, assignment, and operational history workflow.
Operator Report / Execution Admin Review
Project execution, operator report, milestone, work log, risk, evaluation, and handover admin review.
Provider Sandbox / External API Readiness
Provider category registry, sandbox/mock adapter readiness, dry-run lifecycle, credential boundary, and future activation review.
Review Assignment Console
Proposal, evidence, operator, challenge, settlement, and reviewer assignment queue.
Incident / Challenge / Escalation Console
Challenge, escalation, emergency review, independent review, findings, appeal, and project protection previews.
Controlled Record Admin View
Controlled record list, review state, related workflow, exception flags, and audit linkage.
Treasury / Ledger Admin View
Internal ledger, debit/credit preview, settlement/revenue records, treasury record, reconciliation, and exception review.
Admin operations overview across projects, proposals, reviews, challenges, operators, records, ERP work, notifications, and system-agent recommendations.
Active projects
2
Projects visible in registry operations preview.
Review queue
3
Review, compliance, settlement, and escalation items requiring human review.
Operator reports
1
Operator execution reports waiting for admin or compliance inspection.
ERP tasks
2
Internal ERP task cards using local preview state only.
Record previews
5
Controlled record and ledger preview references visible to admin.
Agent recommendations
2
System agent recommendations awaiting accept/reject preview.
Admin Operations
Platform operations can inspect queues, records, assignments, and readiness without becoming the project Operator.
Compliance Queue
Risk flags, provider readiness, settlement exceptions, emergency review, and escalation items remain human review states.
ERP Operations
Internal tasks, document checklists, owners, due dates, approval steps, and operational history are tracked as preview workflow cards.
User, role, permission, workspace access, account verification, and role-change controlled record previews.
founder.demo@example.test
Roles
Founder, Project proposer
Workspace access
Founder projects, Proposal review status
Record / audit
operator.demo@example.test
Roles
Operator, Evidence submitter
Workspace access
Operator workspace, Assigned AX-LOGI operation
Record / audit
compliance.preview@example.test
Roles
Compliance, Reviewer
Workspace access
Compliance queue, Audit logs, Controlled records
Record / audit
Project registry admin operation previews with proposal, governance, operator, participant, controlled record, and audit linkage.
Participant portfolio and transfer previews linked
Readiness-only participant state
Proposal, evidence, operator report, challenge, emergency review, settlement/revenue, reviewer assignment, overdue, and missing evidence queue previews.
Founder proposal and evidence · Evidence package attached · Due in 2 days
Decision preview: Mark review readiness preview
Settlement / revenue preview exception · Settlement report preview requires reconciliation note · Today
Decision preview: Request reconciliation note preview
Challenge escalation and emergency review · Independent review evidence pending · Overdue by 1 day
Decision preview: Assign independent review preview
Reading ChallengeCase, audit, ledger, outbox, notification, and admin queue references from the runtime API.
Active challenge, escalation, emergency review, independent review, findings, appeal, Good Leaver / Bad Leaver, and project protection previews.
Finding draft pending · Good Leaver protection / Bad Leaver review preview · Project protection action preview only
Admin reviews operator work; the operator workspace remains linked but separate from admin controls.
Reading AX-LOGI operation plan, evidence, audit, ledger, and notification references from the runtime API.
Cost / revenue / settlement report preview · Vendor delay risk open · Quarterly evaluation preview · Handover package ready for review preview
Internal ledger and treasury controlled record previews for review, reconciliation, exceptions, and audit linkage. This is not a wallet, bank, exchange, order-book, payment, or trading surface.
Debit Preview
Operator cost preview debit
Credit Preview
Revenue recovery preview credit
Debit Preview
Portfolio update preview
Credit Preview
Participation rights movement preview
Internal task/process/document/approval workflow with owner, due date, priority, related workflow, operational history, and controlled record linkage.
Provider readiness checklist · Compliance reviewer preview
Board/government validation package · Admin approval preview
Admin notification center and System Agent recommendation preview. Accept/reject updates only frontend-local state.
Challenge escalation requires compliance review
NOTIFY-GC-ESCALATION-001Operator report ready for admin review
NOTIFY-OP-REPORT-001ERP evidence task due today
NOTIFY-ERP-OVERDUE-001Evidence gap detected
Request missing evidence preview for AX-LOGI provider readiness.
Review bottleneck detected
Assign compliance reviewer preview for settlement exception.
Sensitive operations boundary
CONTROLLED_RECORDP2-FE-000 / ADMIN-MANAGEMENT
Internal operations console for prototype module visibility, data-source status, and controlled-record coordination. External financial execution remains a future Live Activation Gate concern.
The screen attempts the local Admin Management API and uses approved admin fixtures when the API is unavailable.
Source mode
API_WITH_FIXTURE_FALLBACK
Gate 239 canonical data source mode for the admin management reference screen.
API access
Allowed
API reads are attempted only through the configured local binding.
Fixture fallback
Available
Fallback status stays visible so admin data is not mistaken for production state.
Admin Management activation boundary
CONTROLLED_RECORDOpen the next operational workflow without memorizing admin routes. Every action remains local/demo, auditable, and separated from live activation.
Start, request revision, approve, or reject founder proposals with review records.
Convert approved proposals into public discovery records without opening funding.
Inspect operator profiles, request clarification, select for demo, or reject.
Open governance shortlists for participant weighted voting.
Review tally, assignment, audit reference, and operation preparation state.
Review operation plans, milestones, tasks, URL evidence, and admin decisions.
Review board/government evidence in read-only validation mode.
Admin users should start from the action they need to complete, not from a route list. Approve, publish, operator review, shortlist, voting, and validation evidence remain visibly separated.
Direct links to the role-separated admin review consoles required for human validation walkthroughs.
Review founder submissions, request revision, approve for publication candidacy, or reject.
Open consoleMap approved projects into public discovery without opening funding.
Open consoleReview operator capability, request clarification, select for demo, or reject.
Open consolePrepare shortlists and open participation-unit weighted voting.
Open consoleCanonical stakeholder walkthrough across implemented core routes. Links point to canonical routes only; future activation remains a labeled non-live boundary.
Start with the implemented Project Registry list and visible Data Source Status.
Open a canonical project detail record from the current sandbox fixture/API-shaped data.
Review proposal readiness and evidence references without implying external fundraising activation.
Inspect reviewer/DD records, checklist state, evidence notes, and review boundaries.
Open a review case detail route with controlled actions and fixture fallback disclosure.
Show project governance as a non-live consensus simulation and controlled decision record.
Inspect a governance detail route with participant signal records and future activation boundaries.
Finish with Admin Management as the operations overview and module linkage control surface.
Admin-facing local sandbox operations view for Live Activation workflow readiness, provider status, security blockers, document package readiness, and controlled-record references.
Current workflow step
Payment rail
Current step from the local sandbox workflow state machine.
Provider statuses
11/11
Provider status cards available through local stub readiness only.
Blocked steps
1
Workflow steps blocked by dependency or future-gated readiness.
Security blocked rules
5
Security rules blocking external URLs, credentials, PII, network calls, and live execution.
Live Activation operations boundary
CONTROLLED_RECORDCurrent workflow status: Requires review. Next action: Run local payment preview.
Workflow steps: 5
Project company, SPV, and operator execution readiness is visible as fixture-only local/sandbox metadata for Energy Microgrid Preview.
Entity readiness: Fixture-only
Identity verification / Local stub / Provider selection required; KYC / KYB / Local stub / Legal / compliance review required; Custody / Local stub / Provider selection required; Payment rail / Local stub / Provider selection required; Settlement / Local stub / Future live activation required; Document verification / Local stub / Provider selection required
Local stub providers: 11
Identity / KYC-KYB sandbox adapter is available as a local stub. No real PII is submitted.
Provider references: 2
Custody sandbox reference is available after identity readiness. No wallet, custody account, or key operation exists.
Provider references: 2
Payment rail adapter can generate local instruction previews only. No bank API, stablecoin transfer, payout, or wallet transfer is enabled.
Provider references: 1
Settlement preview waits for payment rail preview review and remains future-gated for live execution.
Provider references: 1
Document verification can prepare a local activation package checklist in parallel. No external verification, e-signature, notarization, or filing occurs.
Provider references: 1
External URLs, credentials, PII payloads, network calls, live execution, and environment promotion remain blocked.
Blocked rules: 5
Controlled record / audit references
Next recommended local action: Run local payment preview.
Local operations actions
Provider activation requires a future Live Activation Gate and approved external provider boundary.
Admin and compliance review surface for the selected provider controlled sandbox status, evidence, audit trace, redaction state, and pre-activation review prerequisites.
Readiness items
9
Evidence records connected from the UAE Activation readiness binding.
Controlled ready
4
Items already represented as controlled local/sandbox implementation evidence.
Checklist items
4
Checklist rows inherited from the selected named provider dashboard binding.
Open review items
2
Open items that require future security/legal/compliance approval.
Provider review boundary
CONTROLLED_RECORDAdapter and configuration status
Route metadata and controlled integration tests cover Sumsub readiness/status/webhook-preview audit boundaries.
No-real-provider boundary labels
Provider legal/compliance decision is pass-with-conditions for controlled sandbox continuation, not legal eligibility approval.
Technical API review supports controlled local/sandbox modeling without enabling external provider calls.
Adapter scaffold, synthetic flow mapping, redaction, and controlled local API surface are implemented.
Provider status is visible in UAE Activation with API_WITH_FIXTURE_FALLBACK and no external provider call.
Synthetic applicant and business verification flow coverage is available for controlled demo review.
Webhook preview is redacted and audit-shaped only; production webhook ingestion remains future-gated.
Controlled response wrappers expose audit event and controlled-record projection references.
Prelaunch workbook coverage is available as business-model context for provider readiness review.
Any real sandbox credential, real provider account, production webhook, or live activation requires a later security/legal/compliance gate.
Controlled trace projection for admin/compliance review. Identifiers are local references, not external provider event ids.
Provider legal/compliance decision is pass-with-conditions for controlled sandbox continuation, not legal eligibility approval.
Evidence: Gate 377 decision record · Source: docs/reviews/GATE_377_PROVIDER_LEGAL_COMPLIANCE_DECISION_RECORD_v0.1.md
Technical API review supports controlled local/sandbox modeling without enabling external provider calls.
Evidence: Gate 378 technical review · Source: docs/reviews/GATE_378_PROVIDER_TECHNICAL_API_REVIEW_v0.1.md
Adapter scaffold, synthetic flow mapping, redaction, and controlled local API surface are implemented.
Evidence: Gate 402-404 implementation · Source: docs/reviews/GATE_405_FIRST_PROVIDER_ADAPTER_CLOSEOUT_DASHBOARD_READINESS_v0.1.md
Provider status is visible in UAE Activation with API_WITH_FIXTURE_FALLBACK and no external provider call.
Evidence: Gate 407 dashboard binding · Source: docs/reviews/GATE_407_PROVIDER_STATUS_DASHBOARD_API_BINDING_REVIEW_v0.1.md
Synthetic applicant and business verification flow coverage is available for controlled demo review.
Evidence: Synthetic flow catalog · Source: /live-activation/providers/sumsub/synthetic-flows
Webhook preview is redacted and audit-shaped only; production webhook ingestion remains future-gated.
Evidence: Webhook preview boundary · Source: /live-activation/providers/sumsub/webhook-preview
Controlled response wrappers expose audit event and controlled-record projection references.
Evidence: Controlled record / audit · Source: docs/dev/GATE_404_PROVIDER_API_WEBHOOK_CONTROLLED_INTEGRATION_REFERENCE_v0.1.md
Prelaunch workbook coverage is available as business-model context for provider readiness review.
Evidence: Gate 400 workbook · Source: docs/reviews/GATE_400_PRELAUNCH_READINESS_WORKBOOK_BUSINESS_MODEL_COVERAGE_CLOSEOUT_v0.1.md
Any real sandbox credential, real provider account, production webhook, or live activation requires a later security/legal/compliance gate.
Evidence: Pre-activation review · Source: Future Pre-Activation Security / Legal / Compliance Gate
Local/demo emergency controls for pausing sensitive sandbox workflow surfaces through controlled-record and audit references.
Emergency records
3
Fixture/API-shaped emergency control records visible to admin review.
Frozen scopes
2
Scopes currently paused or frozen in local/demo state.
Release requests
1
Release requests requiring local admin/compliance review.
Control records
3
Controlled-record references paired with audit event markers.
Provider sandbox checklist requires compliance review before additional preview actions.
Treasury ledger preview references need operator confirmation.
Stakeholder pilot dry run completed and release review was requested.
Admin action boundary
Admin can apply demo freeze for local/demo scope only.
Apply demo freezeParticipant action boundary
Participant does not have Freeze / Apply demo permission in the local/demo role matrix.
Denied for freeze applyAdmin-facing lifecycle summary across implemented core project records. This is local/demo lifecycle visibility, not production execution.
Proposal, review, governance, admin, and future activation state are shown as controlled local/demo lifecycle records.
Proposal, review, governance, admin, and future activation state are shown as controlled local/demo lifecycle records.
Proposal, review, governance, admin, and future activation state are shown as controlled local/demo lifecycle records.
Proposal, review, governance, admin, and future activation state are shown as controlled local/demo lifecycle records.
Proposal, review, governance, admin, and future activation state are shown as controlled local/demo lifecycle records.
Proposal, review, governance, admin, and future activation state are shown as controlled local/demo lifecycle records.
Lifecycle visibility may reference financial-platform concepts as prototype, sandbox, simulation, controlled-record, or future activation states only.
Admin-facing proposal intake checkpoint derived from existing proposal fixtures and lifecycle handoff helpers.
Proposal records
9
Proposal records visible in the current API/fixture binding.
Available handoffs
2
Proposal records with route-safe next lifecycle steps.
Source mode
API_WITH_FIXTURE_FALLBACK
Fallback remains visible until deeper local API persistence is selected.
Governance preparation is available through the canonical governance record.
Governance preparation is available through the canonical governance record.
Registry linkage is pending because no matching project record is available in the current fixture/API result.
Registry linkage is pending because no matching project record is available in the current fixture/API result.
Registry linkage is pending because no matching project record is available in the current fixture/API result.
Registry linkage is pending because no matching project record is available in the current fixture/API result.
Registry linkage is pending because no matching project record is available in the current fixture/API result.
Registry linkage is pending because no matching project record is available in the current fixture/API result.
Registry linkage is pending because no matching project record is available in the current fixture/API result.
Audit-friendly local/demo records that show source, status, environment, evidence note, and safe canonical links. These are not production legal settlement records.
Admin checkpoint summarizes local/demo operations and module linkage state.
Data source mode is surfaced to avoid hiding fixture fallback.
Real external identity, custody, payment, settlement, securities, and trading activation stays future-gated.
Prototype participation-right and unitization references for local/sandbox controlled records. These are product-scope concepts, but this panel does not issue units, transfer tokens, settle value, or create legally binding investor rights.
References
8
Prototype rights references available for review.
Controlled records
8
Controlled-record references linked to rights readiness.
Future gated
2
Rights references that require a future Live Activation Gate.
Disclosure
5
References that require local disclosure review.
Derived from a read-only Participation Unit Simulation fixture; no external issuance, custody, settlement, or transfer is executed.
Derived from a read-only Participation Unit Simulation fixture; no external issuance, custody, settlement, or transfer is executed.
Project-level governance right reference for sandbox participation design.
Local/sandbox treasury records, ledger references, settlement planning records, and distribution previews. External network, wallet, custody, payment, settlement, and trading execution are not active.
Reference amount: 25000 AED_REFERENCE. Demo reference only.
Treasury value is a demo planning reference and is not a payment instruction.
Reference amount: 25000 AED_REFERENCE. Demo reference only.
Settlement planning is shown as a local scenario preview without external execution.
Reference amount: 1000 PROJECT_UNIT_REFERENCE. Demo reference only.
Distribution preview is a simulation artifact for project performance modeling.
Linked modules
12
Admin-visible modules with canonical route linkage.
Audit events
13
Append-only activity references available to the operations console.
Open operations
5
Human-reviewed queues, incidents, and workflow checkpoints.
Canonical route links are shown only for implemented route families. Alias routes and missing route trees are not linked.
Project list/detail routes are canonical and safe for admin navigation.
Records
6
Records visible to the admin overview fixture/API-shaped binding.
Readiness
Reference implementation
Implementation readiness observed from the current route family.
Follow-up
Use registry status as the top-level operations inventory.
Operational follow-up for the next admin/ERP iteration.
Review queue and detail routes are canonical and route-state covered.
Records
0
Records visible to the admin overview fixture/API-shaped binding.
Readiness
Reference implementation
Implementation readiness observed from the current route family.
Follow-up
Use Review/DD status as the admin coordination lane.
Operational follow-up for the next admin/ERP iteration.
Governance records are controlled records with future Live Activation Gate boundaries.
Records
2
Records visible to the admin overview fixture/API-shaped binding.
Readiness
Consensus simulation reference
Implementation readiness observed from the current route family.
Follow-up
Use consensus status for prototype governance operations visibility.
Operational follow-up for the next admin/ERP iteration.
Proposal list/detail/new routes are canonical and now expose proposal-to-lifecycle handoff status for admin visibility.
Records
9
Records visible to the admin overview fixture/API-shaped binding.
Readiness
Lifecycle handoff ready
Implementation readiness observed from the current route family.
Follow-up
Use proposal handoff status to coordinate intake, review readiness, and registry linkage.
Operational follow-up for the next admin/ERP iteration.
Founder-submitted local proposal queue items can now be reviewed through admin actions without public discovery exposure.
Records
9
Records visible to the admin overview fixture/API-shaped binding.
Readiness
Admin decision workflow ready
Implementation readiness observed from the current route family.
Follow-up
Use approval output as a publication candidate for the next publish workflow.
Operational follow-up for the next admin/ERP iteration.
Approved founder proposals can be published to public discovery only through an explicit publish action. Funding remains not open.
Records
9
Records visible to the admin overview fixture/API-shaped binding.
Readiness
Publication workflow ready
Implementation readiness observed from the current route family.
Follow-up
Use publication output as the public discovery source for operator proposal workflow.
Operational follow-up for the next admin/ERP iteration.
Submitted operator proposals create local queue items for future operator review and selection.
Records
0
Records visible to the admin overview fixture/API-shaped binding.
Readiness
Queue visibility ready
Implementation readiness observed from the current route family.
Follow-up
Use the queue as the entry point for the next operator selection workflow.
Operational follow-up for the next admin/ERP iteration.
Assigned operators now move into operation plan, preparation, milestone, task, evidence, review, and progress workflows.
Records
1
Records visible to the admin overview fixture/API-shaped binding.
Readiness
Operation evidence workflow ready
Implementation readiness observed from the current route family.
Follow-up
Use operation evidence records for validation portal and board/government walkthrough evidence.
Operational follow-up for the next admin/ERP iteration.
Participation rights and unitization references are available as local/sandbox controlled records.
Records
2
Records visible to the admin overview fixture/API-shaped binding.
Readiness
Prototype controlled-record reference
Implementation readiness observed from the current route family.
Follow-up
Use rights references for lifecycle visibility before any future Live Activation Gate.
Operational follow-up for the next admin/ERP iteration.
Treasury records, ledger references, settlement planning, and distribution previews are visible as local/sandbox controlled records.
Records
6
Records visible to the admin overview fixture/API-shaped binding.
Readiness
Prototype controlled-record reference
Implementation readiness observed from the current route family.
Follow-up
Use ledger visibility for future Live Activation readiness without external execution.
Operational follow-up for the next admin/ERP iteration.
Audit log list/detail/correlation routes expose controlled local records with canonical related-route links.
Records
13
Records visible to the admin overview fixture/API-shaped binding.
Readiness
Controlled record support module
Implementation readiness observed from the current route family.
Follow-up
Use audit status as evidence for lifecycle/admin traceability.
Operational follow-up for the next admin/ERP iteration.
Identity access shows local/demo role and permission visibility without production auth rewrite.
Records
6
Records visible to the admin overview fixture/API-shaped binding.
Readiness
Demo role and permission matrix
Implementation readiness observed from the current route family.
Follow-up
Use role matrix visibility for admin coordination and future identity activation planning.
Operational follow-up for the next admin/ERP iteration.
Compliance queue
Assigned role: compliance
Controlled record queue
Assigned role: compliance
Treasury record review placeholder
Controlled simulation record only; no funds movement.
Assigned role: compliance
Participant protection escalation
Human review required before any recommendation.
Assigned role: compliance
UAE activation readiness check
Regulatory classification questions are tracked for later Activation Gate review.
Assigned role: compliance
payment instruction
Controlled-record visibility only; external execution requires a future Live Activation Gate.
wallet instruction
Controlled-record visibility only; external execution requires a future Live Activation Gate.
treasury execution
Controlled-record visibility only; external execution requires a future Live Activation Gate.
trading system
Controlled-record visibility only; external execution requires a future Live Activation Gate.
securities administration
Controlled-record visibility only; external execution requires a future Live Activation Gate.
Actions observed
project.read_viewed
Source modules
frontend-api-binding