The intranet that never goes stale
Most intranets hold a paragraph about a decision. This one holds the decision, so the page updates when the record does, and nobody has to remember to republish it.
A page names the record, not a copy
A goal, a decision, a project or a DecisionDoc placed on a page stores only its id. What a reader sees is resolved at the moment they open it, against their own permissions, so the page never drifts from the record and nobody republishes it by hand.
Only what was scanned and made official crosses
A page reaches the intranet in a fixed order: it must be official for that reader, it is scanned for PHI and excluded if the scan cannot clear it, and only then is it shaped down to title and blocks. The scan fails closed, not open.
Each workspace runs its own
Granting access, publishing a page, and ordering the menu are done by a Hub Admin inside that workspace's own hub, not by a platform operator on their behalf. Cross-tenant tooling stays, for the workspace that has locked itself out of its own.
What is actually in it
An intranet has to survive being the first thing everyone opens on a Monday before any of the governance matters.
A real intranet, not a wiki with a logo on it
The company's information architecture is a decision somebody made, not a side effect of how one person filed their notes.
- Spaces, not notebooks: a name, a URL slug, a chosen position in the navigation, and an audience
- A page is composed from blocks by its author, not assembled underneath them by the portal
- Page templates: built-in starters plus a tenant's own, so a governance decision about what an announcement looks like lives on the platform, not in a frontend bundle
- Scheduled publish and expiry evaluated at read time, so a page cannot go stale behind a scheduler that silently never fired
- A home page an author composes from blocks, not four fixed widgets stacked in a fixed order
Blocks that carry a record, not a snapshot
Fourteen ordinary content types, and a second family that points at something alive instead of writing prose about it.
- A metric block reads a KPI's current figure, resolved per reader, the same way it would in DecisionSheets
- A goal, decision, project or DecisionDoc can be published to the intranet and placed as a block, each gated and resolved the same way a metric is
- A DecisionCapture form answered on the page itself, never copied onto it: what a reader sees, and whether they already answered, is decided when they open it
- The news roll-up and the staff directory are blocks an author places, not fixed furniture below whatever they wrote
- An org chart block, built from the same directory the staff directory reads, so a tenant's own disclosure settings apply to both
What a reader can prove they saw
A policy nobody can prove was read is a policy, not evidence. This is built for the second one.
- Read receipts naming the exact revision read, so a rewrite does not inherit the old reading
- Read-and-acknowledge, with an attestation that expires the moment the page it attests to changes
- Search runs over the same rows the projection already produced, so it can never surface a page a reader could not open
- Coverage that separates current, outdated and never read, rather than one number that quietly means all three
- An acknowledgement requirement becomes an owned task in DecisionTasks, so it shows up where the person already works
Administered by the people who use it
The platform used to be the only way to run a hub. A workspace now runs its own.
- Grant and revoke portal access without a platform operator in the loop
- Publish a page to a department, to one person, or to everyone, with the audience spelled out and confirmed before the write
- Order the menu and place a metric, straight from the hub
- Every save travels the same write-through path the platform's own editor uses, so there is one copy of a page and one place it is governed from
- Analytics for who read what and who still owes an attestation, named per page and never per person
A home page that points at the work
A block on a DecisionHub page is a window onto a live record, in four modules at once.
DecisionTasks
An acknowledgement requirement lands as an owned task, where the obligation already lives.
Decisions
A decision block shows its current status, not the status on the day the page was written.
Projects and goals
A project's status or a goal's progress on the front page, current for every reader.
DecisionDocs
An official document surfaces as a card and opens where it actually lives.
An intranet that fails closed, not open
An employee's identity is verified from their own signed sign-in token, not asserted by the intranet client. A page is scanned for PHI before it can publish, and is excluded if the scan cannot clear it. Every save still lands in the same governed storage the platform's own editor writes to, so there is exactly one copy of a page and one place it answers for.