Skip to content

docs(system-prompting): methodology corpus + leaks analysis + hermes register case study#42

Open
todie wants to merge 1 commit into
mainfrom
docs/system-prompting-corpus
Open

docs(system-prompting): methodology corpus + leaks analysis + hermes register case study#42
todie wants to merge 1 commit into
mainfrom
docs/system-prompting-corpus

Conversation

@todie

@todie todie commented Jul 18, 2026

Copy link
Copy Markdown
Member

What

New docs/system-prompting/ directory (sibling to docs/eval, docs/specs) collating the estate's system- and user-prompt methodology.

  • methodology synthesis — grounds the house agent-prompting-manual.md (unsigned-paas) in empirical structure and adds the user-prompt half the manual omits.
  • leaks-corpus analysis — 7 findings from todie/system_prompts_leaks (438 prompts, 18 vendors). Analysed against current upstream because the todie fork is ~1yr stale.
  • hermes ops-register case study — the methodology applied to the cerebral-agent (hermes) register, including a live-pod finding: no kubectl/helm/MCP wired, so the broad-RBAC ops mission is currently latent (charter/tool mismatch per manual Principle 7).

Scope

Reference docs only, no code. The register text itself is delivered out-of-band (OpenBao → Secret) per Principle 9 and is not reproduced here.

Related

Part of the hermes/cerebral-agent system-prompt work: fork cerebral-work/cerebral-agent (rebrand) + unsigned-paas chart wiring (SOUL.md via Secret). Follow-up filed: wire kubectl/helm + grafana-MCP or narrow hermes' stated mission.


View with Codesmith Autofix with Codesmith
Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.

…register case study

New docs/system-prompting/ (sibling to docs/eval, docs/specs) collating the estate's
system- and user-prompt methodology:
- methodology synthesis: grounds the house agent-prompting-manual.md in empirical
  structure + adds the user-prompt half the manual omits
- leaks-corpus analysis: 7 findings from todie/system_prompts_leaks (438 prompts,
  18 vendors; analysed against current upstream since the fork is ~1yr stale)
- hermes ops-register case study: methodology applied to cerebral-agent, incl. a
  live-pod charter/tool-mismatch finding (no kubectl/helm/MCP wired)

Reference only; no code. Register text itself delivered out-of-band per Principle 9.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant