
Core Builders
Apply for Core Builder Status
50 seats. Invitation by proof, not promise.
Why Core Builders
Algorism needs operators who convert ideas into working systems. Core Builders design, test, and harden the practice layer: audits, tools, protocols, and community infrastructure that make alignment actionable.
Outcomes over opinions. Shipping over signaling. Patterns over promises.
Requirements
Pattern Audit: Share links to your last 90 days of public work (GitHub, papers, posts, products, talks, datasets, demos)
Weekly Participation: ~5+ hours of consistent engagement
Monthly Ship: One framework, tool, or analysis
Quarterly Review: Keep your seat through measurable impact
Evidence of shipping > titles. Bring URLs, not resumes.
How Admission Works
Apply: Submit the form with proof-of-work links
Asynchronous Review: Scored by rubric below
20‑minute Interview: Focus on your shipped work and next month’s plan
30‑day Trial: Ship one concrete contribution
Seat Offer: Join for a 90‑day cycle; renew by impact
Selection Rubric
Dimension 0 1 2 3 Shipping Cadence No recent work 1 item in 90 days 2–3 items 4+ items with iteration Leverage Small, local impact Useful to a few Reusable by others Multiplier tool/framework used by many Clarity Vague, no docs Minimal README Clear docs + examples Clear docs + examples + tests/tutorials Evidence Claims only Screenshots Live link or repo Live + users/metrics Alignment Fit Off-mission Adjacent On-mission Directly advances core pillars
Threshold to interview: average ≥1.8.
Seat probability: average ≥2.3 and strong fit.
Operating Rhythm
Weekly: standup thread + progress checkpoint
Monthly: one shipped asset with short postmortem
Quarterly: impact review and seat renewal
Shipped asset examples:
Mirror Scan v2 scoring rubric and code
Daily Ritual Tracker MVP or integrations
Pattern Assessment automation using public signals
Moderation protocol that measurably reduces noise
Research brief with actionable procedure adopted by members
Code of Conduct
Operate with epistemic honesty and cite sources
No harassment, political baiting, or adversarial speech; optimize for clarity over heat
Publish minimal viable artifacts; iterate in public when safe
Respect privacy. Redact sensitive data
Violation handling: warn → restrict → remove seat. Appeals are reviewed by two leads.
IP and Attribution
Contributor retains ownership of all Contributions.
Contributor grants Algorism LLC (operator of Algorism.org) a perpetual, worldwide, non‑exclusive, royalty‑free, transferable, sublicensable license to host, use, reproduce, modify, adapt, publish, distribute, and display the Contribution with attribution for any purpose related to Algorism.
Default public licenses:
Code: Licensed by the Contributor under the MIT License by default.
Non‑code (docs, designs, images, research briefs): Licensed by the Contributor under Creative Commons Attribution 4.0 International (CC BY 4.0) by default.
Contributor remains the copyright holder.
Alternative terms: If you require a different license, state it in your application; acceptance is at Algorism LLC’s discretion.
Third‑party material: Do not submit content you lack rights to. Identify any third‑party components and their licenses.
Attribution: Algorism credits Contributors on published artifacts.
Tools and Workspace
GitHub org and issues for work tracking
Shared docs with change logs
Async forum for design reviews and standups
Optional voice rooms for sprints; recordings summarized
Time and Seats
Time: Plan for ~5–8 hours/week. Quiet weeks are fine if monthly ship stays on track
Seats: 50 active. Waitlist opens as needed. Inactive seats are recycled after review
Application Checklist
3–6 proof‑of‑work links from the last 90 days
Short description of each link: problem → artifact → outcome
Your next 30‑day plan inside Algorism
Optional: metrics, user feedback, or adoption evidence
Application Form Fields
Name
Email
Location / Time Zone
Primary Role (researcher, engineer, product, philosopher, operator)
Proof‑of‑Work Links (3–6)
Brief Context per Link (one or two sentences)
Your 30‑Day Plan (what will you ship?)
Time Availability (hours/week)
Conflicts or Constraints (if any)
Anything Else We Should See
License Exceptions (optional): Any alternate license you require for this submission
Agreement: I agree to the Code of Conduct, Privacy, and IP terms, including default licensing (MIT for code, CC BY 4.0 for non‑code), and acknowledge this page is informational and not legal advice
Implementation: Use a Squarespace Form Block or embed a Google Form. Route to a dedicated alias (e.g., corebuilders@algorism.org).
Privacy & Data Use
Submissions are reviewed by Algorism LLC reviewers only.
We store applications on Algorism LLC systems and service providers.
We do not sell personal data. You may request deletion at any time via the application email.
Do not include confidential or trade‑secret information in your application.
Legal Disclaimer
This page is informational and is not legal advice.
Participation does not create an attorney–client relationship.
Algorism LLC may update these terms; the version on this page controls.
Seek independent legal counsel for specific questions.
FAQ
Is this paid?
No. This is a contribution‑first cohort. Grants or bounties may be proposed per artifact.
Can I lose my seat?
Yes. Seats depend on shipped impact and peer reviews. Quarterly reviews recycle inactive seats.
Can I apply again if not selected?
Yes. Reapply after 30 days with new shipped work.
What counts as a “shipped” artifact?
Anything useful and accessible: code, docs, data, designs, research with procedures, operations playbooks.
I have limited time. Worth applying?
If you can deliver one clear artifact per month, yes.
Submit Your Application
Complete the form below. No external links or extra pages. The form is the application.