agentleFS
hushh-labshushh-labs/hushh-research/.agents/skills/backend-runtime-governance/SKILL.md

backend-runtime-governance

Skill40 starsChanged 4 days agoApache-2.0View on GitHub

Use when changing backend route placement, service boundaries, runtime ownership, or backend docs/tests alignment.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 1 is distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Avoid overlap with backend-api-contracts and backend-agents-operons.

    line 12
  2. Distinctive:

    Keep backend tests and backend docs aligned with runtime changes.

    line 56
  3. Very specific:

    Treat consent validation, trust, and audit rules as security-audit concerns when they become the primary boundary.

    line 58
  4. Very specific:

    Treat uv as the canonical Python toolchain for contributor and CI flows.

    line 59
  5. Very specific:

    When a backend runtime failure is visible in UAT or CI, use ./bin/hushh agents rca --surface runtime --text or --surface uat --text first …

    line 61
  6. Very specific:

    If the request is still broad or ambiguous, route it back to backend.

    line 66
  7. Very specific:

    If the task is primarily a proxy/backend wire contract, use backend-api-contracts.

    line 67
  8. Very specific:

    If the task is primarily about agents or operons, use backend-agents-operons.

    line 68
  9. Very specific:

    If the task becomes trust/IAM/vault policy work, route to security-audit.

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hussh Backend Runtime Governance Skill

Purpose and Trigger

  • Primary scope: backend-runtime-governance
  • Trigger on backend route placement, service boundaries, runtime ownership, and backend runtime docs/tests alignment.
  • Avoid overlap with backend-api-contracts and backend-agents-operons.

Coverage and Ownership

  • Role: spoke
  • Owner family: backend

Owned repo surfaces:

  1. consent-protocol/api
  2. consent-protocol/hushh_mcp/services
  3. consent-protocol/hushh_mcp/integrations
  4. consent-protocol/tests/services

Non-owned surfaces:

  1. backend
  2. security-audit
  3. repo-operations

Do Use

  1. Route and service placement decisions inside the backend runtime.
  2. Runtime ownership boundaries between routes, services, and integrations.
  3. Aligning backend runtime docs and service-layer tests with implementation changes.
  4. Reviewing runtime DB table ownership, data-class posture, retention policy, and access paths when backend migrations or services add durable state.

Do Not Use

  1. Broad backend intake where the correct spoke is still unclear.
  2. Agent/operon orchestration work.
  3. Proxy contract work that primarily belongs to API contracts.

Read First

  1. docs/architecture/system.md
  2. docs/development/contracts/api-contracts.md
  3. consent-protocol/docs/README.md
  4. .agents/skills/backend-runtime-governance/references/async-runtime-performance.md
  5. docs/architecture/schema-migration-discipline.md

Workflow

  1. Confirm the runtime boundary before moving code between routes, services, or integrations.
  2. Keep backend tests and backend docs aligned with runtime changes.
  3. For any migration or durable service table, confirm the runtime DB data-plane contract declares owner, data class, primary access path, expected row growth, retention policy, deletion behavior, and plaintext/ciphertext posture.
  4. Treat consent validation, trust, and audit rules as security-audit concerns when they become the primary boundary.
  5. Treat uv as the canonical Python toolchain for contributor and CI flows; requirements*.txt are generated runtime artifacts, not the source of dependency truth.
  6. For backend bootstrap, packaging, or runtime-governance changes, rerun the authoritative service checks once directly and once again through the canonical repo entrypoint.
  7. When a backend runtime failure is visible in UAT or CI, use ./bin/hushh agents rca --surface runtime --text or --surface uat --text first so service fixes are anchored to the blocking runtime classification instead of log-chasing.
  8. For slow or intermittently "unreachable" endpoints, run the async runtime performance health check before editing: confirm whether the asyncio event loop is blocked by a synchronous call (DB client, external SDK) rather than a slow DB, then apply the run_in_threadpool/asyncio.to_thread offload and the layered caching strategy in references/async-runtime-performance.md. Never call the synchronous db/db_client.py client or a blocking SDK directly from an async def handler.

Handoff Rules

  1. If the request is still broad or ambiguous, route it back to backend.
  2. If the task is primarily a proxy/backend wire contract, use backend-api-contracts.
  3. If the task is primarily about agents or operons, use backend-agents-operons.
  4. If the task becomes trust/IAM/vault policy work, route to security-audit.

Required Checks

cd consent-protocol && python3 -m pytest tests/services -q
./bin/hushh agents data-model-audit

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.