grtninja Repo C Boundary Governance
Use this skill to keep architecture and governance constraints intact.
Workflow
- Read
BOUNDARIES.mdandAGENTS.mdbefore coding. - Confirm changes stay in trust-layer lane (policy, scoring, telemetry libraries).
- Reject coupling to hardware-execution internals from shim/DDC repos.
- Run lint/tests and document governance impact in PR notes.
Scope Boundary
Use this skill for architecture/governance boundary checks across docs, contracts, and cross-repo interfaces.
Do not use this skill for:
- Policy file/schema validation execution lanes.
- NDJSON trace packet validation mechanics.
- Ranking engine scoring/report contract implementation details.
Quick Governance Checks
rg -n "BOUNDARIES.md|REPO_B_SIDECAR_URL|Windows-SDK|fail-closed|trust-layer" -S README.md AGENTS.md docs src repo-c repo_c_trace ranking_engine
ruff check .
pytest -q
Output Requirements
- Explicit statement of boundary-safe scope.
- Updated docs when contracts/interfaces shift.
- No new prohibited phrasing or dependency coupling.
Reference
references/boundary-checks.md
Loopback
If this lane is unresolved, blocked, or ambiguous:
- Capture current evidence and failure context.
- Route back through
$skill-hubfor chain recalculation. - Resume only after the updated chain returns a deterministic next step.