Route Family
Operator workspace
Loading
Preparing the next operator surface.
Keeping route continuity, tenant scope, and calm feedback in place while data resolves.
Route Family
Loading
Keeping route continuity, tenant scope, and calm feedback in place while data resolves.
Internal partner access and handoff controls. External partners use the scoped portal after an active grant is verified.
Toni Catering
Maya - Owner / Ops lead
America/Chicago
Commercial proof not connected
Event proof: Commercial proof not connected | Customer proof: source reference connected
Event proof not connected
Commercial owner owns proof not connected. Next action: Return to Command Center and connect proof
Blocked because: Event proof not connected
Proof needed: Connect this internal page to the shared commercial spine object
Commercial proof not connected
Event proof: Commercial proof not connected | Customer proof: source reference connected
Event proof not connected
Commercial owner owns proof not connected. Next action: Return to Command Center and connect proof
Blocked because: Event proof not connected
Proof needed: Connect this internal page to the shared commercial spine object
Operators prepare partner grants and handoffs here before anything appears in the external portal.
Shared object
Referral and readiness notes
Last task: Clear partner handoff item.
Selected Event context
No Event selected
Open this workspace from an Event root or add eventId to review partner handoffs around one Event.
External portal: partner users see no events, files, tasks, or payment summaries until the partner portal session endpoint verifies an active grant.
Open job readinessCalm Friction explains exactly why a partner action is blocked or allowed.
Referral attribution
Partner can see the shared event and referral credit, not tenant-private margin notes.
Handoff item
Rental proof must be attached before ops can mark the event production-ready.
Permission scope
Partner view is scoped to customer/event memory and readiness proof only.
Internal operators can register partner documents and link them to the operating record before or after external upload.
PartnerDocument
DocumentVersion
DocumentLink
DocumentAccessGrant
DocumentTag
Event command object
Partner documents must resolve Event identity through an exact document link before operators use the Event workspace for review.
Event identity
Pending until document link resolves
Commercial stage
Document evidence
Proof exists
DocumentLink + DocumentAccessGrant
Primary blocker
Missing event/entity link
Next safe action
Link document to Event, job, or proposal first
Event workspace link: eventHref
Disabled until exact Event identity resolves
Meaning: eventHref opens the operator Event workspace only after the document link resolves. Example: /events/event_123
Source record link: sourceHref
/api/v1/partners/documents
Meaning: sourceHref opens the canonical internal partner document source. Example: /api/v1/partners/documents
Proof surface link: proofHref
DocumentLink + DocumentAccessGrant evidence
Meaning: proofHref opens document-link and access-grant evidence. Example: /api/v1/partners/documents?view=evidence
Action surface link: actionHref
/partners?view=documents
Meaning: actionHref opens the exact operator task needed to attach Event identity. Example: /partners?view=documents
Fallback link: fallbackHref
/partners
Meaning: fallbackHref stays on the internal partner workspace and preserves selected Event context when available. Example: /partners?eventId=event_123 Alias: workspaceHref.
Document Event command context is operator navigation only. It does not grant partner access, expose storage paths, accept proposals, settle payment, record readiness clearance, or prove provider delivery.
Files support operating review; they do not promote commercial, payment, or readiness state.
Partner uploads create document metadata, version history, record links, tags, and document access grants.
Ops still approves canonical proposal decisions, payment proof, readiness blockers, and downstream provider completion from their source surfaces.
Entity-scoped conversation threads for events, proposals, jobs, documents, blockers, and partner tasks.
CommentThread
Comment
Mention
Reaction
Comments support coordination without becoming source truth.
`/api/v1/partners/comments` is the internal operator path. `/api/v1/partner-portal/comments` requires a partner session grant with the `comment` capability.
Partner-created comments cannot be internal-only, and comment activity does not approve artifacts, settle payment, or clear readiness blockers.
Visibility-filtered timeline entries from source events, comments, documents, and future partner tasks.
PartnerActivity
domain_event
audit_event
comment
document
task
Timeline entries help operators and partners see what changed without changing source truth.
`/api/v1/partners/activity` is the internal operator path. `/api/v1/partner-portal/activity` requires a partner session grant with the `view_activity` capability.
Partner-visible activity filters out internal-only rows and never marks proposals accepted, payments settled, jobs ready, or provider delivery complete.
Durable task lanes for partner handoffs, submissions, blockers, dependencies, and SLA review.
PartnerTask
TaskAssignment
TaskDependency
TaskSla
TaskStatus
Partner task movement is collaboration evidence, not source-of-truth promotion.
`/api/v1/partners/tasks` is the internal operator path. `/api/v1/partner-portal/tasks` requires a partner session grant with the `manage_task` capability.
Partners can move tasks through to-do, in-progress, blocked, and submitted states. Approved remains an operator-controlled state and does not clear readiness alone.
Partner responses attach to observed readiness blockers so ops can review missing staffing, delivery, rental, or venue evidence.
JobReadinessBlockerObservation
BlockerAssignment
BlockerWaiver
PartnerBlockerResponse
Partner triage is evidence for review, not readiness clearance.
`/api/v1/partners/blockers` is the internal operator path. `/api/v1/partner-portal/blockers` requires a partner session grant with the `respond_blocker` capability.
Partner responses can confirm, request more info, upload evidence, or request a waiver. Existing ops services still control blocker assignments, waivers, and job readiness.
Partner staff, availability, assignment proposals, and confirmations with ops-controlled canonical staffing.
PartnerStaffMember
StaffAvailability
PartnerStaffingAssignmentProposal
AssignmentConfirmation
StaffingAssignment
Partner proposals and confirmations support scheduling review without becoming the canonical assignment.
`/api/v1/partners/staffing` is the internal operator path. `/api/v1/partner-portal/staffing` requires a partner session grant with the `confirm_staffing` capability.
Partner staffing proposals and confirmations do not create canonical StaffingAssignment records, clear readiness, settle payment, or prove provider delivery.
Partner staff windows summarized for capacity review without booking or readiness authority.
PartnerStaffAvailabilityWindow
PartnerStaffMember
AvailabilityState
CapacitySignal
share_availability
Capacity views coordinate planning without changing the source staffing or commercial state.
`/api/v1/partners/availability` is the internal operator path. `/api/v1/partner-portal/availability` is GET-only and requires a partner session grant with the `share_availability` capability.
Partner availability windows do not book staff, create canonical StaffingAssignment records, clear readiness, settle payment, record proposal acceptance, or prove provider delivery.
Partner-visible holds, reservation states, and conflict evidence over existing inventory truth.
InventoryReservation
InventoryItem
ReservationState
PartnerInventoryHold
PartnerInventoryConflict
Partner inventory holds support planning without becoming canonical stock reservation proof.
`/api/v1/partners/inventory` is the internal operator path. `/api/v1/partner-portal/inventory` requires a partner session grant with the `reserve_inventory` capability.
Partner holds and conflicts do not create canonical InventoryReservation records, clear readiness, settle payment, or prove provider delivery. Existing ops services still reserve inventory for the job.
Versioned partner timelines for delivery, setup, service, breakdown, pickup, and venue milestones.
RunOfShow
RunOfShowVersion
RunOfShowItem
RunOfShowApproval
edit_run_of_show
Timeline collaboration supports execution review without promoting readiness or schedule truth.
`/api/v1/partners/run-of-show` is the internal operator path. `/api/v1/partner-portal/run-of-show` requires a partner session grant with the `edit_run_of_show` capability.
Partner run-of-show versions and approvals do not create canonical schedule assignments, clear readiness, settle payment, or prove provider delivery.
Approval requests, requirements, decisions, and evidence attached to exact documents, proposal artifacts, or run-of-show versions.
ApprovalRequest
ApprovalRequirement
ApprovalDecision
ApprovalEvidence
approve_artifact
Partner artifact approvals are evidence for review, not commercial acceptance or operations clearance.
`/api/v1/partners/approvals` is the internal operator path. `/api/v1/partner-portal/approvals` requires a partner session grant with the `approve_artifact` capability.
Approval decisions stay attached to the exact artifact/version target and do not record proposal acceptance, settle payment, clear job readiness, or prove provider delivery.
Version-specific annotations on document versions, proposal artifacts, and run-of-show versions.
AnnotationTarget
Annotation
AnnotationStatus
AnnotationResolution
annotate_artifact
Redlines help teams review exact artifact versions without promoting source truth.
`/api/v1/partners/annotations` is the internal operator path. `/api/v1/partner-portal/annotations` requires a partner session grant with the `annotate_artifact` capability.
Annotation targets keep the version, anchor, status, and resolution trail stable. Redlines do not record proposal acceptance, settle payment, clear readiness, or prove provider delivery.
Partner-visible venues, spaces, layout attachments, and zone map annotations for event/job planning.
Venue
VenueSpace
VenueLayout
LayoutAnnotation
EventVenuePlan
manage_venue_plan
Floorplans and zone maps help review venue logistics without becoming schedule, staffing, inventory, payment, or readiness truth.
`/api/v1/partners/venue-plans` is the internal operator path. `/api/v1/partner-portal/venue-plans` requires a partner session grant with the `manage_venue_plan` capability.
Partner venue plans and layout annotations do not clear job readiness, create canonical schedule/staffing/inventory assignments, settle payment, record proposal acceptance, or prove provider delivery.
Partner and customer-facing proposal option guidance over issued option sets.
ProposalOptionSet
ProposalOption
PartnerOptionRecommendation
SelectedProposalOptionSnapshot
recommend_proposal_option
Recommendations help ops review partner preference without changing proposal acceptance or job scope.
`/api/v1/partners/proposal-options` is the internal operator path. `/api/v1/partner-portal/proposal-options` requires a partner session grant with the `recommend_proposal_option` capability.
Partner option recommendations do not record proposal acceptance, settle payment, clear job readiness, create job scope, or prove provider delivery. The selected option still flows through customer/proof-bound acceptance.
Partner-safe payment checkpoints over accepted commercial context, handoff lifecycle, and provider-backed payment evidence.
PaymentMilestone
PaymentTransaction
PaymentHandoffLifecycleEvent
JobPaymentStatusProjection
view_payment_summary
Milestones summarize payment evidence for review without becoming settlement, acceptance, or readiness authority.
`/api/v1/partners/payment-milestones` is the internal operator path. `/api/v1/partner-portal/payment-milestones` is GET-only and requires a partner session grant with the `view_payment_summary` capability.
Partner-visible milestones do not settle payment, record proposal acceptance, clear job readiness, create job scope, or prove provider delivery.
Operator-managed request templates and partner-submitted field-state evidence.
PartnerSmartRequestTemplate
PartnerSmartRequestField
PartnerSmartRequestResponse
PartnerSmartRequestFieldState
submit_smart_request
Requests collect partner answers and field states for operator review without changing commercial truth.
`/api/v1/partners/smart-requests` lets operators list templates, create templates, and submit field-state evidence. `/api/v1/partner-portal/smart-requests` requires a partner session grant with the `submit_smart_request` capability.
Partner smart requests do not create quotes, record proposal acceptance, settle payment, clear job readiness, or prove provider delivery.
Partner confirmations and disputes flow into operator review and provenance.
PartnerFieldConfidenceReview
CommercialFieldState
ProvenanceFact
PartnerActivity
review_field_confidence
Partner confidence helps operators decide what to trust without becoming commercial truth.
`/api/v1/partners/field-confidence` lets operators list, submit, and review field confidence records. `/api/v1/partner-portal/field-confidence` requires a partner session grant with the `review_field_confidence` capability.
Partner field confidence reviews do not confirm commercial truth, record proposal acceptance, settle payment, clear job readiness, or prove provider delivery.
Partner-reported issues, severity, and photo evidence for operator triage.
PartnerIssueReport
IssuePhotoEvidence
PartnerActivity
OpsTriage
report_issue
Issue photos help ops decide what to triage without becoming source resolution.
`/api/v1/partners/issues` lets operators list, create, and triage issue reports. `/api/v1/partner-portal/issues` requires a partner session grant with the `report_issue` capability.
Partner issue reports and photos do not clear readiness, waive blockers, create canonical assignments, settle payment, record proposal acceptance, or prove provider delivery.
Derived task, SLA, issue, photo, and staffing-confirmation signals for operator review.
PartnerScorecard
PartnerTaskSla
IssueMetrics
StaffingConfirmations
view_scorecard
Scorecards summarize partner collaboration health without becoming commercial, readiness, payment, or delivery authority.
`/api/v1/partners/scorecard` is the internal operator path. `/api/v1/partner-portal/scorecard` requires a partner session grant with the `view_scorecard` capability.
Partner scorecards do not rank commercial truth, clear readiness, waive blockers, create canonical assignments, settle payment, record proposal acceptance, or prove provider delivery.