IMPLEMENTATION
Make the boundary visible.
Keep authority with the human, durable knowledge in Markdown, retrieval rebuildable, and execution replaceable. Every handoff names its input, output, and verification.
Declare intent
Write the desired outcome, constraints, and acceptance test in plain language.
Map the layers
Assign knowledge, retrieval, procedure, tool, model, and evidence responsibilities.
Bound execution
Grant only the capabilities needed for this task; keep credentials and private data out of public material.
Verify and record
Check the result against the gate and preserve a concise operational record.
Copyable public prompt
Describe [PUBLIC_WORKFLOW] using this boundary map: human authority, Echo character, Hermes runtime, Markdown knowledge, rebuildable retrieval, reusable skills, bounded tools, replaceable models, and evidence. Use placeholders only. Do not include private paths, endpoints, credentials, identities, or raw inventories. End with a verification gate.
Privacy warning
This page is public-safe by design. Never paste private paths, IP addresses, endpoints, credentials, people records, or raw system inventories into a prompt, diagram, or evidence note.
Verification gate
- Authority is explicit and human-owned.
- Each transformation has a named boundary.
- Public copy contains placeholders, not secrets.
- Result has a reproducible check.