Workplace Doctrine

Purpose and Scope

The methodology of the Real-Identity Workplace — who works under a real name and why, what gets funded and on what principle, and how a proven volunteer crosses into accountable, contracted work. This is tier 1 (principle); the step-by-step mechanics are the Workplace SOP’s.

This Doctrine operates under, and never overrides, the Constitution. It governs the inside of the real-identity workplace. It does not govern:

the boundary itself — that work entering privacy, security, or contract must be real-identity is fixed by the Constitution (§15E), not here;
the climb — the Climb and the operator ladders are the WiseNxt domain;
community life — the volunteer commons is the Commons domain;
the substrate — nodes, network, and identity systems are the Enclave domain.

1. The Real-Identity Principle

A callsign proves skill; it cannot bear legal accountability. The whole reason this workplace exists apart from the commons is that some work enters a legal field, where a person must be able to answer in law under their own name. Three fields draw that line (Constitution §15E):

Privacy — handling confidential or personal information.
Security — operating security-sensitive systems.
Contract — performing under a binding contract.

Work that enters any of these belongs to the Real-Identity Workplace (LDAP-Alpha). It may not be done under a callsign. The crossing into Alpha is therefore a deliberate de-pseudonymization for accountability — not a reward, not a rank, not an automatic promotion. This Doctrine’s job is to operate that requirement faithfully; it has no power to waive it.

2. Funded Work and Compensation

This is the material that moved out of the Constitution under the v12.1 Real-Name Anchor Amendment (the triggers are now the real-identity triggers, Constitution §15E, v12.8). The Constitution kept the requirement; the money lives here.

Real-identity is not the same as paid. Real-identity is about who can stand behind the work in law. Funding is about whether the Economic Group pays for it. The two ran together in the old model and are now separate: a thing is real-identity because of the legal field it enters, and separately funded because the Tech Board decides to fund it (Constitution §16).

What gets funded. The Tech Board allocates the funds. Examples of funded work include:

Work on a commercial product — something the operation sells or monetizes.
Confidential or security work run as a standing operation or contracted deliverable, rather than donated effort.

🔶 TBD (commercial trigger). Under v12.1, “commercial” is a funding trigger here, not a real-identity trigger in the Constitution. If you want commercial-product work to be constitutionally real-identity on its own (even absent privacy/security/contract), that belongs back in Constitution §15E and I’ll move it. As written: commercial → funded (here); privacy / security / contract → real-identity (Constitution).

🔶 TBD (rates). This Doctrine sets the principle that funded work is administered through the Workplace and disbursed under the SOP. It does not set rates or bands of pay amount — that is the Tech Board’s, within the Economic Group’s envelope (SOP §4).

Payment requires a real name. A person can be paid only under a real, contracted identity. So all funded work is real-identity (Alpha) work — there is no funded callsign. Note the direction of the logic, because it is the reverse of the old model: the legal field makes work real-identity; pay then attaches to that real-identity work because pay cannot attach to anything else. Funding is a consequence of the boundary, not the boundary.

The bands. Work sorts as follows (relocated and reframed from old Constitution §15E):

Band	Funded?	Identity	Basis
Public, non-sensitive	No — volunteer	Pseudonymous (Beta)	Nothing sold, nothing private, nothing under contract
Commercial product	Yes — Tech Board funds	Real-identity (Alpha)	Sold or monetized work
Confidential / security operation or contract	Yes — Tech Board funds	Real-identity (Alpha)	Real-identity required by the Constitution; funded as a standing or contracted operation
Root / personal	Not delegable	Out-of-band	The sovereign’s own (Custodian)

The bounded judgment (mirrors Constitution §16). The Tech Board decides funding, not identity. It may not reclassify work that genuinely enters privacy, security, or contract as pseudonymous to dodge the real-identity requirement. The real-identity requirement is the Constitution’s (mandatory); the funding decision is the Board’s (discretionary).

3. Internal Sourcing and the Trust Judgment

The workplace is drawn only from proven volunteers of the commons (Constitution §12, Internal Sourcing — Absolute). There is no external hiring into Alpha; no outsider applies or is recommended.

