The platform
A governed decisioning layer, not another board portal.
Boardverse is a workflow, decision and evidence platform for boards and executive teams adopting AI under real scrutiny.
Every record that enters the platform is provisional until a named person confirms it. Every confirmation is written to an immutable audit trail.
Enforcement
Five things the platform will not let you skip.
Segregation of duties, five modules deep
Risk register, financial packs, board actions, resolutions and financial snapshots each gate a token-submitted record behind a Founder confirm that the submitter cannot perform themselves. The rule is enforced server-side, not hidden in the interface.
Dual sign-off with content integrity
A resolution needs a Chair and a Founder, two different people. If the text changes between the two signatures, the first signature is invalidated automatically. A signature can never be claimed against text that later changed.
Threshold-based risk escalation
Severity is computed server-side, never client-submitted, and recomputed from impact and likelihood on every save. Crossing the organisation's threshold fires an audit-logged escalation to Founder and COO, by email and in-app.
Variance-linked financial packs
A material variance blocks submission until it is tied to a real board action or resolution. Once approved, a pack is immutable and supersede-only.
Ask Poseidon
A weekly synthesis grounded in live governance data, with a source citation on every claim. The platform's AI narrates from the governed record, never from an uncited summary.
The modules
Twenty-one modules in one governed record.
Grouped as the platform presents them.
Overview
Governance
Operations
Growth
Account
Security
Passkey and MFA as standard. Module-scoped access tokens, access-logged.
Platform questions
What is the confirmation gate?
The rule that nothing a connected tool submits becomes official until a person who did not submit it says so. The submitter can never confirm their own entry, and the rule is enforced server-side, not hidden in the interface.
How does dual sign-off prevent backdating?
A resolution needs a Chair signature and a Founder signature from two different people. If the text changes between the two signatures, the first signature is invalidated automatically, so a signature can never be claimed against text that later changed.
Is risk severity client-submitted?
No. Severity is computed server-side, never client-submitted, and recomputed from impact and likelihood on every save. Crossing the organisation's threshold fires an audit-logged escalation to Founder and COO, by email and in-app.
What happens to a financial pack after approval?
A material variance blocks submission until it is tied to a real board action or resolution. Once approved, a pack is immutable and supersede-only.
Which modules are covered?
Twenty-one, in five groups. Overview: Dashboard and Ask Poseidon. Governance: Board Portal, Resolutions, Risk Register, Board Calendar, Documents and Data Room. Operations: Action Log, OKRs, Financial Review and Leadership Team.
Growth: Campaigns, Clients, Engagements, Product Backlog, Pipeline, Fundraising, Competitive Intel and Customer Reviews. Account: Integrations.