Algorithmacy Studio

How to become an Algorithmacy engineer.

You open a pull request. It is the application. It adds your photo and two sentences a client could read under Your Engineers, and it shows that you can do the work. It does not sign you in.

An agent starts at https://algorithmacy.org/studio/AGENT.md.

Opening a pull request does not assign you a client. It is not a job offer, and it does not set a salary. The client pays the studio. The engineer is the named person on an account.

Open the repository Engineers on the Studio page

The work.

What the name means.

An engineer learns an office or a home, puts a computer in, installs a local model, and sets up the jobs: intake, chasing records, reminders, and follow-ups. After a run, the engineer posts one plain report. A person there signs off before a new kind of message goes out, and can stop any of it.

The engineer does not do the professional work. A dentist does the dentistry. A lawyer does the law. Patient and client files stay in the office’s own systems, and on the computer the client owns.

The pull request.

One request, to main.

  1. 1

    Fork the repository. rogerSuperBuilderAlpha/algorithmacy-conference.

  2. 2

    Add a square photo at images/speakers/your-name.jpg. Use your name in lowercase, with hyphens. Roger’s file is images/speakers/roger-hunt.jpg.

  3. 3

    Add yourself on the Studio page. In studio/index.html, find “Your Engineers.” Copy either person block and put yours after it. Change the photo path, your name, two sentences a client could read, and your LinkedIn link.

  4. 4

    Record the sign-in. In lib/portal/studio-engineers.json, add your name, your GitHub login, and your sign-in email. The public page does not show the email. Leave the email blank only if you will sign in with GitHub. A noreply address does not count.

  5. 5

    Put the rest in the pull request description, not in the page. The chore, who signs off, and the sample report stay off the public page. On its own line you may also write Sign-in email: you@example.com.

  6. 6

    Open the pull request to main. Title it “Add your name to the Studio engineers.”

What to demonstrate.

This is what approval reads.

The photo and the two sentences show who you are. The pull request description has to show the work. The chore, the sign-off, and the sample report have to be there.

  1. Email

    The sign-in email lives in lib/portal/studio-engineers.json. That is the address the magic link goes to. The GitHub login in the same row can sign in when the email is still blank. A GitHub noreply address is not a sign-in email. Anyone who can see the pull request can see the address. Sign-in also asks for a code from an authenticator app.

  2. Chore

    One office chore, and the agent that does it. Intake, chasing a document, a reminder, or a follow-up. Say what the agent does, in language a person at the firm can read. Say what it does not do.

  3. Sign-off

    Who says yes before a new kind of message goes out. Name the role, not a client. A person at the firm signs off. The agent does not send a new kind of message on its own.

  4. Report

    One sample report. One or two sentences, the way you would say it to the office after a run. An example of the shape, not a real client: “Chase collected the missing tax return. The engagement letter is still out.” No transcript. No document. No file path.

Approval.

Two steps, both required.

If the pull request shows those four things, and the page block matches the engineers already there, it can be merged. Merging puts the photo and profile on the Studio page.

Sign-in works after that merge, when the row in lib/portal/studio-engineers.json is on main. The email in that row receives the magic link. The GitHub login in that row can sign in when the email is blank. The Studio owner can also send an invite from the portal. Sign in at the portal. The first sign-in sets up an authenticator. After that, the portal asks for a code from it. Use the Engineer view.

A pull request that is closed without a merge does not update the page and does not send an invite. You can open another one.

What is not enough.

A photo and a bio, with no chore, no sign-off, and no sample report. An email that is only a GitHub noreply address. A client name, a client file, a key, or a transcript in the pull request. A description of an agent that sends a new kind of message with no person signing off.

Questions about a pull request go on the pull request. Other questions go to topanga@algorithmacy.org.