Skip to content
View mephistopheles4's full-sized avatar
💭
Meaningless [C]ode
💭
Meaningless [C]ode

Highlights

  • Pro

Block or report mephistopheles4

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
mephistopheles4/README.md

The Pact. Instrument of agreement No. 0004. Terms under which machines work beside me.

This agreement is made between Ayman Diab, tech lead in Montréal, hereinafter the Architect, and any agent that runs under these terms, hereinafter the Familiar.

The Architect supplies intent. The Familiar supplies labour. Both parties agree to the articles below, which are enforced by CI rather than by honour, and drawn in Schedule A.


Article I · Intent

The Architect states what and why. The Familiar proposes how. Nothing ships that a human did not intend.

Article II · Main

The Familiar shall not push to main. Every change arrives as a pull request. Force-push and deletion are forbidden, and no party, the Architect included, holds a bypass.

Article III · Gates

No pull request merges until the gates check passes: install, tests, build, and the editorial rules. A green gate is the only signature the branch accepts.

Article IV · Provenance

Every third-party action is pinned to a commit SHA. A tag can be moved after it is signed; a hash cannot.

Article V · The Grimoire

The Familiar may draw on the spells in grimoire. It shall cast them wisely.

Article VI · Consideration

In return, the Architect provides a clear brief, a working test suite, and forgiveness for the first draft.


Schedule A · The drawing

Engineering drawing MEPH-0004, 'Humans as architects of intent', drawn by A. Diab in Montréal and checked by CI. It shows how a change reaches main: intent, then agent, pull request, gates, main. A red dashed line from agent straight to main is crossed out as forbidden.

Schedule B · Works

Item Work Description
1 the-pact The terms themselves: the moves, tiers, lenses and guards every agent works under. Installs as CLAUDE.md.
2 grimoire A spellbook of agent skills. The one balloon 4 refers to.
3 stacks Local-first reading tracker. Obsidian vault in, 3D bookshelf out. MIT.
4 athanor Your tests, sealed. Each run in a fresh Linux container, for many agent sessions on one machine. On npm. MIT.
5 aymandiab.com The full drawing set.

Signed: the Architect, /s/ Ayman Diab. Countersigned: the Familiar, on every commit, as Co-Authored-By.

Pinned Loading

  1. the-pact the-pact Public

    The engineering playbook: global Claude Code rules and agents

    JavaScript 1

  2. grimoire grimoire Public

    A spellbook of agent skills for AI. Cast wisely.

    JavaScript 1 1

  3. athanor athanor Public

    Run a repo's tests on your current work in a fresh Linux container, with at most N runs at once on the machine.

    TypeScript

  4. stacks stacks Public

    Got books? Got stacks! — a local-first reading tracker that turns your Obsidian vault into a 3D bookshelf.

    TypeScript