◇ COLLABORATEAID :: WELCOME

// CALL FOR HANDS

One person can’t build this. Tell us where you can help.

This site, HelmKit, the intake/signing pipeline, the doctrine pages, the analysis briefs — all of it currently runs through one operator with a five-to-fifteen-hour weekly budget. That ceiling is the single biggest constraint on the mission. If you have a skill below and two hours a week, that materially changes the slope of what’s possible.

Compensation: where revenue exists, work is paid at sane rates against the 1:1 services pipeline. Where revenue doesn’t exist yet, work is credited, attributable, and ships in public repos under your own name. Nothing is owed, nothing is locked in, you can walk at any time.

// ROLES (CURRENT)

  • Engineering

    TypeScript · Next.js · web crypto · edge functions · self-hostable.

    // SKILLS WE NEED

    • TypeScript / Next.js (this site, and HelmKit)
    • Web Crypto API · JWS signing · key management
    • Edge / serverless functions on a free tier
    • Static-first thinking; we treat servers as optional

    // WHAT YOU’D ACTUALLY DO THIS QUARTER

    Help finish the intake-signing edge function, the /brief/[id] verification surface, and the HelmKit prototype. Public repos. Public commits.

  • OSINT / Analysis

    Pattern work · open sources · careful claims.

    // SKILLS WE NEED

    • Open-source intelligence methodology
    • Disinformation / timeline-tampering literacy
    • Writing assessments where uncertainty is a first-class field
    • Comfort flagging your own bias inside reports

    // WHAT YOU’D ACTUALLY DO THIS QUARTER

    Co-author the standing analysis brief: what is actually being tampered with right now, sourced and dated. Sets the surface read that Stage 01 service uses.

  • Design

    Type · HUD · cartography · stillness over flourish.

    // SKILLS WE NEED

    • UI design that respects bandwidth (this is not a marketing site)
    • Brand mark refinement (we have a Wing Commander placeholder)
    • Sigil generation system for Resonant Briefs
    • Cartography / chart design for timestream visuals

    // WHAT YOU’D ACTUALLY DO THIS QUARTER

    Replace the placeholder Wing Commander emblem with the real animated version. Design the Resonant Brief PDF template. Help calibrate doctrine pages so they read serious, not weird.

  • Writing / Editing

    Plain language. Mythic when earned, never before.

    // SKILLS WE NEED

    • Strong editorial hand for technical-and-spiritual material
    • Ability to ground weird claims in concrete consequence
    • Comfort with the FUNCTION vs NOT-CLAIM pattern
    • Bonus: experience with mental-health-safe language

    // WHAT YOU’D ACTUALLY DO THIS QUARTER

    Edit the doctrine pages (/timestream, /resonant-pipeline, /clan) so a sceptical operator can read them without dismissing the whole project.

  • OPSEC / Trust & Safety

    Crisis routing · consent architecture · adversarial thinking.

    // SKILLS WE NEED

    • Trust-and-safety experience, especially for small-team services
    • Familiarity with crisis-line routing protocols
    • Adversarial review: how would this be weaponized, by whom
    • Privacy-engineering instincts; we store as little as possible by design

    // WHAT YOU’D ACTUALLY DO THIS QUARTER

    Red-team the intake flow, the wellness gate, the crisis page. Pressure-test the consent doctrine. Find the failure modes before a real visitor does.

  • Fabrication

    When physical gear actually ships.

    // SKILLS WE NEED

    • Hardware prototyping (HelmKit form factor, future printed credentials)
    • Small-batch fabrication and BOM thinking
    • Open-source hardware practice (KiCad, public BOMs)

    // WHAT YOU’D ACTUALLY DO THIS QUARTER

    Not active yet. Listed honestly because it will be needed when HelmKit moves past prototype. Express interest now if this is your lane.

// HOW TO REACH

Send a short message. We’ll reply.

Pick the channel that fits the kind of work you do. If you write code, the HelmKit repository on GitHub is the fastest path — open an issue, file a PR, or just lurk. For everything else, use /connect with topic=collaborate:<role-id> so we can route it.

We don’t maintain a Slack or a Discord. Async written work via email and GitHub is the protocol. The fewer channels we run, the more attention stays on the work.