Human authority
Capability and permission are separate. Human or institutional decision rights remain explicit unless a bounded delegation is defined.
This page records the public controls and boundaries we apply to authority, evidence, data handling, third-party references and commercial interaction.
Static, public information layer
Not active
Not used on bpm.ba
Not used on the current public site
We publish the constraints that matter before asking an institution, client or researcher to trust a broader capability claim.
Capability and permission are separate. Human or institutional decision rights remain explicit unless a bounded delegation is defined.
Planned, experimental, observed and validated states are not interchangeable. Failure and limitations remain part of the record.
Public engagement asks for information needed to qualify the mission. Sensitive operational data is not requested through public forms unless a protected route is established.
The public site exposes product and research context, not credentials, private repositories, model secrets or protected implementation logic.
Public architecture is intentionally useful but incomplete. Proprietary routing, policy logic and implementation detail remain controlled.
Infrastructure providers, programmes or research environments are named only for factual context. Use does not imply endorsement, certification or partnership.
The future platform layer is being designed around invitation, role assignment and workspace-level permissions rather than unrestricted public registration.
Existing public pages remain openly accessible. Gated evidence, partner rooms, client rooms and internal Mission Room capabilities belong to the next platform phase and will not be simulated with a superficial login screen.
Trust claims should point to an actual boundary, policy or evidence source.