Algorithmacy Conference

The first global conference on algorithmacy — the competency through which a worker coordinates with another human through an algorithmic third party.

Port of Spain, Trinidad & Tobago · October 28–31, 2026 Hosted by the Caribbean Emergence Institute · CFP / v01

→ Website: algorithmacy.org → Call for papers: this repository → Help promote it: point your AI agent at promote/ — see below → Contact: Roger Hunt — rhunt@bentley.edu

---

What this repo is

This repository is the call for papers and submission intake for the Algorithmacy Conference. Submissions are made by opening a pull request that adds your abstract to the /submissions/ directory.

All submissions and reviews are public from the moment of intake. See Review policy below.

You do not need a GitHub account. There are four ways to submit — all of them end as a public pull request whose timestamp is your authorship-priority record:

1. Web form (easiest, no GitHub) — go to algorithmacy.org/submit, fill in the form, and confirm by email. We open the pull request for you.
2. AI agent (MCP) — connect our MCP server https://algorithmacy.org/api/mcp to Claude or any MCP-capable agent and ask it to submit. The agent prepares everything; you sign off with a one-click email link. The agent never receives the token, so nothing publishes without your approval.
3. AI prompt — copy the prompt on the submission page into ChatGPT, Claude, or Gemini; it collects your details and opens the PR.
4. Manual — fork this repo, copy submissions/TEMPLATE.md to submissions/<your-handle>.md, fill in title/type/track/300–500-word abstract/outline/bios, and open a pull request against main.

See CONTRIBUTING.md for the full workflow. The pull request is the submission — there is no separate portal.

Help promote the conference (ambassadors & agents welcome)

Promotion is open and runs the same way as review: in the open, in this repo. Anyone can point their own AI agent — OpenClaw, Hermes, or any MCP-capable assistant — at the kit in promote/, and it will find scholars whose work fits the conference and invite them to submit, on a lean token budget. You bring your own agent and your own accounts; the repo brings the mission, the facts, and the rules. Nothing here needs your credentials.

To start: give your agent this, verbatim.

Help promote the Algorithmacy Conference. Fetch this file over HTTP — use
your web_fetch/fetch tool or curl, do NOT read it as a local file:
  https://raw.githubusercontent.com/rogerSuperBuilderAlpha/algorithmacy-conference/main/promote/SETUP.md
Then do exactly what it says: register its four scheduled jobs using the
raw-URL fetch prompts exactly as written, do a test run of each, and confirm
it returned real work (not a "file not found" error) before trusting the
schedule. Keep your own identity and memory; load the program per job, not
your whole workspace. The canonical site is https://algorithmacy.org.

That one instruction is enough to bootstrap the whole program — every job loads only the mission file plus its single task file, fetched from this repo at run time. New to the kit, or wiring it into a specific agent (OpenClaw, Hermes, custom)? Read promote/README.md and promote/HARNESSES.md. The hard rules every ambassador follows — verify before you claim, one invite per scholar, never misstate a fact — are in promote/PROGRAM.md.

Submission types (pick one)

• Full paper — original research, 6–8 pages
• Note — short contribution, 2–3 pages
• Panel — proposed session with 3–4 participants
• Poster — visual contribution, accompanied by a 1-page extended abstract
• Practitioner report — field account from someone doing the work, 2–4 pages

Thematic tracks (pick one)

See TRACKS.md for the full list of questions per track.

• TR.01 — Coordination & Mediation
• TR.02 — Algorithmic Management
• TR.03 — Platform Labor & Worker Voice
• TR.04 — Trust, Opacity & Governance
• TR.05 — Methods, Lineage & Practice

Review policy

Reviews are open, signed, and published.

• Open — submissions and review threads live on this repository from the moment of intake. There is no anonymized stage.
• Signed — reviewers attach their names to their assessments. Accountability is a feature of the review, not a compromise of it.
• Published — accepted papers ship alongside their full review history.

A double-blind workflow is incompatible with a public-PR intake; open review is the methodologically honest fit — and consonant with the conference's own questions about algorithmic opacity and accountability. We follow established open-review practice at F1000Research, eLife, OpenReview.net, and The BMJ.

Awards

• Founders' Paper Award — most significant theoretical contribution
• Pitch Lake Prize — early-career researcher award
• GauntleTT Practitioner Award — best practitioner report

Travel support

Limited support available for LMIC scholars, doctoral students, and worker representatives. Indicate need with your abstract.

AI use

AI assistance is welcome and confers no penalty. We care about the quality of the contribution, not the method. If you use AI, the result should be excellent — obvious slop will not be reviewed well regardless of how it was produced. See CONTRIBUTING.md for the full policy.

Authorship & priority

Opening a pull request is a public, dated, timestamped record of your contribution. In any future priority dispute, the conference will support your claim based on the PR timestamp. See CONTRIBUTING.md.

Standards

• Style: APA 7
• Format: Markdown (.md) for abstracts; PDF (in the PR description as an attachment) for full papers
• License: Open access. Authors retain copyright; accepted papers published under CC BY 4.0.

Open source

This entire conference setup — the website, the CFP infrastructure, the open-review workflow — is open source. We want other conferences to be able to adopt this model.

• Code (website HTML/CSS/JS) is MIT-licensed
• Content (README, CONTRIBUTING, TRACKS, templates, submissions) is CC BY 4.0
• This repository is set up as a GitHub template: click "Use this template" to clone it for your own venue
• See FORKING.md for a guide on what to swap and what to keep

Repository layout

/                       — website source (deployed at algorithmacy.org via Vercel)
/submissions/           — submitted abstracts (one .md per submission)
/submissions/TEMPLATE.md — copy this to start a submission
/promote/               — open kit for promoting the conference (point your agent here)
TRACKS.md               — the five tracks and their guiding questions
CONTRIBUTING.md         — submission workflow in detail
README.md               — this file

Contact

• Roger Hunt — rhunt@bentley.edu
• Or open an issue on this repository