| name | this-project-only-skill |
| description | Centralized documentation of business rules, domain logic, and specific project requirements. |
| version | 1.1.0 |
Business Rules — Agentic Governance Framework
This file captures repository-specific rules for the AGF project itself. If a
new project-level rule is introduced during a session, update this file
immediately so the framework's behavior does not drift across sessions.
1. Core Logic & Domain Rules
- Portable Governance First: AGF is a framework/template repository, so governance changes must remain portable and readable before they become host-specific integrations.
- Deterministic Before Behavioral: If a security or consistency rule can be checked by script, that executable check should exist in addition to the markdown guidance.
- Shared Decisions vs Local Context: Shareable governance decisions belong in committed files under
agf/docs/; machine- or user-specific context may stay in agf-this-project.md.
- Hook Pairing Rule: New critical hooks should ship with both a policy document and a clear enforcement path (script, git hook, CI job, or host integration).
- Token Safety Rule: Context loading must stay intentionally small; only task-relevant files should be expanded into memory after cold boot.
2. KPIs & Metrics
- Cold Boot Read Set: Start with exactly the kernel, local kernel, and session handoff unless the task requires more.
- Session Handoff Size: Keep
agf/docs/session-handoff.md concise enough for reuse; target <= 80 lines and treat 120 lines as the hard cap.
- Critical Hook Coverage: Each critical governance hook should have either a runnable check or a documented integration path.
- Governance Drift Rate: Hook indexes, ADR indexes, and manifest references should stay aligned with files that actually exist on disk.
3. Technical Constraints
- Workspace Scope: Governance automation must operate only inside the current repository workspace.
- Low-Dependency Tooling: Prefer shell,
rg, and small scripts for governance automation before introducing heavier runtimes.
- Traceability Requirement: Structural governance decisions must be recorded in ADRs, not only in chat output.
- Security Hygiene: Raw logs stay local, structured logs must be redacted, and obvious secret-like strings should be treated as blockers.
- Temporary File Cleanup: Files created for testing, bug fixing, or temporary operations must be cleaned up. After they fulfill their purpose, you must explicitly ask the user for permission to delete them before removing.
Last update: 2026-04-03
"Specific rules beat generic placeholders."
