eric/policy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Simplify policy wording while preserving explicit safeguards

Browse Source
This commit is contained in:
Eric Rakestraw
2026-09-27 19:46:41 +00:00
parent ad4a20e17f
commit bf92cb1c83
11 changed files with 152 additions and 462 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/development.md
View File

@@ -9,8 +9,8 @@ Read the [agent policy](policy/agents.md) and inspect the working tree before
editing. Preserve unrelated work. Follow explicit task instructions, including
requests to leave changes uncommitted. This repository's policy files retain
their template adoption sections because they are distributed as templates.
Application-specific template examples do not require this repository to acquire
application interfaces or infrastructure.
Application-specific examples illustrate downstream adoption. This repository
maintains policy templates and reference materials.
## Policy Reading Guide
@@ -39,7 +39,7 @@ application interfaces or infrastructure.
Keep reusable instructions portable. Put adoption instructions in template
sections and project-specific contributor procedures here. Original licensing
examples belong under `examples/licensing/`; explanatory instructions belong in
their guide or policy so they are not copied into notices.
their guide or policy.
Increment the affected template's `Base Policy Version` and update its date when
changing its substantive rules or adoption instructions. Preserve the licensing
@@ -47,15 +47,12 @@ scope defined in `COPYRIGHT`; reproduced license texts must remain verbatim.
Review the diff, run `git diff --check` for changed prose, and check affected links
and examples. Example placeholders and destination-relative links should be
validated against the documented downstream layout, not treated as published
URLs or missing local dependencies. No application build or new test suite is
needed for prose-only changes. Retain upstream formatting in verbatim license
texts even where it would trigger whitespace warnings.
validated against the documented downstream layout. Diff, link, and example
review suffice for prose-only changes. Retain upstream formatting in verbatim
license texts even where it would trigger whitespace warnings.
Pin adopted-source and example links to commits that contain the referenced
files. Discovery links to the upstream project and current adoption guide may
track `main` so downstream agents can find updates. New assets can use local
links within this repository until a containing commit is available; do not
invent a future hash or publish changes merely to obtain one.
Before publication, confirm that public reference links are accessible. This is
change validation, not a recurring downstream release gate.
track `main` so downstream agents can find updates. Use local links for new
assets until a containing commit is available. Pin public reference links to existing commits and confirm
their accessibility when preparing publication of the reference changes.