Ctrlk
Home
For the complete documentation index, see llms.txt. This page is also available as Markdown.

2. Identity and Discovery

Goal: make you (i) findable, (ii) routable into the right rooms and programs, and (iii) trusted through observable contribution—without noise.

Start here (click-to-action)

2.1 Building a High-Trust Profile (what to include; what to avoid)

2.1.1 What your profile is used for

Your profile is not a résumé. It is a routing card used to:

  • match you to groups, programs, and events

  • help other members understand your scope in 20 seconds

  • support eligibility decisions (when rooms or programs are gated)

  • establish trust (identity + precision + consistency)

2.1.2 Step-by-step: build your profile correctly (10 minutes)

  1. Log in: https://therisk.global/login/

  2. Open your Account (this is your control panel): https://therisk.global/account/

  3. From the account/profile menu, complete these fields in order (do not skip):

A) Identity (required)

  • Full name (as you want it used in the community)

  • Current title (exact and current)

  • Organization/affiliation (or Independent)

  • Country/region (jurisdiction context)

Rule: if it cannot be verified publicly, describe it conservatively.

B) Operating scope (required) Write 3–6 bullets describing what you actually do. Use verbs.

Examples:

  • “Lead operational resilience testing across enterprise technology and vendors”

  • “Design risk governance frameworks and board reporting”

  • “Build crisis finance readiness playbooks for public institutions”

  • “Run critical infrastructure continuity planning and exercises”

Avoid: generic words like “strategy” without the object (“strategy for what?”).

C) Your “here to do” statement (required) Add two short lines:

  • I’m here to contribute to: (one sentence)

  • I can support / I’m seeking: (one sentence)

This is the single most useful field for routing collaboration.

D) Expertise tags (required) Add tags (see 2.2). Choose accuracy over breadth.

E) Proof points (recommended) Add 3–5 items that establish credibility without oversharing:

  • published work (papers, standards, guidance)

  • major deployments or programs

  • measurable outcomes delivered

  • leadership roles (only if formally granted)

Keep it short. A profile with 5 clean proof points beats 40 buzzwords.

F) Availability + engagement posture (recommended) Select what you’re open to:

  • review requests

  • co-authoring

  • hosting sessions

  • joining builds/hackathons

  • mentoring

If you have constraints, state them clearly:

  • “Available for review only (not meetings)”

  • “Open to 1 collaboration thread/month”

2.1.3 Visibility and confidentiality hygiene (public-safe vs member-only)

Use this rule:

  • Public-safe: role + high-level domain, general focus, non-sensitive bio

  • Member-only: specific initiatives, operational constraints, internal context

If you’re unsure, keep it public-safe and move detail into the appropriate group room rather than the profile.

2.1.4 What to avoid (high-risk profile mistakes)

Do not include:

  • implied endorsement (“official partner”, “certified by”) unless explicitly granted

  • authority claims (“chair”, “director”, “governor”) unless formally appointed and current

  • overbroad expertise (“expert in everything”)—use lanes

  • marketing copy (this is an operating room, not a sales channel)

  • confidential information (do not paste internal documents or sensitive operational details)

2.1.5 Profile quality check (30-second test)

If a stranger reads your profile for 20 seconds, can they answer:

  • Who are you (role, institution, jurisdiction)?

  • What do you actually work on (3–6 bullets)?

  • What will you contribute here (two-line statement)?

  • How should they engage you (review/host/build/etc.)?

If yes, your profile is “high-trust.”

2.2 Expertise Tags and Domain Alignment (how tagging drives routing)

2.2.1 Why tags matter

Tags are the platform’s routing engine. They drive:

  • who finds you in the directory

  • which Q&A topics surface to you

  • which events/programs you’re recommended

  • how moderators route you into rooms

  • how people interpret your scope quickly

2.2.2 Step-by-step: choose tags correctly

Use this 3-layer method:

Layer 1 — Choose one primary lane (required) Pick the lane where you can contribute consistently for the next 30–90 days.

Examples:

  • Financial risk & resilience

  • Technology risk & assurance

  • Health systems risk

  • Public risk & emergency systems

  • Policy, governance, and standards

Layer 2 — Add 2–5 functional tags (recommended) Add skills/activities that describe what you do:

  • stress testing

  • scenario design

  • incident response

  • resilience engineering

  • standards drafting

  • evidence validation

  • audit readiness

  • critical infrastructure continuity

Layer 3 — Add 0–3 sector tags (optional) Only add if it’s truly your operating domain:

  • banking, insurance, asset management, utilities, telecom, transport, public sector, etc.

