# 0. Introduction
Nexus Platforms is the member workspace for the Nexus ecosystem on **therisk.global**—a network of governed hubs and work rooms where leaders connect, publish, learn, and contribute to real outputs without needing prior context.
**Your operating arc on the platform**\
Join → Orient → Participate → Produce → Verify → Progress
**What you can do in practice**
* Establish a trusted professional presence (profile, expertise tags, contribution record)
* Find peers and join domain hubs and working groups
* Publish updates and structured briefs
* Ask/answer questions in the Q\&A knowledge hub
* Participate in events (webinars, workshops, office hours) and work programs (quests, bounties, builds, hackathons)
* Track participation markers and eligibility signals via the Registry layer (where enabled)
**Key links (start here)**
* **Login:**
* **Your Account (profile + settings hub):**
* **Membership (tiers and pathways):**
* **Groups (work rooms):**
* **Events (calendar):**
* **Q\&A (knowledge hub):**
* **Knowledge Base / Wiki (how-to library):**
* **Registry (status & portfolios where enabled):**
***
### 0.2 Community Membership — What it includes (capabilities, boundaries, expectations)
#### Included capabilities (what you can do)
**A) Identity & discovery**
* Create and maintain a member profile (role, organization, scope, expertise tags)
* Discover members and communities through directories and domain pages
* Follow relevant hubs/streams to personalize your feed
**B) Community participation**
* Join Groups (work rooms) and participate in threads and collaboration lanes\
* Engage through comments and structured discussions (high-signal, task-oriented)
**C) Publishing (self-publishing tools)**
* Publish Posts (short updates, signals, requests, progress notes)
* Publish Articles/Briefs (long-form structured insights, proposals, draft notes)
* Share events, announcements, and participation updates through the appropriate lane
**D) Q\&A knowledge hub**
* Ask questions and receive structured answers\
* Use **“Ask question”** for new topics (best for reusable how-to guidance)\
(then click **Ask question**)
**E) Events & cadence**
* Register for and attend events (webinars, workshops/clinics, office hours)
* Use event pages as the source of truth (agenda, resources, follow-ups)
*
*
*
* Event submission/management (where enabled):
**F) Work programs**\
Join participation programs that convert effort into outputs and recognition:
* Quests (structured tasks with defined outputs)
* Bounties (deliverable-based challenges with acceptance criteria)
* Builds (team sprints producing reusable artifacts)
* Hackathons (time-boxed builds with tracks and submissions)
Links:
* **Hackathons hub:**
* **Bounties hub (where enabled):**
**G) Progression & recognition (where enabled)**
* Participation markers (credits/badges/levels) and eligibility signals for advanced lanes
* Registry-linked participation record (where enabled)\
**H) Generate tools (platform-native)**\
Create structured drafts and intelligence artifacts using built-in “Generate” workflows:
* Guided forms → structured artifacts (briefs, checklists, submissions)
* Bots/assist tools (where enabled in your rooms)
* Repeatable templates to reduce friction and improve quality\
(Access appears inside eligible rooms and tool panels; visibility depends on your permissions.)
#### Boundaries (what you must follow)
**Use the right lane (keeps the platform high-signal)**
* Q\&A for questions/how-to
* Groups for collaboration and delivery
* Events for scheduled work and attendance
* Forms for structured intake/requests
* Journals/Wiki/KB for reusable documentation and published guidance
**Integrity + handling**
* No misrepresentation: do not claim roles, endorsements, titles, or authority you do not hold.
* Respect visibility: keep sensitive material in the correct rooms; do not post restricted content into public-safe areas.
* Be output-oriented: post with purpose, scope, and a clear “next action” request.
***
### 0.3 Platform Map — Where to do what (routing guide)
**Posts (short updates)**\
Use for: quick signals, introductions, lightweight coordination, simple asks.\
Avoid for: long proposals, dense documentation, issues that need structured resolution.
**Articles / Briefs (long-form)**\
Use for: structured insights, proposals, field notes, draft documents, summaries.\
Best practice: include **Scope → Proposal → What you need** (review/collaborators/decision).
**Groups (work rooms)**\
Use for: collaboration, working threads, program delivery, sprint coordination.\
Directory:
**Nexus Q\&A (knowledge hub)**\
Use for: “how do I…?” questions, troubleshooting, repeatable guidance.\
Hub:
**Events (calendar + cadence)**\
Use for: webinars, workshops, office hours, hackathons, recurring sessions.
* Calendar:
* List view:
* Dashboard:
* Submit/manage (where enabled):
**Forms (structured intake)**\
Use for: applications, nominations, submissions, formal requests, reports.\
Rule: if routing/approval/tracking matters, use the structured path provided in your room or program page.
**Quests / Bounties / Builds / Hackathons (work programs)**\
Use when there is an output + acceptance criteria + a deadline.
* Hackathons:
* Bounties hub (where enabled):
***
### 0.4 Nexus Network Map
Think of Nexus Platforms as a network of hubs, each with a distinct job:
**Domain Hubs (Future-of platforms)**\
Your primary “home” communities by domain (each includes groups, publishing streams, and events).
Example domain hubs:
* Health:
* Society:
* Space:
**Groups (Work Rooms)** — where collaboration and delivery happens day-to-day\
**Q\&A** — the reusable knowledge layer\
**Knowledge Base / Wiki (KB)** — the documentation and how-to library\
**Events layer** — schedules, attendance, resources, follow-ups\
**Registry layer (where enabled)** — status, participation record, portfolios\
Operationally, most members work inside **Domain Hub(s) + Groups + Q\&A + Events**, with outputs later promoted into **KB/Journals/Campaigns** when applicable.
***
### 0.5 First 15 Minutes Quickstart (7-step checklist)
Complete these in order (10–15 minutes total):
1. Log in:
2. Open your Account hub and complete profile basics:
3. Choose your domain home (start with 1–2): e.g.,
4. Join 1–3 Groups (one home group + one working group):
5. Post a short introduction (who you are • what you work on • what you will contribute)
6. Register for one event (orientation / office hours / webinar):
7. Ask or answer one Q\&A (fastest way to learn and contribute):
***
### 0.6 Your First Week Plan (Day 1 / Day 3 / Day 7 milestones)
#### Day 1 — Activate
* Complete profile + tags (Account):
* Join Groups:
* Register for an Event:
**Outcome:** you’re visible, correctly routed, and subscribed to the right rooms.
#### Day 3 — Make one real contribution
Choose one:
* Answer a Q\&A in your domain:
* Publish a short post: “one insight + one question + one ask”
* Join a work program (quest/bounty/build/hackathon) where enabled
* Hackathons:
* Bounties:
**Outcome:** your first contribution is recorded and you understand the rhythm.
#### Day 7 — Choose your lane (next 30 days)
* Contributor: publish briefs/templates/field notes
* Reviewer: provide structured feedback and improve drafts
* Host: run office hours/webinars/workshops
* Builder: join builds/hackathons and ship artifacts
* Mentor: support onboarding and routing new members
**Outcome:** you adopt a pathway where your work compounds.
***
### 0.7 Getting Help (Decision tree: Q\&A vs Support Form vs Moderator)
**Use Q\&A when**
* It’s a “how do I…?” or “where do I…?” question
* The answer should be reusable for others\
Q\&A:
**Use the Knowledge Base when**
* You want official guidance, playbooks, and how-to pages\
KB/Wiki:
**Use a structured intake (Form) when**
* Access, permissions, eligibility checks, or formal submissions are required\
(Use the form link provided inside your relevant room/program page.)
**Contact a Moderator when**
* Integrity issues: misrepresentation, harassment, spam, confidentiality/handling violations\
(Use the escalation path provided in your room; if in doubt, post a short “routing request” in Q\&A.)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.therisk.global/organization/operations/platforms/0.-introduction.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.