GAF Runtime Boundary Guard
Goal
Ensure automations do not depend on gaf-core-knowledge at runtime.
Use This Skill When
- Reviewing runtime code before validation/deploy.
- Refactoring task implementation or shared clients.
- User asks to check architecture boundary compliance.
Boundary Rules
- Build time may read core-knowledge docs for planning and implementation.
- Runtime code must use env vars, manifests, and runtime resources only.
- No direct runtime file reads from
gaf-core-knowledge.
Checks
- Search task runtime and shared client code for file path references to
gaf-core-knowledge. - Identify implicit coupling (hardcoded schema docs, registry file reads, template reads).
- Propose replacements using runtime config or manifest fields.
Output
CompliantorNon-compliant.- list of boundary violations with file paths and fixes.
- residual risk notes for ambiguous cases.
Guardrails
- Prefer minimal, explicit config changes over broad rewrites.
- Escalate unclear cases instead of assuming allowed runtime access.