This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch fix/mission-line-85-mode-rename-leftover
in repository https://gitbox.apache.org/repos/asf/airflow-steward.git

commit 1681957bc601f5ba5a4ae6f483c140a931f1a110
Author: Jarek Potiuk <[email protected]>
AuthorDate: Sun May 10 12:56:56 2026 +0200

    docs(mission): fix "modes A–C" leftover in v1 vendor-neutrality goal
    
    Follow-up to #99 — caught one missed rename in MISSION.md line 85
    (the "Validate vendor-neutrality in v1 pilots" goal under Initial
    Goals). All other references were renamed in #99.
    
    Generated-by: Claude Code (Claude Opus 4.7)
---
 MISSION.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MISSION.md b/MISSION.md
index 4dfd327..ba3c0dd 100644
--- a/MISSION.md
+++ b/MISSION.md
@@ -82,7 +82,7 @@ Four design choices set the project apart from "just bolt a 
code-review bot on i
 - Settle on a contributor-sentiment evaluation methodology with Apache Plumb 
(separate proposal). Eval covers both ASF and non-ASF cohorts so the data isn't 
an internal-ASF artefact.
 - **Ship the privacy and security posture** as a release-blocking part of v1 — 
sandbox setup, clean-env wrapper, privacy-LLM gate, PII redactor, signed 
releases, pinned-tools manifest. Not a follow-up.
 - **Ship the maintainer-education stream** alongside v1 — pattern catalogue, 
"your first skill" path, first scheduled workshops. The platform is only as 
adoptable as the docs that go with it.
-- **Validate vendor-neutrality** in v1 pilots: at least one project running 
modes A–C against a frontier-model backend, one against fully-local inference 
(Ollama / vLLM), one against an Apache-hosted or Apache-aligned endpoint as it 
becomes available.
+- **Validate vendor-neutrality** in v1 pilots: at least one project running 
Triage, Mentoring, and Drafting against a frontier-model backend, one against 
fully-local inference (Ollama / vLLM), one against an Apache-hosted or 
Apache-aligned endpoint as it becomes available.
 
 ## Technical scope
 

Reply via email to