Scope
Who needs the workflow, what is visible, and what stays out.
Trust boundary · Management engagements
Operator portfolio data is workspace- and account-scoped. Owner views contain only published service terms and owner-visible transfer items; internal escalation, staffing, team access, and handoff notes remain in separate restricted records.
Module proof path
See the workflow, proof, and operating limits in one scan before reviewing the detailed path.
Inspect proof Open demoWho needs the workflow, what is visible, and what stays out.
Screenshot, proof card, or demo path that makes the claim inspectable.
What requires human review or source evidence.
Why this page is short
Some areas are intentionally represented by a narrow public boundary instead of a full feature page. That keeps sensitive operations, access rules, and unfinished marketing claims out of the buyer-facing experience.
How we evidence thisEnforced boundary
Operator portfolio data is workspace- and account-scoped. Owner views contain only published service terms and owner-visible transfer items; internal escalation, staffing, team access, and handoff notes remain in separate restricted records.
PORTFOLIO_BOUNDARY · apps/api/src/ironbound_api/modules/management_engagements/router.py:51
Copied verbatim from apps/api/src/ironbound_api/modules/management_engagements/router.py and regenerated from apps/api/src/ironbound_api/modules. The API returns these same strings in its boundary fields, and a drift check fails the build if this page and the source stop agreeing.
Pilot access
The best demo is not a feature checklist. It follows a request from owner intake to manager triage, vendor packet, field evidence, reviewed closeout, and owner-safe reporting.
We respond with the recommended demo route, who should attend, and what production access would require.