Make the repository adoptable by anyone deploying Able - #31
Merged
Conversation
Able's tree was already tenant-neutral, but nothing told a stranger how to run it, and nothing told an agent which of the two jobs in this repository it was doing. An adopter's agent reading AGENTS.md found only upstream maintenance rules, which are actively misleading when the whole task is to configure one specific business. Add docs/adopt.md as the adopter entry point: prerequisites, fork-with- upstream rather than a template snapshot, the tenant boundary as an explicit table, the three customization levels, the deployment steps only a human can complete, and the upgrade path. Declare a private context slot. AGENTS.local.md is git-ignored and holds a deployment's standing context; AGENTS.local.example.md is the committed template. AGENTS.md now branches upstream work from deployment work and reads that file first when it exists. The public-readiness scan rejects any published *.local.md and requires both new documents, so the boundary is enforced rather than merely described. Narrow the blanket .claude/ ignore to local session state so committed agent assets ship to adopters, and add the deploy-able skill, which drives docs/deployment.md in order and stops at every human gate — including the decision to enable public intake. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Able's tree was already tenant-neutral, but nothing told a stranger how to run it, and nothing told an agent which of the two jobs in this repository it was doing. An adopter's agent reading
AGENTS.mdfound only upstream maintenance rules, which are actively misleading when the whole task is to configure one specific business.docs/adopt.md— the adopter entry point: prerequisites, fork-with-upstream rather than a template snapshot, a localdev:paritytrial, the tenant boundary as an explicit table, the three customization levels, the deployment steps only a human can complete, and the upgrade path.AGENTS.local.example.md— committed template for the git-ignoredAGENTS.local.md, the declared slot for a deployment's standing context.AGENTS.mdnow branches upstream work from deployment work and reads that file first when it exists.npm run scan:publicrejects any published*.local.mdand requires both new documents..gitignorenarrows the blanket.claude/rule to local session state so committed agent assets ship to adopters, and adds thedeploy-ableskill, which drivesdocs/deployment.mdin order and stops at every human gate — including the decision to enable public intake.Documentation and tooling only; no runtime behavior changes.
npm run checkpasses on the rebased tree (278 tests).🤖 Generated with Claude Code