Nexus Portal

The room behind the public doorway.

The public site explains what is being built. Nexus is where the work is being organized: branches, co-ops, projects, tasks, contributor fit, and records.

It is being built to show how the system runs before anything becomes full operations.

Purpose

Visible enough to trust.

Nexus exists so the work does not live in scattered chats, memory, or assumptions. It gives the build a place to show what is connected, what is active, what is paused, and what still needs structure.

How it runs

Branches to co-ops to projects to tasks.

Branches hold the focus areas. Co-ops hold shared effort. Projects hold planned work. Tasks break the work into pieces. Ability tags help match people to what they can carry.

What stays out

Private records are not the first layer.

Detailed household records, youth records, medical information, private messages, payout ledgers, and contracts do not belong in the public proof layer.

Access

Invitation-based while it is being shaped.

Nexus is not an open signup system today. Early access will follow branch readiness, written terms, and admin review.

Portal access

The login path is visible before access is opened widely.

Nexus uses magic-link sign in. The login page can be public, while dashboard access depends on Supabase auth, project configuration, and invitation/readiness rules.

At a glance

What this page holds.

These cards show how this public page connects to the wider build.

Public proof

Project overview

Shows projects, branches, co-ops, task counts, and contributor counts.

Task fit

Ability tags

Shows what each task needs before people are asked to carry it.

Contributor fit

Public-safe profiles

Shows rough fit without turning people into private case files.

Intake

Low-detail first

Public contact stays simple until consent, retention, and access rules are ready.