Documentation  /  The vision — iCore · iQuorum · iCorp

HiNet — Sovereign Intelligence: iCore · iQuorum · iCorp

Status: Canonical vision (v1) — the source of truth for the org/human sovereignty model. The Whitepaper narrates the science of composition; this document defines where the membranes are drawn, who owns what, and how it pays — and is the source the whitepaper, Functional Spec, Technical Spec, and the mind.quorumz.com landing propagate from.

1. Thesis

Enable any organization, company, or individual to build its own intelligence from its own know-how — and to use it internally or sell it externally — without surrendering that intelligence to a central platform.

We decentralize intelligence to the atom (the human) while respecting the membranes of the real business world: inside a company people share and compound intelligence freely; that intelligence is not freely aggregated outside the company without the company being paid back. The unit of sovereignty is the human; the unit of commerce is the organization.

2. Primitives

• iCore — one human's sovereign, owned AI: a local model continually personalized on that human's approved data. iCore == 1 human. Always human-owned, always portable.
• iQuorum (pl. iQuorumz) — a consenting assembly of iCores that answers as a group. Can be ad-hoc (auto-selected for a question) or predefined (a named group, for @-mentioning).
• iCorp — a rigid, org-gated iQuorum that presents to the outside world as a single business-unit identity. Externally it does not expose its member iCores individually; it answers as itself (the company). Internally it is a workspace of iCores + iQuorumz.
• Membrane — the boundary that defines where a quorum draws its edge. Membranes are org- or gov-gated: they decide what compounds inside and what may cross out (and on what terms). The membrane is what lets decentralized intelligence coexist with corporate/state confidentiality.

3. Human-first sovereignty + the lease

The iCore belongs to the human, permanently. Employment is modeled as a lease, not a transfer:

• If a human works at an iCorp (e.g. full-time) and consents, their iCore is leased to that iCorp for the duration of employment.
• While leased, the iCore contributes to the iCorp's own intelligence model (its sovereign corporate intelligence).
• When the human leaves, the iCore travels with them (portable, still theirs) — but the intelligence it contributed remains inside the iCorp's model. The company keeps what was built on its premises; the human keeps their atom and moves on.

This is the core reconciliation: atomic human-first sovereignty underneath, corporate borders respected on top. (This is why portability/export is foundational — see §8.)

4. Two audiences, three views

Public netizen (regular user). Sees: - Free iCores — iCores not bound to any solid iQuorum/iCorp. - iCorps — as single identities (business units). Their internal iCores are not exposed.

iCorp member (business user). Sees the company workspace — internally, all the iCorp's iCores and its internal iQuorumz.

So the product differentiates a public user from a business user: a public user builds on their own iCore, which participates in the public network; a business user operates inside their iCorp workspace.

5. Asking & answering

A question can be directed three ways: 1. A specific iCore (ask one human's intelligence). 2. A definite set of iCores — a predefined iQuorum used for mentioning. 3. Open — just ask; the mechanism selects the most suitable quorum to answer.

Public network. An answer is attributed to the iCores / iQuorumz / iCorps that produced it, and pay-per-usage flows to those contributors (see §7). iCorps may answer publicly, but then they answer as the iCorp identity — the internal iCores are neither referenced individually nor paid directly; the iCorp is the unit that is credited and paid.

6. "Slack for AI" — the UX shape

Like Slack, but the objects are iCores and iQuorumz, not channels. An iCorp is a workspace. - By default there are no channels/groups — you either ask a specific iCore, ask a defined group of iCores, or ask openly and let the mechanism route to the best internal quorum. - An admin can predefine internal iQuorumz (akin to Slack groups) so they can be mentioned as a unit.

User/team structure. A user signs up and can create a team (an iCorp), then assign iCores to team members. The admin assigns internal iQuorumz. Each member's participation is governed by their lease/consent (§3). Because the member set is known, iCorps get a more streamlined path to build their intelligence than the open public network does.

7. Business model

• iCorp — SaaS. Companies pay a subscription and retain their sovereign intelligence (it never leaves their membrane unless they choose to externalize it).
• Public — pay-per-usage. Everyone retains their own intelligence; askers pay per question, and that payment is split among the iCores / iQuorumz / iCorps that helped answer, with a share to the platform. iCorps that externalize earn as a unit (their internal iCores are paid via the iCorp, not directly).

8. What this implies to build

This document owns the model, not the build. For build order and the implementation surface, see HiNet-Decentralized-Network-Integration.md.

9. Relationship to the current whitepaper/specs

This is the canonical source for Whitepaper §6B (the org/membrane/lease/economy model).

Next: Fractal Intelligence (origin paper) →  ·  All documentation →