This is why the workplace is human-recruited rather than machine-run. Skill is graded by the machine in the commons. Trust with confidential things cannot be graded by a machine — it is a human judgment, made here, about a person whose public work is already known. The commons answers can they?; the Workplace answers can we trust them with this?

4. Dual-hold and De-pseudonymization

A worker keeps their callsign. Crossing to Alpha adds an accountable, real-identity beside the pseudonymous one; it does not erase it (Constitution §3, §12). The commons continues to see only the callsign.

The link between the two identities is private — held by the contract administrator alone, never exposed to the commons. De-pseudonymization is scoped to the confidentiality the work warrants: vetted to the degree the work requires, no further. It is an accountable handshake, not a public unmasking.

The Custodian is the standing proof of this pattern: a callsign in the commons, a sovereign role above it, the link disclosed at discretion.

5. The Two Contract Types

Funded work takes one of two forms. The principle is here; the workflow is SOP §1.

Project contract — a one-time deliverable (commercial or confidential). Scoped and recommended by the operation or zone that needs it; the Tech Board reviews and awards. No open posting.
Operation contract — the term-based running of a standing system (a confidential operation or a commercial product). The Tech Board defines the role and opens an internal posting to the proven-volunteer pool; it screens, selects, and awards.

Both end in a Tech Board award, and the award is the crossing into the workplace.

6. The Custodian Partnership

The standing option for a proven participant to fork the public blueprints and run their own sovereign instance (Constitution §11.7, §14 — the Deploy/Fork door). It is not a rung of the climb and not a contract within the Workplace; it is an exit into peerhood.

On partnership, any internal contract is closed and internal Alpha access is revoked; the relationship becomes external and peer-to-peer, with a B2B interface in place of internal access. The participant’s commons callsign is retained throughout. Entering a partnership is an ownership-level decision of the Economic Group, because it concerns who holds root over a derived instance.

Model first-draft; terms reserved. The interface, the terms, and any ongoing obligations are TBD (mechanics in SOP §7).

7. Authority and Place in the Charter

The Workplace is the Economic Group’s real-identity operational arm (Constitution §15D), operated by the KenyaX team (kenyax.com is one of its public fronts). It sits inside the governed structure, holding nothing of the structure itself:

It takes its funding direction from the Tech Board (Constitution §16) and disburses within the Economic Group’s envelope.
It draws its people from the commons (the Commons domain) and the climb (WiseNxt), by recruitment only.
It runs on Enclave infrastructure — records in ERPNext in the Office (Alpha) — at the application layer, with no root and no Basement access (SOP §5).
It holds no operator level and no constitutional authority.

Changes to Workplace mechanics are SOP edits under Custodian approval. Changes that cross the infrastructure boundary — the two-world line, the identity structure, the real-identity triggers — require a companion Constitutional amendment (Constitution §13B).

Changelog

v1.2 (2026-06-16) — Reconcile to Constitution v12.8

Domain is the Workplace; KenyaX is the team/brand. “KenyaX domain / Doctrine / SOP” → Workplace domain / Doctrine / SOP throughout; §7 reframed so the Workplace is the domain and the KenyaX team operates it (kenyax.com a front), mirroring Constitution §15D.
“Real-name” → “real-identity” as the label (the Real-Identity Workplace; §1 the Real-Identity Principle; the bands table). The literal “under their own name / a real name” is kept where it means the act.
“Foundation” → “the Climb” (Purpose); CNMCyber → Commons (§7); “paired amendment” → “companion amendment” (§7, matching Constitution §13B).

v1.1 (2026-06-13) — Real-Name Anchor alignment

Aligned to Constitution v12.1; reframed from “the paid workforce” to the real-name workforce; received the relocated §15E pay content (§2); restated the privacy/security/contract triggers; two TBDs carried (§2). (v1.2 renames the domain to the Workplace and the label to real-identity, per Constitution v12.8.)

v1.0 (2026-06-12) — Initial (lost)

Original Two Worlds release. Not in hand; v1.1 superseded it. Reconcile against any surviving fragments, especially §6 (Custodian Partnership), which the SOP cross-references.

END OF DOCUMENT