Docs: name the force function (uniform mechanism, local voice) - #16
Open
daveh-beep wants to merge 1 commit into
Open
Docs: name the force function (uniform mechanism, local voice)#16daveh-beep wants to merge 1 commit into
daveh-beep wants to merge 1 commit into
Conversation
chalkline already ships the mechanism that makes approved language bind (consult-before-writing, must>should precedence, exact-wording blocks, provenance, calibration-as-regression-check). What the docs never state is the thesis that reconciles "align language" with "not one-size-fits-all": the force function is the consult contract, which a whole organization can share, while the content — voice, terms, channel rules — stays local and sovereign to each team. Add FORCE_FUNCTION.md stating that distinction and, as importantly, the things chalkline refuses to become at enterprise scale (a shipped voice, a mandated agent, a central authority, speculative multi-brand/eval machinery). Cross-links README and OPERABILITY.md rather than repeating their content; adds one README line so the doc is discoverable. Docs only. No change to setup/PROTOCOL.md or the AGENTS.md frontmatter contract. Signed-off-by: David Hamilton <daveh@squareup.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.
What this changes
Adds
FORCE_FUNCTION.md— a short positioning page — and one README line pointing to it. Docs only. No change tosetup/PROTOCOL.mdor theAGENTS.mdfrontmatter contract, so this is the single-maintainer review path.Why
The repo already ships the mechanism that makes approved language bind (consult-before-writing,
must>shouldprecedence, Exact wording blocks, provenance footers, calibration-as-regression-check) and, since #12/#14, explains how to operate it (OPERABILITY.md). What's never stated is the thesis that reconciles "align language across an organization" with "not a one-size-fits-all agentic plan":At enterprise scale that distinction is the product. This page names it, and — as importantly — names what chalkline refuses to become: a shipped voice, a mandated agent/runtime, a central authority over teams, or speculative multi-brand/eval machinery (the last deferred to field evidence, consistent with CONTRIBUTING).
Scope discipline
README.mdandOPERABILITY.mdrather than repeating their content.AGENTS.mdconsult order/precedence/on-brand rule; Exact wording;OPERABILITY.md"does not yet define … precedence across overlapping repositories").What setup experience this improves
It gives an evaluator deciding whether to adopt chalkline org-wide the one-page answer to "is this going to mandate how my teams write?" — no. It aligns how language binds, not what you say.