Validation Role Map

Role separation and workflow authority map for validation review

KO / LTRVIRTUAL_RECORDSHUMAN_REVIEW_READY

Validation Portal / Role Map

Role-Based Product Map

Role separation, allowed entry routes, workflows, record creation, and actions each role cannot perform in prelaunch validation mode.

Evidence source: Static fallback evidence

Validation Portal prefers `/validation/evidence/*` API data and keeps static fallback for board-demo resilience.

Fallback evidence

Validation Evidence API has not been loaded yet.

Validation portal boundary

READ_ONLY
Current mode is Prelaunch validation mode. Future mode is Live activation after required business, legal, government, provider, and operational approvals. This portal is read-only and contains no state-changing admin actions.

Role separation

This is a product role map, not an organization chart. It shows entry routes, workflow powers, records, and explicit limits.

/home

Public Visitor

Public reads remain separate from account, admin, and validation actions.

Main workflows
  • Public discovery
  • Product education
  • Login-gated continuation
Records created
  • safe returnTo route reference
Cannot perform
  • submit proposals
  • cast admin decisions
  • publish projects
/login -> /home -> /my-page

General User / Participant

Participant actions remain virtual and controlled before activation.

Main workflows
  • Project participation review
  • Simulation
  • Portfolio reference
  • Weighted operator vote
Records created
  • ParticipationRecord
  • PortfolioReference
  • ParticipantOperatorVote
Cannot perform
  • admin review
  • publication
  • operator shortlist governance
/home -> /my-page -> /founder/projects/new

Founder / Project Originator

Founder submission routes feed admin review and do not self-publish.

Main workflows
  • Project proposal
  • Business plan
  • Evidence
  • Review status
Records created
  • FounderProposal
  • BusinessPlanRecord
  • EvidenceReadinessRecord
Cannot perform
  • approve own proposal
  • publish project
  • select operator alone
/operators

Operator

Reusable profile and project-specific proposal data remain separate.

Main workflows
  • Profile readiness
  • Opportunity review
  • Proposal submission
  • Assignment status
Records created
  • OperatorProfile
  • OperatorProposal
  • OperatorReviewQueueItem
Cannot perform
  • approve proposal
  • self-assign to project
  • open funding
/admin-login -> /admin-management

Admin / Reviewer

Admin actions are not exposed in validation portal pages.

Main workflows
  • Founder review
  • Publication
  • Operator review
  • Shortlist governance
Records created
  • AdminReviewDecisionRecord
  • PublicationCandidate
  • OperatorReviewDecisionRecord
Cannot perform
  • create live legal effect
  • move funds
  • activate production provider
/validation/access -> /validation/overview

Governance / Validator

Validation portal is a curated read-only evidence console.

Main workflows
  • Evidence review
  • Lifecycle review
  • Readiness review
  • Guided demo
Records created
  • read-only validation route evidence
Cannot perform
  • state-changing admin actions
  • private data mutation
  • live activation
/audit-logs

System / Audit

System records support traceability but do not create business or legal effect.

Main workflows
  • Audit trace
  • Controlled record projection
  • Email outbox event visibility
Records created
  • AuditReference
  • ControlledRecordReference
  • EmailOutboxEvent
Cannot perform
  • final sensitive outcome without human gate
  • external execution