Files
canina/infra/hermes-editorial/README.md
T

77 lines
4.5 KiB
Markdown

# Hermes editorial runtime distribution v4.1.0
Config-only tracked artifact for `canina-hermes`, explicit home `/opt/data`.
No deployment or runtime writes were performed by this change. Parent owns CI
copy/provisioning and Stage bridge acceptance. No dependencies beyond Python stdlib.
## Isolated verification / approved CI usage
```
python3 -m unittest discover -s infra/hermes-editorial/tests -v
python3 infra/hermes-editorial/installer.py install --target-home /ABSOLUTE/DISPOSABLE/HOME
python3 infra/hermes-editorial/installer.py verify --target-home /ABSOLUTE/DISPOSABLE/HOME
python3 infra/hermes-editorial/installer.py rollback --target-home /ABSOLUTE/DISPOSABLE/HOME
```
Never use live `/opt/data` until the parent-approved CI installation step. Installer
requires an explicit existing absolute home. Exact 19-file allowlist and SHA-256
manifest cover unique `canina-editorial-v4` skills for six canonical profiles plus
blocked status. No root skill inheritance is assumed. Profile discovery requires
fresh-session validation after CI; copying bytes alone is not runtime discovery.
Each changed file is fsynced and atomically replaced on its destination filesystem.
A durable write-ahead rollback journal records only allowlisted owned files and
original modes; a process lock rejects concurrent installers. Synchronous failures
restore the prior files. Process death may leave a partial transaction: rollback
before retry; never activate consumers during install. This is per-file atomicity,
not a claim of a globally atomic multi-directory swap. Rollback preflights every
file, refuses external-edit conflicts, restores old bytes/modes, removes newly
installed files, and leaves empty directories/lock. An unchanged reinstall performs
no byte/mtime changes. Different-version upgrades require rollback first. Do not
edit or symlink managed paths concurrently; installer rejects existing symlink
ancestors but is not an adversarial filesystem sandbox.
## Read-only target findings (2026-10-24 UTC)
Inspected canonical `pmo`, `canina-competitor-worker`, `canina-seo-worker`,
`canina-content-worker`, `canina-vet-review-worker`, `canina-qa-worker` under
`/opt/data/profiles`. All exist; registry uses these names. PMO filesystem skill
inventory lacks `canina-daily-content-publisher`; Content has it. Root publisher
exists at `/opt/data/skills/canina/canina-daily-content-publisher/SKILL.md`.
Existing cron JSON contains 17 jobs, all `enabled:false`, `state:paused` (there is
no `paused` boolean field). CLI resolves `/opt/hermes/bin/hermes`.
No secret values, config files, cron prompts or database contents were copied.
Target checks establish filesystem availability, not an end-to-end workflow.
## Backend proposal bridge integration contract
Parent reports implementation `09dbe4d`, integrated as `64419f6`. This bundle does
not mark dispatch or actual execution verified merely because this endpoint exists.
CI/grant provisioning belongs to parent. No speculative token path or grants are
created here; parent must pin the dedicated PMO secret file and service origin
before implementing/exercising a submitting client. Never pass tokens in argv,
print tokens, use generic admin grants, or submit to Production.
* POST `/api/internal/prepare-worker/editorial-proposals`, authenticated Bearer
dedicated grant with id `pmo`, role `WORKFLOW_WORKER`, explicitly listed in
`workerIds`.
* DTO: `requestId` UUID; `pilotKind:editorial-research-to-brief-v1`;
`operationMode:PREPARE`; `environment:staging`;
`scope:EDITORIAL_RESEARCH_TO_BRIEF`; `researchTopic` <=180 characters;
`acceptanceCriteria` 1..10 strings each <=500 characters; `commitSha` 40 lowercase
hexadecimal characters; `budgetLimitCents:20`.
* Response: `taskId`, `key`, `state:GATE1_PENDING`, `version`, `metadata`.
* Submission is proposal preparation only, not worker execution, Gate1 approval,
budget expenditure evidence, article creation or publishing authorization.
A fixed reviewed request must be committed separately with a real commit SHA
and stable requestId; ambiguous submit requires reconciliation, not new UUID retry.
## Remaining acceptance blockers
Read `payload/editorial-v4/status.json`. Dispatch/result transport, durable
artifacts, authenticated owner gates, first-party research, image routing,
Stage Admin auth, scoped backup/restore, publisher idempotency and public browser
verification are all unverified. No cron activation, deployment, Production write
or RELEASE_AUTHORIZE is included. Config isolation tests cannot establish any of
these bridges. Policy is in each profile-local `references/policy.md`.