Build the future of child-centered, trauma-informed practice.

Who it's for#

This is interdisciplinary by design. The hardest problems here live between fields, and we want teams that mirror that. You belong here if you're studying — or interning in —

Project tracks#

Every track maps to real platform data — the same roles, workflows, scenarios, and artifacts the CLI exposes. Pick one, form an interdisciplinary team, and build something usable.

Browse the full surface anytime — 18 roles, 5 workflows, 9 scenarios, 12 safety modules, and 134 artifacts — on the Catalog page or with cotrackpro catalog.

Start in 5 minutes#

Everything is offline and unauthenticated until you choose to sign in — explore the whole catalog with zero setup.

npm install -g @cotrackpro/cli   # or: npx @cotrackpro/cli <command>

# 1. Explore the problem space (no account needed)
cotrackpro catalog                       # counts across the whole platform
cotrackpro catalog roles                 # all 18 roles
cotrackpro artifacts search school       # find artifacts by keyword

# 2. Sign in when you're ready to build
cotrackpro setup                         # guided browser sign-in
cotrackpro whoami                        # your identity, org, role, permissions

# 3. Scaffold your project, SDK + auth already wired
cotrackpro scaffold school-incident-tool

From there, build with the typed @cotrackpro/sdk and — when your tool needs gated platform data — mint a short-lived, scoped token instead of holding credentials (see Gated access).

Contribute safely#

Student contributions flow through the same proposer model every developer and agent uses, so you can ship real changes without anyone weakening the platform's trust boundary:

1. Fork → branch → pull request. No direct pushes to main; nothing self-merges.
2. CI has your back. Every PR runs npm run typecheck, npm test, and the npm run codegen:check drift gate — generated code must come from codegen, never hand-edits.
3. Sensitive paths get human review. Auth, credentials, and signing live behind protected paths: you can propose changes there, but a maintainer always decides.

This means your first PR can be small and safe — fix docs, add a test, scaffold a new command — and the checks tell you the moment something's off. Start with the Contributing guide, read the full contract in docs/extensibility/agent-proposer.md, and look for good first issues to get started.

Join the global developer network#

The network lives in GitHub Discussions — open to students and interns anywhere in the world:

• Introductions — tell us your discipline, school, and what you want to build.
• Project help — get unstuck on a track, find interdisciplinary teammates.
• Show & tell — demo what you shipped.
• RFCs — propose new tracks, artifacts, and ideas.

What you get: mentorship from maintainers, merged pull requests and a real portfolio, and a community building toward the same mission. Recognition tiers (Explorer → Builder → Scholar → Maintainer) that unlock new capabilities as you contribute are coming next — for now, every introduction and every PR is the start of your track record.

Universities & faculty#

Bringing a class, clinic, or capstone cohort? The platform is built for it — interdisciplinary problems, real data, and a safe contribution path with CI guardrails so student work can't break production.

• Capstones & practicums — adopt a project track as a semester deliverable; each maps to concrete roles, workflows, and artifacts students can scope a grade around.
• Clinics & cohorts — law, social-work, and CS programs can co-supervise a single interdisciplinary team on one track.
• Course modules — the catalog (artifacts, roles, workflows, scenarios) doubles as ready-made teaching material on trauma-informed, court-neutral practice.

Faculty and program leads: open a thread in Discussions to plan a cohort, or reach out at dougdevitre@gmail.com. We'll help scope tracks to your syllabus and timeline.

Our safety & ethics commitment#

This work touches families in crisis, so it comes with non-negotiable commitments — for the people we build for, and for you as a contributor. The platform's 12 prompt-module guardrails (child-centered language, trauma-informed response, legal and therapeutic neutrality, coercive-control awareness) encode these directly.

• Educational, not advice. Everything CoTrackPro produces is informational and educational only — not legal advice, not clinical advice, and never a substitute for a licensed professional.
• Child-centered and court-neutral. Use a child's initials or a pseudonym. Describe behavior; never characterize a parent. Stay neutral — we document, we don't take sides.
• Respect data sensitivity. Artifacts are classified public, sensitive, or confidential; build for least-privilege access and never log or exfiltrate credentials.