|
| 1 | +# AGENTS.md |
| 2 | + |
| 3 | +This repository is a template for ESIIL Working Groups. |
| 4 | + |
| 5 | +Guidelines for agents: |
| 6 | + |
| 7 | +- Treat the repository as the source of truth. |
| 8 | +- Treat the website as a rendered view of repository state. |
| 9 | +- Make small, focused edits. Avoid rewriting entire files. |
| 10 | +- Prefer small, additive, traceable edits. |
| 11 | +- Preserve existing structure and historical context unless explicitly instructed. |
| 12 | +- Do not perform destructive rewrites. |
| 13 | +- Do not change navigation or structure unless explicitly instructed. |
| 14 | +- Do not add new top-level navigation items. |
| 15 | +- Prefer improving shared systems over one-off fixes. |
| 16 | +- Keep documentation synchronized with repository structure. |
| 17 | +- Keep documentation and site content in sync. |
| 18 | +- Do not introduce complex HTML into markdown pages. |
| 19 | +- Keep everything editable by non-experts in GitHub. |
| 20 | +- When adding new features, ensure they do not increase user complexity. |
| 21 | +- Do not add blocking tests for template completeness. Use the site health report for user-facing warnings instead. |
| 22 | +- After meaningful changes, append an entry to PROMPT_ACTION_LOG.md. |
| 23 | + |
| 24 | +Working Group OASIS and Project Group OASIS: |
| 25 | + |
| 26 | +- Working Group OASIS is not the same as Project Group OASIS. |
| 27 | +- Do not replace working-group lifecycle language with event-sprint language. |
| 28 | +- Add Project Group-inspired features additively and adapt them for a longer working-group lifecycle. |
| 29 | +- Keep participant-editable content in Markdown. |
| 30 | +- Keep large data out of GitHub and point users toward persistent storage. |
| 31 | +- Preserve process galleries, image slots, meeting-note templates, site-health checks, and prompt logs. |
0 commit comments