01
Scope
Who needs the workflow, what is visible, and what stays out.
Loading this page.
Trust boundary · Platform kernel
The platform kernel normalizes cross-module coordination without replacing source records. Owner-safe summaries, property scope, feature gates, provider status, and capacity posture are shown as operational decision support; it does not perform autonomous dispatch, external writes, payments, tax filing, or emergency response.
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
The platform kernel normalizes cross-module coordination without replacing source records. Owner-safe summaries, property scope, feature gates, provider status, and capacity posture are shown as operational decision support; it does not perform autonomous dispatch, external writes, payments, tax filing, or emergency response.
PLATFORM_KERNEL_BOUNDARY · apps/api/src/ironbound_api/modules/platform_kernel/router.py:61
1 further boundary constant in this module
The obligation register creates work, never authority. A credential that has expired is refused at the point of use by the check that has always refused it, whether or not the generator has run. Nothing here grants a right by expiring, and no deadline in this register is a legal notice.
OBLIGATION_BOUNDARY · apps/api/src/ironbound_api/modules/platform_kernel/obligations.py:80Copied verbatim from apps/api/src/ironbound_api/modules/platform_kernel/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.