WiseNxt Doctrine

Purpose and Scope

This Doctrine governs the Climb — the opt-in path by which a community member becomes an operator. It is an overlay on the Commons Doctrine (every climber is a community member; most members never climb), and it hands off at the top to the Workplace Doctrine (funded work) and the Constitution’s Partner door. The Constitution fixes the boundaries — that the Climb exists and is opt-in, that the operator ladders and four Gate 2s exist and who owns them, the genesis seed, and that Enclave Bootcamp (the theory → the Learner Permit) is the Climb’s prerequisite.

The entry sequence runs across three separate documents, none of which is this Doctrine, each a different domain’s course: Welcome to Opplet Commons (the community intake at Gate 1, Commons domain), Enclave Bootcamp (the theory that grants the Learner Permit, Enclave domain), and WiseNxt Orientation (the Climb’s opt-in on-ramp, WiseNxt domain). This Doctrine describes the methodology of the Climb proper; the WiseNxt SOP holds the tunable mechanics and names the tooling.

The Climb develops; it does not filter. Its job is to grow capability and sort by aptitude, not to cull. No one is rejected — only “not yet.” The only scarce things are the Range and the operator seats, and those are rationed, not refused (§2, §4).

1. The Climb at a Glance

A member clears Welcome to Opplet Commons (Gate 1) to become a community member of the Volunteer Commons. A member who completes Enclave Bootcamp earns the Opplet Learner Permit — a certified-member credential. Per Constitution §11.3 the Permit grants (a) read-only Range review of the free community forge, (b) the Opplet-thematic courses, and (c) the WiseNxt Orientation, and it gates certified-member participation such as the Developer-space vote (Commons Doctrine §7). Holding the Permit is a complete standing in itself: many Permit-holders join the spaces and never climb, and that is a valid place to stop.

A Permit-holder who wishes to climb opts in through the WiseNxt Orientation (§2) — the Climb’s on-ramp — by producing and nominating work, which discovers their functional aptitude (§3). On clearing the Climb they cross one of four Gate 2s (§5) into operating a zone, taking up an L2 seat of that zone’s operator ladder (§4) and receiving the Operator License (§5). They rise by handling exceptions well — advancing by certification and by claiming open seats across the lattice (§4).

At the top sit two doors that are not rungs — the bounty door (funded work, the Workplace domain) and the Partner door (fork your own). The whole Climb lives in the Volunteer Commons: it confers role and access, never real-identity or pay (§8). Crossing into funded work is a separate event.

The Climb’s infrastructure is WiseNxt’s, on the Range. The forge (exemplar work and curation records), the CI, the tracker, and the practice forks are the Climb’s, on the Range (Zone 5), not the Lounge’s. The Climb’s durable datasets — forge repositories, tracker, curation records — carry a backup exception (Constitution §5A, §9), so Gate 2 can read them and they survive the Outpost’s volatility; only the practice forks are ephemeral, rebuilt from templates. Tooling is named in the SOP.

2. The Climb’s Path

The Climb begins at the WiseNxt Orientation — the opt-in, climb-only learning activity that follows the Permit. It teaches how the Climb runs and, as its capstone, invites the participant to propose a concrete improvement to Opplet or the Commons. That proposal is the participant’s first exemplar; a higher-ranked operator reviews it (recruitment is the upper ladder’s duty — §4). From there the Climb is the work-discovery driving practice, ordered cheap-first so the expensive steps are the only ones rationed:

Exemplars. Produce visible, specialty-flavored work in the open — and the work is concrete: an improvement to Opplet or the Commons, which the Climb then equips the participant to make real. The first exemplar comes from the Orientation proposal; further exemplars arrive through several doors, all producing the same kind of output and converging on one ranking spine:
- the Orientation proposal, reviewed by a senior operator;
- periodic hackathons, judged by established best practice;
- the demand-driven vacancy — an open need posted to the community and answered with produced work (§4, Vacancies).
Peer comparison. Curation by people already doing the work (weighted; the upper ladder’s standing duty — §4) plus the Developer-space vote (supporting, certified-member-gated — Commons Doctrine §7) ranks the work against peers’. A participant who does not place keeps producing for the next cohort — the wait develops them.
The Range lease. Top-ranked current work earns an ephemeral, auto-provisioned practice fork on the range, theirs for the lease, then recycled. The first rationed step.
The deploy. In the sealed fork, stand up and run the whole mini-Opplet — safe because nothing there bleeds out. Machine-graded across the four faces (WiseNxt SOP). This is mastering Opplet — breadth at fork-operating depth — and where the aptitude the exemplars hinted is confirmed.

