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

potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow-steward.git


The following commit(s) were added to refs/heads/main by this push:
     new 0033cf2  docs: add introductory index page for docs/ (#449)
0033cf2 is described below

commit 0033cf297e2f721b1e2dc45141113eb34dcc78fa
Author: Rich Bowen <[email protected]>
AuthorDate: Thu Jun 4 11:16:52 2026 -0400

    docs: add introductory index page for docs/ (#449)
    
    * docs: add introductory index page for docs/
    
    Why: the existing documentation has no entry point for someone
    encountering the project for the first time. Every doc assumes
    prior context. This adds a one-page overview with audience paths.
    
    * Make `prek` happy.
    
    * Add security/privacy notes.
    
    Co-authored-by: Jarek Potiuk <[email protected]>
    
    * More fixes (and typos) to make prek happy again. :)
    
    * Apply suggestion from @potiuk
    
    ---------
    
    Co-authored-by: Jarek Potiuk <[email protected]>
---
 docs/index.md | 101 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 101 insertions(+)

diff --git a/docs/index.md b/docs/index.md
new file mode 100644
index 0000000..3cdd9a1
--- /dev/null
+++ b/docs/index.md
@@ -0,0 +1,101 @@
+<!-- START doctoc generated TOC please keep comment here to allow auto update 
-->
+<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
+**Table of Contents**  *generated with 
[DocToc](https://github.com/thlorenz/doctoc)*
+
+- [What is Apache Magpie?](#what-is-apache-magpie)
+  - [How it works](#how-it-works)
+  - [Who is this for?](#who-is-this-for)
+    - [Maintainers wanting to adopt Magpie in their 
project](#maintainers-wanting-to-adopt-magpie-in-their-project)
+    - [Security team members](#security-team-members)
+    - [Contributors to the Magpie framework 
itself](#contributors-to-the-magpie-framework-itself)
+    - [People evaluating whether to adopt](#people-evaluating-whether-to-adopt)
+    - [People who are concerned for security and privacy when using their 
agents](#people-who-are-concerned-for-security-and-privacy-when-using-their-agents)
+  - [Key concepts in 60 seconds](#key-concepts-in-60-seconds)
+  - [Where to go next](#where-to-go-next)
+
+<!-- END doctoc generated TOC please keep comment here to allow auto update -->
+
+# What is Apache Magpie?
+
+Apache Magpie is an AI assistant for open-source project maintainers. It 
handles the repetitive parts of running a project — triaging issues, reviewing 
PRs, onboarding contributors, managing security reports, cutting releases — so 
maintainers can spend their time on design, relationships, and the work that 
actually requires a human.
+
+**The agent proposes. The human decides.** Magpie never merges, never pushes, 
never sends mail, never flips a label without a maintainer confirming first.
+
+---
+
+## How it works
+
+Magpie provides **skills** — step-by-step workflows an AI agent follows. You 
pick which skills your project uses. The agent reads your issues, PRs, or 
security reports, does the analysis, and drafts a response. You review it and 
hit "go" (or don't).
+
+Five **modes** describe what the agent can do, from low-risk to high:
+
+| Mode | What it does | Status |
+|---|---|---|
+| **Triage** | Classify issues/PRs, spot duplicates, propose labels | Stable |
+| **Mentoring** | Help contributors with conventions, point to examples | 
Experimental |
+| **Drafting** | Write a code fix or a PR for you to review | Stable 
(security) |
+| **Pairing** | Self-review your own code before submitting | Experimental |
+| **Auto-merge** | Merge trivial changes without human review | Off 
(deliberately) |
+
+Each project picks the modes that fit. You can run just Triage and nothing 
else.
+
+---
+
+## Who is this for?
+
+### Maintainers wanting to adopt Magpie in their project
+
+You have an open-source project with an issue tracker and/or PR queue, and you 
want agent assistance with the mechanical parts.
+
+→ Start with the [README](../README.md#adopting-the-framework) (adoption 
steps) and [install recipes](setup/install-recipes.md).
+
+### Security team members
+
+You handle CVE reports and want agent help with the 16-step lifecycle — 
import, triage, fix, allocate, publish.
+
+→ Start with [security workflow overview](security/README.md), then [new 
member onboarding](security/new-members-onboarding.md).
+
+### Contributors to the Magpie framework itself
+
+You want to improve the skills, add tools, or fix bugs in the framework.
+
+→ Start with [CONTRIBUTING.md](../CONTRIBUTING.md) and the [spec-driven 
development](spec-driven-development.md) loop.
+
+### People evaluating whether to adopt
+
+You want to understand the trust model, cost, and governance commitments 
before deciding.
+
+→ Read [MISSION.md](../MISSION.md) (the why), 
[PRINCIPLES.md](../PRINCIPLES.md) (the rules), and [mode 
economics](mode-economics.md) (what it costs in tokens).
+
+### People who are concerned for security and privacy when using their agents
+
+You would like to use agentic AI but you are concerned about security and 
privacy - when LLMs / Agent
+might get access to your credentials and poison your workstation, or have 
access to private information
+from mailing lists, slack etc.
+
+→ When you setup Magpie, it will setup your workstation with security 
guardrail layers that will run your agents in containerized sandbox, and it 
will setup privacy gateways for the tools your agentic setup will use. Read 
more details in [Secure agent setup RFC](../docs/rfcs/RFC-AI-0002.md) and 
[Privacy-aware LLM routing for foundation private 
information](../docs/rfcs/RFC-AI-0003.md).
+
+---
+
+## Key concepts in 60 seconds
+
+- **Skill** — A markdown file describing one workflow (e.g., "triage a PR"). 
The agent reads it and follows the steps.
+- **Mode** — A risk level (Triage → Mentoring → Drafting → Pairing → 
Auto-merge). Projects opt in per-mode.
+- **Adopter config** — Your project-specific settings (mailing lists, label 
schemes, canned responses) in a `<project-config>/` directory.
+- **Sandbox** — The agent runs in a locked-down environment. It can't read 
your credentials, can't access the network freely, and can't push code.
+- **Human-in-the-loop** — Every action visible to others requires explicit 
maintainer confirmation. No exceptions until Auto-merge (which is off).
+
+---
+
+## Where to go next
+
+| I want to… | Read… |
+|---|---|
+| Understand the full vision | [MISSION.md](../MISSION.md) |
+| See what skills exist today | [modes.md](modes.md) |
+| Adopt in my project | [README → 
Adopting](../README.md#adopting-the-framework) |
+| Set up the secure agent sandbox | [setup/](setup/README.md) |
+| Understand the security workflow | [security/](security/README.md) |
+| Know what it costs to run | [mode-economics.md](mode-economics.md) |
+| Understand the privacy model | [rfcs/RFC-AI-0003.md](rfcs/RFC-AI-0003.md) |
+| Contribute to the framework | [CONTRIBUTING.md](../CONTRIBUTING.md) |

Reply via email to