KeizAI

KeizAI The social dynamics

Trust that keeps its context.

A producer's real answer to "who should shoot this?" contains a name, a reason, and a qualifier they would never say in a room with the candidate in it. The qualifier is what makes a referral a referral rather than a directory lookup — and it is exactly what every public-reputation product destroys, because a judgement made visible to its subject stops being honest and becomes diplomatic. KeizAI's social design exists to keep that judgement where its author put it.

Peers, not sides

There is no employer side and no worker side.

A freelancer hires a studio; the studio hires a freelancer; both directions are equally normal, recursively. Buyer and seller schemas hard-code asymmetry into tables, permissions and interfaces, and cannot represent a chain four levels deep — so KeizAI's model has one Actor abstraction for person and company, and commerce is an engagement with a direction, not a role type. Nothing in the schema privileges one side.

The same discipline applies to language. The specification maintains a list of words the product refuses, because each one smuggles in a model of people the product rejects.

Refused
"Match score" — the system does not choose people
Refused
"Talent pool" — people are not browsable inventory
Refused
"Rating" / stars — quality is not a leaderboard
Refused
"Verified ✓" — KeizAI vouches for no one; provenance names who does
Refused
"Hire" as an automated verb — hiring is a human act
Standing behind someone

A nomination says how far you will stand behind it.

When a person puts a candidate forward, they choose the weight of their own name behind the act — from "I know them; you should talk" to "I remain accountable for delivery". The upper levels are not decoration: a delivery responsibility creates an accountability link, and the parent role cannot complete while the work it stands behind is unfinished.

A nomination is always a person's act — an AI agent can propose a candidate, but can never nominate. Once made, its author, its level and its statement are immutable; a change of mind is a visible withdrawal and a new nomination, not an edit. And when a nominee declines, the reason is a closed set — available to the nominator without ever leaking a private judgement.

The nominee is a peer in the act too: they may accept, counter, or offer to fill an entire branch and bring their own people or company.

Introduction — "I know them; you should talk"
Role recommendation — "appropriate for this role"
Preferred collaborator — "I want them in my branch"
Sourcing and supervision — "I will manage or review their work"
Delivery responsibility — "I remain accountable for delivery"
How constellations grow

A chain is not a special structure.

Person sources company sources person is just the ordinary composition of role, decision and engagement, repeated at each level. Each engagement in the chain stays an independent bilateral record, and nothing cascades: ending one engagement never silently ends another — it raises a decision for the person responsible above it.

A company chooses, per project, how much of itself to show: a black box that presents one price and no members — with no signal that members even exist — or named members, or a fully transparent subgraph. The same company can be opaque on one project and open on another, because disclosure is a commercial stance, not a fixed property.

Privacy as structure

Absence must be undetectable.

Privacy here is structural, not procedural — enforced by what can exist, not by what is filtered. A relationship you chose not to disclose is designed to be undetectable: no count changes, no gap appears in an ordering, no page runs short, no response is measurably slower, and no interface ever shows a "results hidden" notice. A hidden thing and a nonexistent thing look identical, in bytes and in time.

A private judgement — "don't suggest this person to me" — is unreachable rather than filtered: it feeds no search index, no projection, no export, no AI prompt, and its subject can never encounter it. Yet it never blocks anyone: a colleague may still nominate that person, no warning fires, and excluding someone from a project requires a visible, attributable veto instead. Influence is private; authority is public.

Explanations obey the same rule. A candidate's explanation may only cite facts the viewer is authorised to see; where the only evidence is a hidden relationship, the system says less or nothing — it never fabricates a collaboration, and it never says "hidden reason", which would itself disclose. Even a vague reason is a disclosure, so there is deliberately no generic "strong fit" fallback.

Two identical result lists side by side, four rows each, same length and spacing. In the right-hand list one relationship is hidden — and nothing marks the difference: the lists are indistinguishable. Nothing hidden One edge hidden Same count · same order · same timing · same bytes
The specification's test is statistical: the hidden case and the plain case must be indistinguishable to a measuring adversary, not merely to a polite one.
No universal score

Nobody is a number, and this is marked "never revisit".

KeizAI computes no global reputation for anyone. There is no field named score, rating, rank or match in the domain model, and where every other design trade-off carries a measured trigger for revisiting, this one's trigger reads: never. A global number collapses contextual taste into a gameable metric and turns private judgement into published claims about people.

Instead, trust stays typed, owned and scoped: who asserted what about whom, for which kind of work, visible exactly as far as its author chose. The default for every human-authored judgement is private to its author. Sharing it with its subject is always permitted and encouraged; making it public requires the subject's own revocable consent, because publishing a claim about a person is publication.

The design is honest about limits: narrowing visibility stops future disclosure but recalls nothing already seen, the record of who worked together survives archiving — because the graph, not the coordination, is the durable asset — and trusted circles can reproduce bias, which the charter names as a risk to govern, not a problem it pretends to have solved.

L0
Private to me The default for every human judgement
L1
This project Follows the project, not the employer
L2
My organisation Shared with colleagues, still owned by its author
L3
Shared with the person Always permitted — telling someone what you said cannot harm them
L4
Public Only with the subject's revocable consent; no unauthenticated public graph exists

KeizAI is in an early specification phase. This page describes the social design recorded in the project's charter, invariants and privacy governance documents — design intent, not shipped software.