From db037511305dad2f77e1b34caf60d79b8ec72b6a Mon Sep 17 00:00:00 2001 From: Bill Berry Date: Mon, 1 Jun 2026 17:56:08 -0700 Subject: [PATCH] docs: add content policies section and refine ADR wording MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - add Content Policies section to CODE_OF_CONDUCT linking Microsoft/GitHub policies - replace Trap with Pitfall in ADR 0001 decision driver and option text - soften bold complementary phrasing in ADR 0002 📝 - Generated by Copilot --- CODE_OF_CONDUCT.md | 9 +++++++++ ...phase-gated-adr-creator-aligned-with-peer-planners.md | 4 ++-- ...y-as-agent-and-skill-behavior-evaluation-framework.md | 2 +- 3 files changed, 12 insertions(+), 3 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 5f9bb93d5..2a6307681 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -21,6 +21,15 @@ Resources: * Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns * Employees can reach out at [aka.ms/opensource/moderation-support](https://aka.ms/opensource/moderation-support) +## Content Policies + +This project follows Microsoft's published policies for AI output and community conduct: + +* AI output and prohibited content categories: [Microsoft Enterprise AI Services Code of Conduct](https://learn.microsoft.com/legal/ai-code-of-conduct) +* Contributor conduct (including responsible use of AI-generated content): [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/) +* GitHub-platform conduct for issues, discussions, and reviews: [GitHub Acceptable Use Policies](https://docs.github.com/site-policy/acceptable-use-policies/github-acceptable-use-policies) +* Microsoft brand and trademark use: [Microsoft Trademark and Brand Guidelines](https://www.microsoft.com/legal/intellectualproperty/trademarks) + --- 🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers. diff --git a/docs/planning/adrs/0001-adopt-phase-gated-adr-creator-aligned-with-peer-planners.md b/docs/planning/adrs/0001-adopt-phase-gated-adr-creator-aligned-with-peer-planners.md index f8609757f..7e627b59a 100644 --- a/docs/planning/adrs/0001-adopt-phase-gated-adr-creator-aligned-with-peer-planners.md +++ b/docs/planning/adrs/0001-adopt-phase-gated-adr-creator-aligned-with-peer-planners.md @@ -122,7 +122,7 @@ ADR templates without forking the agent? | Decision driver | Option A | Option B | Option C | Option D | |--------------------------------------|----------|----------|----------|----------| | Standards fidelity + disclaimer | Yes | No | Partial | No | -| Peer-planner consistency | Yes | No | No | Trap | +| Peer-planner consistency | Yes | No | No | Pitfall | | Thin-orchestrator maintainability | Yes | No | Partial | No | | BYO template support | Yes | No | Partial | No | | Coaching quality (load-before-act) | Yes | Partial | No | Partial | @@ -192,7 +192,7 @@ Compliance with this decision is confirmed by four mechanisms: ### Option C * Good, because each agent can optimize for its specific output shape. -* Bad, because three agents duplicate identity logic (state machine, six-step protocol, Govern autonomy prompt), exactly the maintenance trap the thin-orchestrator driver names. +* Bad, because three agents duplicate identity logic (state machine, six-step protocol, Govern autonomy prompt), exactly the maintenance pitfall the thin-orchestrator driver names. * Bad, because no shared `state.json` schema; resuming a session requires knowing which agent owned it. * Bad, because MADR v4 text and Y-Statement formula end up duplicated across agents, creating drift risk identical to Option B. * Neutral, because contributors writing one ADR shape can ignore the others; cognitive load per session is similar to Option A. diff --git a/docs/planning/adrs/0002-adopt-vally-as-agent-and-skill-behavior-evaluation-framework.md b/docs/planning/adrs/0002-adopt-vally-as-agent-and-skill-behavior-evaluation-framework.md index 9122920b5..cbbbcf269 100644 --- a/docs/planning/adrs/0002-adopt-vally-as-agent-and-skill-behavior-evaluation-framework.md +++ b/docs/planning/adrs/0002-adopt-vally-as-agent-and-skill-behavior-evaluation-framework.md @@ -170,7 +170,7 @@ its tag-routed grader catalog matches the multi-suite design, and it is npm- and GitHub-Actions-native so it fits existing PR CI and local `npm run` workflows. -`vyta/beval` (Option B) is treated as **complementary rather than rejected**: it +`vyta/beval` (Option B) is treated as complementary rather than rejected. It targets a different layer (runtime, multi-turn agentic behavior with scored multi-dimensional metrics and persona-driven conversation simulation over ACP/A2A) and is being integrated through open pull requests. It does not