2.2.3 Use platform taxonomy (so your language matches the system)

Before finalizing tags, check the community’s live vocabulary:

Instruction: choose tags that already exist where possible (reduces fragmentation).

2.2.4 Domain alignment (how to pick your “home” room)

Your “home” is where you will:

  • join 1–2 groups

  • attend events

  • answer Q&A

  • contribute to programs

Start here:

2.3 Member Directory — Find People Fast (filters, search patterns)

Directory = fastest way to find the right human. https://therisk.global/members/

2.3.1 How to search (repeatable patterns)

Use one of these methods:

A) Search by institution type Try:

  • central bank / regulator / ministry / DFI / MDB

  • insurer / reinsurer / broker

  • exchange / market infrastructure

  • utility / telecom / transport / critical infrastructure

  • university / lab / research institute

B) Search by role keyword Try:

  • CRO, CISO, CTO, CIO

  • risk, resilience, continuity, crisis, incident

  • policy, standards, assurance, audit

C) Search by problem statement (best for matching) Try:

  • outage, cyber, liquidity, stress test, claims, verification, evidence

2.3.2 What to do after you find someone (the correct workflow)

  • Open their profile and read scope + engagement posture.

  • Decide the correct lane:

    • Need a quick pointer or invite? Message them (see 2.5)

    • Need collaborative work? Move to a group thread (DM → group)

    • Need a reusable answer? Ask in Q&A (see 2.4)

If you’re starting a new initiative, create a group thread in an existing group first: https://therisk.global/groups/

2.3.3 “Three-person rule” for efficient discovery

If you’re stuck, find:

  • 1 operator (hands-on builder)

  • 1 governance/standards person

  • 1 domain specialist

Then route the work into a group and a Q&A entry so it becomes reusable.

2.4 Following, Subscriptions, and Feeds (how to personalize your workspace)

2.4.1 Your objective: signal, not volume

A clean feed = you show up consistently, respond quickly, and don’t miss important items.

2.4.2 What to follow (recommended order)

2.4.3 Best-practice subscription posture (first month)

  • Week 1: 2 groups, 3 tags, 1 event

  • Week 2: add 1 program (Quests recommended)

  • Week 3–4: add 1 additional group only if you shipped something

Control point: tune your overall posture from your account area: https://therisk.global/account/

2.5 Messaging and Introductions (best practices; boundaries)

2.5.1 When to use messaging (and when not to)

Use messaging to:

  • introduce yourself

  • request a pointer to the right room

  • invite someone into a group thread or event

  • ask for a quick review of a specific item

Do not use messaging to:

  • run long work threads

  • paste sensitive content

  • request titles, endorsements, or authority

  • do promotional outreach or recruitment

Rule: if it needs tracking, move it into:

2.5.2 The “perfect first message” template (copy/paste)

Keep it under 6 lines:

  1. Context: “I saw your work on [specific topic].”

  2. Why you: “It aligns with [group/program/event] on Nexus Platforms.”

  3. Who I am: “I’m [role] at [institution], working on [scope].”

  4. The ask: “Could you [one action] (review / point me to the right room / join a build / co-host)?”

  5. Routing: “If this belongs in a group thread, tell me which room to post in.”

  6. Thanks + signature

2.5.3 Best practice: move from DM → room

After agreement, immediately move the work:

This is how work becomes durable and reusable.

2.6 Credibility Markers (roles, participation history, recognition signals)

2.6.1 How credibility works here

Nexus Platforms credibility is evidence-based:

  • you earn trust through contribution that others can see, reuse, and validate

  • titles matter less than outputs, reviews, hosting, and accepted deliverables

2.6.2 The credibility stack (what members actually look at)

A) Profile integrity Accurate identity + scope + lanes (see 2.1)

B) Observable participation

C) Output quality Reusable briefs, checklists, templates, and structured notes (not volume posting)

D) Program acceptance signals (where enabled) Accepted work in:

E) Recognition markers (where enabled) Credits/badges/levels that reflect verified participation and accepted deliverables.

F) Registry-linked proof (where enabled) When artifacts are tied to governed records: https://therisk.global/registry/

2.6.3 Role hygiene (strict)

Only claim roles that are formally granted and time-bounded.

If unsure, state your participation lane: Contributor / Reviewer / Host / Builder / Mentor. If a role is later granted, update your profile after it is recorded.

2.6.4 Fast credibility path (one-week plan)

If you want credibility without noise:

This produces a clean participation trail and makes you easy to route into higher-value work.

Checklist (15–20 minutes)

Previous1. Accounts and SettingsNext3. Community Norms

Last updated

Was this helpful?