Mastery here means competently running the whole small instance — breadth across all four faces — not deep expertise in any one. Depth comes after, in the zone you enter.

3. The Four Specialties

The four work-focus specialties are cross-cutting — a description of what you work on, discovered in the Climb and carried into whatever zone you operate. Every zone-team needs all four.

Specialty	Community work (forge, BookStack-Beta)	Operator / funded work
Engineering	Guides, tutorials, public merge requests	Audit repos, source-of-truth docs, run infra exceptions
Logistics	Resource indices, event coordination, process docs	Logistics workflows and operational coordination
Finance	Community budget summaries, ledger explainers	Finance records (and, as funded Workplace work, confidential finance and donor relations)
Marketing	Community copy, public messaging	Source-of-truth marketing content for the public sites

The pattern is one line: same kind of work, higher-trust environment, after demonstrated competence. Community work earns the operator gates; aptitude is read from what a participant actually ships, not what they claim.

4. The Operator Ladder — Certification, Seating, and the Lattice

Each working zone is run by a four-rung operator ladder, an exception-escalation ladder (Pillar 3 — the machine governs routine, the human governs the exception). Each rung is defined by the class of exception it is trusted to resolve:

L1 — user / community member. No exceptions; the machine runs the lifecycle. (This rung is plain membership.)
L2 — power user. The routine human exceptions; the entry rung at Gate 2.
L3 — admin. Exceptions needing authority.
L4 — sysadmin. The deepest non-root exceptions; owns the zone’s Gate 2.

Certification is uncapped; seating is vacancy-gated. Passing the machine-graded bar for a level certifies the participant for it — automatic by default, with the zone’s senior operators handling the exceptions in the ladder’s own running (borderline calls, disputes). Certification is a capability statement, not a status: nothing is appended to a callsign, there is no rank prefix, and it confers no pay. Certification is not the same as holding a seat. Operating a zone at a given level is capacity-bounded; a certified participant takes up a level only by claiming an open seat announced as a vacancy (Vacancies, below). One may be certified for L3 and wait for an L3 seat — the wait is productive, never a rejection.

The ladder is a lattice, not four silos. A certified operator advances by claiming an open seat in their own track or another. Because the deploy grades all four faces (§2), every operator has demonstrated baseline competence across Engineering, Logistics, Finance, and Marketing, so lateral movement is well-founded. A cross-track move lands by default at the new track’s entry rung (L2), bounded by demonstrated competence and the open seat, and requires a curation for the new zone — which adds a zone endorsement to the operator’s license (§5) — but no re-deploy, since breadth was proven once.

Recruitment is the upper ladder’s standing duty. Among the exceptions a senior operator handles is growing the next operators. The L3/L4 operators curate and review incoming exemplars — Orientation proposals, hackathon entries, vacancy responses — vouch for reviewed work, and own their zone’s Gate 2 (§5). Recruitment is therefore not a separate office but a duty of the upper rungs, which is also what makes the curation signal obtainable: a member’s work is reviewed by someone whose role includes reviewing it. At genesis, before a zone holds its own seniors, the Custodian seeds the first operators (§6); once a zone holds its own L3/L4, recruitment passes to them, as Gate 2 ownership does.

Vacancies. An open position is a vacancy, of two kinds surfaced to two audiences:

Advancement vacancies — open operator seats (the next level in a track, or a lateral seat in another). Their audience is climbers and operators, who see them in the tracker, beside the cohort queue. Read-visible to all climbers, claim-gated to the certified.
Entry vacancies — open needs posted to seed exemplar work (the demand-driven door, §2). Their audience is members who have not yet climbed and who live only in the community spaces, so entry vacancies are broadcast to a dedicated community space for potential climbers, reaching people who are not yet in the tracker.

