System authority
Owns core architecture boundaries, platform direction and high-impact technical decisions.
Leadership & operating model
Authority should be visible before decisions become consequential.
BPM RED Academy uses explicit architecture, domain and review responsibilities rather than treating every contributor as having the same decision rights.
Founder
Edin Vučelj
System & Product Architecture
Leads the public product thesis, governance-runtime architecture, validation methodology, evidence discipline and system-level product direction for BPM RED Academy and HumAI MightHub.
Architecture authoritySystem boundary • product architecture • validation contract • public technical claims
Operating model
Roles are separated by decision right.
The organisation is being built around clear responsibilities that can later map directly into controlled workspaces and platform permissions.
Domain lead
Owns domain validity, constraints and acceptance criteria inside a defined vertical or mission.
Reviewer
Challenges claims, evidence packages and decision gates without inheriting execution authority.
Implementation contributor
Builds within approved scope; implementation access does not imply authority to approve outcomes.
Operations & administration
Supports organisational process, records, coordination and controlled external engagement.
External specialist
Contributes bounded expertise without receiving broader system or organisational authority.
Contribution ≠ approval ≠ authority.
The same principle used in governed AI applies internally: access to information or execution capability does not automatically grant decision rights.
Public team disclosure
Only roles and individuals whose mandate is stable and approved for public disclosure are listed here. Wider team and project participation can remain private until a public role is necessary.
Next
See how authority becomes a trust control.
The Trust Center describes the public boundaries around human authority, security, evidence and disclosure.