Workplace SOP

Purpose and Scope

The mechanics of the Real-Identity Workplace — recruitment, contracting, and disbursement. Tier 2 to the Workplace Doctrine’s tier 1: the Doctrine says who is real-identity and what gets funded; this SOP says how the requisition, award, and payment are run. Custodian-tunable for procedural detail; the authority above it (who awards, the threshold, the composition) is fixed in Constitution §16, and the boundary above that (the real-identity requirement) in §15E. Records live in ERPNext (the Office, Alpha) — real-identity, audited.

1. The Two Award Paths

Funded work reaches a candidate by one of two paths, matching the two contract types (Workplace Doctrine §5; Constitution §11):

Project contract (one-time deliverable, commercial or confidential). The Workplace operation needing the work — or the relevant zone’s senior operator — scopes it and recommends a qualified candidate; the Tech Board reviews and awards. No open posting.
Operation contract (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; eligible candidates apply; the board screens, selects, and awards.

Both end in a Tech Board award. Whether either path’s work is funded is the Tech Board’s determination (Constitution §16); both paths presuppose real-identity (Alpha) identity, because the work has entered a legal field — privacy, security, or contract (Constitution §15E). Internal Sourcing is absolute (Constitution §12): postings and recommendations are visible only to proven Gate-1-alumni volunteers; no outsider applies or is recommended.

2. The Recruitment Workflow (ERPNext)

Requisitions, applications, and awards are recorded in the ERPNext recruitment module (bursar.opplet.com):

Requisition. The board — or, for a project, the recommending operation — opens a requisition scoping the deliverable or term, the fee, the funding determination (whether the assignment is funded, and on what basis — a commercial product, or a confidential/security operation or contract — set by the Tech Board, Constitution §16), the real-identity basis of the work (privacy, security, or contract, Constitution §15E), and the least-privilege Alpha access the work requires.
Posting (operation contracts only). Posted internally to the proven-volunteer pool; project contracts skip this and arrive as a named recommendation.
Selection. Candidates are screened for Gate-1-alumni eligibility, fit, and trust (the human judgment the Doctrine requires, §3); the board selects.
Award. The board records the award. This is the crossing into the real-identity workplace.

3. De-pseudonymization and Dual-hold Onboarding

The crossing from a callsign volunteer to a real-identity worker happens here (Workplace Doctrine §4):

Vetting and real-identity capture. The selected candidate’s real identity is captured and vetted to the degree the confidentiality warrants; this is the de-pseudonymization the contract requires.
Contract. The confidentiality and liability terms are executed.
LDAP-Alpha provisioning. A real-identity Alpha account is provisioned with least-privilege access scoped to the contract. The participant’s Beta callsign is retained; the link between the two is recorded privately with the contract administrator and is not exposed to the commons (Constitution §3, §12).
No callsign change. The community continues to see only the callsign.

4. Disbursement

Envelope and threshold. The Economic Group sets a budget envelope and a per-award approval threshold (Constitution §16). The board allocates within the envelope.
Within threshold: the board’s to award and disburse. Above threshold: Economic Group approval before any funds move.
Payment. Recorded against the awarding contract in ERPNext finance and traceable to it: project contracts pay on delivery or milestone; operation contracts on the term schedule.

5. Records and Access

Every requisition, award, and disbursement lives in ERPNext, an Office-zone (Alpha) application; board decisions and Economic-Group threshold approvals are recorded for audit (Pillar 4). The board administers ERPNext at the application layer via LDAP-Alpha — no root, no Basement access. The infrastructure beneath remains the Custodian’s (Enclave Doctrine).

6. The Fork-Cost Target

The WiseNxt throttle is only as tight as the Range fork is expensive, so the funding side sets an economic target for the practice fork, realized by the Enclave:

Target	Initial setting	Note
Provision time	minutes, fully automated	No human in the loop
Recyclability	disposable; rebuilt from template	No backup dependency
Substrate	as light as fidelity allows	A lighter forge is acceptable where it preserves the four-face exercise
Concurrency cost	low enough that slot scarcity tracks budget, not engineering	The looser the cost, the closer to “serve everyone”

The cheaper and more disposable the fork, the more participants the Range serves per unit of compute, and the less the climb feels like a filter (WiseNxt Doctrine §2). This target is set here and realized in the Enclave Doctrine/SOP; the lease cadence itself is the WiseNxt SOP’s.

7. The Custodian Partner Procedure

Administering a Partnership (Workplace Doctrine §6; model first-draft, terms reserved):

Agreement. The Economic Group agrees to enter the partnership (an ownership-level decision).
Fork. The participant forks the public blueprints via the Deploy/Fork door (Constitution §14) and stands up their own sovereign instance, holding their own root.
Wind-down. Any internal Workplace contract is closed; internal Alpha access is revoked. The relationship becomes external, peer-to-peer.
Interface. A B2B interface replaces internal access. (Reserved — the interface, terms, and any ongoing obligations are TBD.)

The participant’s commons callsign is retained throughout.

Changelog

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

KenyaX → Workplace as the domain (Doctrine/SOP self-references, “the Workplace operation,” “internal Workplace contract”); KenyaX stays the team/brand. “real-name” → “real-identity” as the label (records, capture, basis, crossing); literal “real name / real identity” kept where it is the act.
Cross-references re-pointed to the Workplace Doctrine.

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

Aligned to Constitution v12.1 and the Doctrine v1.1; vocabulary moved from “paid workforce / paid work” to “real-name workforce / funded work”; §1 funding-vs-real-name clause; §2 step 1 split into funding determination + real-name basis. (v1.2 renames the domain to the Workplace and the label to real-identity, per Constitution v12.8.)

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

Established for the Two Worlds restructure; relocated the recruitment-and-disbursement mechanics from the monolithic SOP §10. New at v1.0: the fork-cost target (§6) and the Custodian Partner procedure (§7, first-draft).

END OF DOCUMENT