Explore curated prompts

Act as an agent-governance constitution compiler. Turn the scattered system instructions, project rules, and working preferences I provide into a testable, traceable, and reversible constitution. Never weaken safety, legal, privacy, permission, or production controls merely to make the result shorter. Inputs: - Current instructions: {verbatim text, source file or location, scope, owner, and last-modified time} - Agent mission and users: {jobs, audience, and success criteria} - Non-negotiable boundaries: {safety, legal, privacy, permission, data, and production rules} - Adaptive behavior preferences: {tone, length, initiative, tool choices, and delivery format} - Common jobs and unseen edge cases: {representative work, exceptions, and conflicts} - Real run evidence: {successes, failures, user corrections, incidents, and tests; mark missing evidence unverified} - Change control: {version owner, approver, test budget, and recovery location} Follow this process: 1. Build a traceable ledger. Record each instruction's text, source, owner, trigger scope, dependencies, latest evidence, and semantic overlap. Do not describe unread files, unrun tests, or guesses as facts. 2. Separate four layers: A, non-negotiable safety, legal, privacy, permission, and production guardrails; B, mission principles explaining why the agent exists and what outcomes it protects; C, behavioral guidance that may adapt to the task; and D, preferences such as tone or formatting. Never demote a guardrail into guidance or disguise a preference as a safety rule. 3. Derive principles from commands. For every layer B or C command, state the user outcome it protects, conditions where it applies, conditions where it stops applying, and an observable signal. Merge rules only when evidence supports equivalence. Keep layer A explicit, enforceable, and outside flexible interpretation. 4. Define what the agent is not. List three to seven likely failure identities or behaviors, such as an unsupported agreeer, an unauthorized executor, an evidence fabricator, or a judge that treats preference as fact. Pair every negative identity with an observable replacement behavior instead of a slogan. 5. Establish precedence. Resolve conflicts in this order: law and safety; permission and explicit authorization; truth and privacy; user goals and acceptance criteria; task guidance; expression preferences. When same-layer rules conflict, stop the affected action, show the conflict and evidence gap, and request a decision from the owner of that scope. Never silently choose the more convenient rule. 6. Test edge cases. Write at least five representative cases and three counterexamples with input, triggered rule, expected behavior, prohibited behavior, and pass criteria. Cover missing information, rule conflict, external writes, failure recovery, and a changed user request. 7. Control changes. Assign the constitution a version, owner, reason for change, test result, and previous recoverable version. Return a draft and semantic diff before any overwrite. High-risk changes require the named approval and an isolated test. 8. Final audit. Confirm that every guardrail remains, principles have evidence, guidance has applicability conditions, preferences yield to higher layers, unknowns are labeled, and no credentials or personal data were copied into the output. Return exactly: A. Executive summary; B. Instruction-source ledger; C. Four-layer constitution; D. Negative identities and replacement behaviors; E. Conflict precedence; F. Edge-case and counterexample tests; G. Version, approval, and rollback plan; H. Semantic diff from current instructions; I. Unverified items.