Community · Cells
Nexus Competence Cells
Institutionally hosted, mission-bounded expert units. They localise and operate risk capabilities, keep a record of everything they do, and incubate new work with partner institutions.
Research and learning
- Research competence cell A hosted team of researchers on one question, publishing methods, models and open datasets.
- Joining
- By request
- Decides by
- Consent (sociocratic objection rounds)
- Members
- 3 or more
- Academy cohort and lab cell Hosts an Academy cohort or lab, with learning records that show progress.
- Joining
- Open
- Decides by
- Simple majority
- Members
- 3 or more
Data and engineering
- Observation and data competence cell Runs monitoring and curates open observation data for its place and hazards.
- Joining
- By request
- Decides by
- Consent (sociocratic objection rounds)
- Members
- 3 or more
- Systems and digital twin competence cell Builds and operates open tools and digital twins for the hosted programme.
- Joining
- By request
- Decides by
- Advice process
- Members
- 3 or more
Preparedness and people
- Early warning and anticipatory action cell Turns forecasts and observations into protocols and triggers with local partners.
- Joining
- By request
- Decides by
- Advice process
- Members
- 4 or more
- Community emergency response team (CERT) Neighbourhood or campus preparedness and first response, hosted by an institution.
- Joining
- By request
- Decides by
- Advice process
- Members
- 5 or more
- University-based competence cell A campus team hosted by a university, combining study, research and volunteering.
- Joining
- By request
- Decides by
- Simple majority
- Members
- 5 or more
Sector forums
Standards
Review and assurance
Policy and finance
- Risk policy cell Prepares evidence briefs and consultations for public authorities, labelled as advice.
- Joining
- By request
- Decides by
- Consensus with fallback
- Members
- 3 or more
- Risk finance readiness cell Designs and tests parametric triggers and prepares readiness evidence. No money moves.
- Joining
- By request
- Decides by
- Supermajority
- Members
- 3 or more
How a cell forms
- DraftVisible to its members only, while the core areas are completed.
- ActiveListed in public, open to join as the cell has set.
- ClosedIts mission is complete; its records stay readable.
Core
- Mission and scope. The purpose, place, scale and timeframe are filled in.
- Members and roles. The type's minimum roles are held, including a safeguarding contact where one is required.
- Governance. A decision rule is adopted by a founding decision, with a record anyone can verify.
- Agreements. The charter and membership agreement are signed by the minimum members, and the data and licence choices are made.
Substantial
- Work programme. At least one project and three issues, or one open call.
- Workflows. The intake and decision routes are set.
- Services. At least one shared service is connected.
- Competences and learning. The competences sought are listed, and a learning path is set for each role.
Finish
- Public page. A cover, a logo, an about text and the outputs section are in place.
- First activity. A first decision, post or output is on the record.
Ways to join
- Open
- Anyone signed in can join.
- By request
- People ask to join with their relevant expertise and a short motivation; the cell's admins approve or decline.
- By invitation
- Only people the cell invites can join.
What every cell keeps to
- One engine per job: governance, matters, issues, credentials, competence and contributions stay in their own plugins; this contract only names them.
- Nothing is priced and no money moves; credits are recognition only.
- Learning and review records show progress and proof of review; they never certify.
- Members under 18 are protected: never listed in public, never in response roles, always with an adult safeguarding contact.
- Public counts under 5 are suppressed.
- Every type is interdisciplinary: it names the expertise areas and disciplines it draws on, and anyone may ask to join.
- A network may add types that extend a base type; a network type may override label, summary, defaults and starter set, never the boundary or the minors rule.