The tracker is the single source of truth for all vacancies; the community broadcast is a surfacing of the entry kind. (Tooling and surfacing mechanics: SOP.)

5. The Four Gate 2s and the Operator License

Crossing from member to operator happens at one of four Gate 2s — one per working zone — each owned by that zone’s own L3/L4 operators. The crossing draws on:

The Learner Permit + the machine-graded deploy — objective proof of competence.
The endorsement signal — project-member curation (the necessary signal, the upper ladder’s duty; recorded durably) plus the certified-member Developer-space vote (supporting, not by itself sufficient).
The zone operators’ admission — they review and admit. The machine proves you can; the operators confirm fit and readiness.

On admission, the operator takes up an L2 seat within LDAP-Beta (no directory change — the Climb is all Beta), same callsign throughout.

The Operator License. Admission grants the Operator License — the permit→license spine completed: the Learner Permit is the learner’s permit, the Climb is the driving practice, and Gate 2 is the road test passed. It is one license carried under the callsign, with a per-zone endorsement added each time the holder clears a zone’s Gate 2 — the first Gate 2 grants the license and its first endorsement; a cross-track move adds a further endorsement via the new-zone curation, no re-deploy (§4). The L-levels are a separate axis (the certifications — which class of exception); the seat is the position held. The Lounge Gate 2 makes a member CNMCyber staff (Commons Doctrine §5).

6. The Genesis Seed

Because a zone has no senior operators to own its Gate 2 — or to recruit and curate — until its first ones exist, at enclave genesis the Custodian seeds each zone’s initial operators by root provision, bounded to Gate-1 alumni (Internal Sourcing is absolute, Constitution §12). The first cohort is certified by the machine (the Learner Permit + deploy), not vouched for by operators who do not yet exist. Seeding is a one-time bootstrap; once a zone holds its own L3/L4, its Gate 2 and its recruitment duty (§4) pass to them.

7. Identity Across the Climb

A participant’s callsign is permanent and unchanged through the entire Climb; only access and role change. Their forge work, BookStack-Beta drafts, curation records, the Learner Permit, the Operator License and its endorsements, and operator record all attach to one callsign-identified identity. If they later cross into funded work, they dual-hold — the callsign stays in the commons, a real-identity is added in the Workplace, the link private (Constitution §3, §12; Commons Doctrine §2).

8. The Top of the Climb

The Climb’s default summit is being a trusted volunteer operator (up to L4 of a zone, in one track or across the lattice), and a participant may stay there for life. Two doors open beside it, neither a rung:

The bounty door → funded, confidential work as a real-identity worker. Awarded by the Tech Board where confidentiality requires it; governed by the Workplace Doctrine. Taking it is taking a contract, not earning a rank.
The Partner door → fork the public blueprints and run your own sovereign instance (Constitution §11.7, §14). The Range deploy you mastered is its miniature rehearsal.

WiseNxt opens the path to these doors; it does not govern them.

Changelog

v4.4 (2026-06-16) — Reconcile to Constitution v12.8

Enclave Bootcamp (was “Opplet Boot Camp”) is the Enclave domain’s theory course and the Climb’s prerequisite (Purpose, §1); the entry sequence is the three domain courses — Welcome to Opplet Commons (Commons), Enclave Bootcamp (Enclave), WiseNxt Orientation (WiseNxt).
CNMCyber → Commons as a domain (Commons Doctrine references); KenyaX → Workplace as a domain (the bounty door, §1, §8); real-name → real-identity; “improvement to CNMCyber” → “to the Commons.”
The Permit’s §11.3 grants recorded (§1). CNMCyber stays the team/brand (“CNMCyber staff,” §5).

v4.3 (2026-06-15) — The Operator License; forge stays on the Range; PROVISIONAL lifted

The Operator License named (§5); §1 forge/CI/tracker/forks on the Range with the durable-dataset backup exception; domain homes settled; PROVISIONAL lifted. (v4.4 re-homes the theory course to the Enclave domain and renames the CNMCyber/KenyaX domains.)

END OF DOCUMENT