CONCEPTS

Mental model for curious users

Read this section when you want the product model behind the commands: why the product exists, how one repo stays authoritative, how outputs differ, and where policy becomes important.

Read In This Order

• start with Why plugin-kit-ai if you want the product-fit answer
• then read How plugin-kit-ai Works for the one-repo model
• read Choosing Runtime when deciding between Go, Node, or Python
• read Target Model when deciding what kind of output to ship
• leave Stability Model for last when you need exact policy language

Why plugin-kit-ai

Understand the problem the product solves, who it fits, and when it is the wrong tool.

How plugin-kit-ai Works

See how one repo stays authoritative while you generate output, validate strictly, and hand off a clean result.

Choosing Runtime

Pick the best starting language without confusing that choice with packaging or integration decisions.

Target Model

Learn the difference between runtime, package, extension, and repo-owned integration outputs.

Stability Model

Use the exact support vocabulary when you need the formal compatibility contract.