meta-founding-contract
Skill1 starsChanged 45 days agoNo licenceView on GitHub
The project's own statement of what it is — internal, behind the scenes, never about the product's audience — held as an original text that is never rewritten plus dated amendments saying where the project has progressed to. Every contract opens with a two-sentence BEARING in service of it. Correcting a bearing is a reevaluation (the direction is off in some respect), not a redraw (an adjustment within a direction already correct). An amendment must name what caused it and what it now binds; one that only ratifies work already done is retro-fitting, and retro-fitting turns the statement into a check that cannot fail at the top of the practice. Amending is a pioneer act. The content is unmeasurable and reached by reflection; only the form is enforceable.
In this repository17 other files it gives its agents.
- meta-antidrift-expandSkill
- meta-antidriftSkill
- meta-bootstrapSkill
- meta-casebookSkill
- meta-contract-artifactSkill
- meta-contract-before-executionSkill
- meta-correction-logSkill
- meta-drift-eventlogSkill
- meta-extractSkill
- meta-foundationSkill
- meta-learningSkill
- meta-ledgerSkill
- meta-manifestSkill
- meta-mapSkill
- meta-mechanismsSkill
- meta-skill-builderSkill
- meta-understandingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.