PROD Hermes Workspace
76 pages 76 clean 0 need attention
Page navigation 76

Project

Domains

Folders · apps/

Folders · docs/

Folders · knowledge/

Folders · ops/

Folders · packages/

Folders · scripts/

Folders · tests/

Folders · pods/

Folders · tools/

Shared

Metadata clean
Route
/knowledge/portal/project/folders/ops/contracts
Source
knowledge/portal/project/folders/ops/contracts.md
Covered files
0
Last generated
unknown

ops/contracts/

State: folder wiki page generated by deterministic sync

Folder: ops/contracts/

What

ops/contracts/ contains contracts implementation scope under ops. This boundary currently has 3 direct file(s) and 0 direct subfolder(s).

Does

It packages operational runbooks, scripts, and deployment artifacts for runtime stewardship (dominant direct file kinds: .json:2, .md:1).

Why

Operational clarity is required for recoverability, incident response, and safe production changes.

Subfolders

  • (no direct subfolders)

Files

  • README.md — What: ops/contracts/ contains contracts implementation scope under ops. This boundary currently has 3 direct file(s) and 0 direct subfolder(s). Does: It packages operational runbooks, scripts, and deployment artifacts for runtime stewardship (dominant direct file kinds: .json:2, .md:1). Why: Operational clarity is required for recoverability, incident response, and safe production changes.
  • hermes_role_config_template.json — What: Configuration/data artifact for hermes role config template in ops/contracts/hermes_role_config_template.json. Does: Provides structured settings or metadata read by runtime and tooling. Why: Keeps behavior deterministic by centralizing non-code control values.
  • lane_supervisor_process_template.json — What: Configuration/data artifact for lane supervisor process template in ops/contracts/lane_supervisor_process_template.json. Does: Provides structured settings or metadata read by runtime and tooling. Why: Keeps behavior deterministic by centralizing non-code control values.